Person

Tobias Hofmann

Capabilities16

Provides 2
IDE provisioningABAPIDE provisioningcapabilityGetting the IDE onto a developer's machine with the required plugins already in it, at a version the team can name. Distinct from [editor support](capability:editor-support), which is what the editor does once it is there: this is the download, the update site, the install and how the result reaches machines a developer does not administer.Knowing the maintenance status of a releaseABAPUI5Knowing the maintenance status of a releasecapabilityKnowing whether a release a solution runs on is still maintained, and until when: which versions get fixes, which get critical fixes only, and when maintenance ends. Upgrading to a newer release once that is known is a different job.
Demonstrates 3
DocumentationUI5ABAPDocumentationcapabilityFinding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.Static analysisABAPStatic analysiscapabilityCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.Unit testingABAPUnit testingcapabilityTesting application logic without a running business process — and the test doubles that make dependencies on the database and on framework services tractable.
Contributes to 11
Agent guidanceUI5ABAPAgent guidancecapabilityPackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.AttachmentsUI5ABAPAttachmentscapabilityStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.Editor supportABAPUI5Editor supportcapabilityWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.GeneratorsABAPUI5GeneratorscapabilityGetting from nothing to a project that runs, and from a project that runs to one that has the piece you just decided you need. Two different moments: the first is a one-time decision about layout, the second recurs for the life of the project.Launchpad pluginsUI5ABAPLaunchpad pluginscapabilityExtending an application launchpad’s shell rather than an individual app: adding header buttons, user-menu entries, frame areas or background behaviour shared across the apps it hosts. A development sandbox for launching an app is a separate concern.LLM integrationUI5ABAPLLM integrationcapabilityCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.ThemingUI5ThemingcapabilityApplying a consistent visual identity across every control, including the parameters an app may read and the custom themes an organisation may build.Touch operationUI5Touch operationcapabilityOperating an app with a finger, a stylus or a gloved hand on a tablet, kiosk or shop-floor terminal: targets large enough to hit, and input that does not assume a hardware keyboard. Distinct from responsive layout, which is about the width of the screen rather than what touches it.TypeScript supportUI5TypeScript supportcapabilityWriting apps and libraries in TypeScript — the type definitions, the module syntax the loader expects, and the build step that gets from one to the other.UI5 testingUI5UI5 testingcapabilityProving a UI still works — unit tests over controllers and formatters, integration tests that drive real controls, and end-to-end runs against a served app.Web Components interopUI5Web Components interopcapabilityUsing standards-based custom elements inside an app, and the question of which control set an app should be built from at all, two concerns that are often answered as one.

Entries12

Group by12 of 12 entries
EntrySignals
Maintains2
adt-bundle-builder
none

Windows build packaging Eclipse with ADT as a portable IDE

pam-mcp-server
none

Local MCP server on support status from an SAP PAM export

Maintains: samples, sketches and references2
off-stack-abap
none

Demonstration of off-stack ABAP development on Node.js

SAP Support Radar
none

Browser app checking SAP product support status from a PAM export

Contributes to8
@ui5/webcomponentsv2.28.1
Functional boundary

SAP's UI elements as standard custom elements

generator-ui5-appv1.0.8
none

Easy-UI5 generator scaffolding a new UI5 application

generator-ui5-flp-plugin
none

Easy-UI5 generator scaffolding a Fiori Launchpad plugin

my-ide-actions
none

Collection of ABAP Development Tools IDE Actions

SAP-samples/ui5-typescript-tutorial
none

Tutorial on TypeScript for UI5 apps via a weather-lookup app

UI5 Web Components agent skills
Functional boundary

Two agent skills for accessibility and styling of web components

ui5-journey-recorder
none

Chrome extension generating OPA5 or wdi5 tests from recorded journeys

wdio-ui5-servicev3.0.12
Functional boundary

End-to-end testing for UI5 on WebdriverIO with UI5 control selectors

Details

History3
  • pam-mcp-serverentry → createdStaged as its own entry beside the app (ADR-0063, two entries) because an agent reaches for the server and a person opens the app. part_of rests on the README's project layout. ecosystem: umbrella and serves_ecosystems: abap for the same reasons as the app: it reads the same matrix, and its documentation's worked example queries SAP S/4HANA 2022 and SAP NetWeaver 7.5. No tool_count: the README lists three tools and states no count. Its package is private and not on npm.
  • SAP Support Radarentry → createdStaged with the capability Knowing the maintenance status of a release and the external SAP Product Availability Matrix. ecosystem: umbrella (ADR-0063) because its documentation is about SAP products as such and names no single stack it serves: "Check the support/maintenance status of the SAP products and versions you actually use against the official SAP Product Availability Matrix (PAM)". OpenUI5 is what it is built with, not whom it serves. serves_ecosystems: abap because the releases its documentation checks are SAP S/4HANA and SAP NetWeaver, as in the worked example in docs/mcp-server.md ("SAP S/4HANA 2022 On-Premise", "SAP NetWeaver 7.5"). use_as: reference because it is consulted at its own address. The README names no contributors besides the maintainer. Named SAP Support Radar, the title the maker gives it in the README, by the maintainer's decision on 2026-10-12; serves_ecosystems: abap confirmed by the maintainer the same day.
  • First entry seenDiscovered via Added by hand.
Profile1
For your agent