Person
Oliwer
Capabilities
Contributes to
AccessibilityUI5AccessibilityMaking a UI usable with a screen reader, with a keyboard alone and without seeing the layout: accessible names on controls, a heading order, landmarks, focus handling and announcements. Target size for a finger is [touch operation](capability:ui5-touch-uis).Agent access to your codeUI5Agent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Data bindingUI5Data bindingKeeping a control and a model in step in both directions, including the formatting, type conversion and validation that sit between the two.Key-user adaptationUI5Key-user adaptationChanging a delivered app without modifying it — moving, hiding and adding elements as a layered set of changes that survive an upgrade.LoggingUI5LoggingSeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.Routing and navigationUI5Routing and navigationTurning a URL hash into a view, and a view change back into a URL — so a deep link, a browser back button and a refresh all land where the user expects in a single-page app.ThemingUI5ThemingApplying a consistent visual identity across every control, including the parameters an app may read and the custom themes an organisation may build.TypeScript supportUI5TypeScript supportWriting 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 testingProving 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 interopUsing 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.
Entries
Group by
EntrySignals
Contributes to
@openui5/sap.ui.core@openui5/sap.ui.coreThe OpenUI5 core: the module loader, the MVC runtime, data binding, routing, theming and the test stack, which is everything a UI5 app does before a single community package is added.sap official, ui5
Framework core: module loader, MVC runtime, binding, routing, theming
@ui5/mcp-server@ui5/mcp-serverSAP's MCP server for UI5 development: ten tools that scaffold an app or a card, read the project in front of the agent, and run the linter and the manifest validator against it.sap official, ui5
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
MCP server for UI5 development with ten tools
Details
For your agent
- Ref
actor:1110101- JSON
- /actors/1110101.json
- MCP
- Connecting an agent