Person
Nikolay Kolarov
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 guidanceUI5Agent guidancePackaged 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.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/plugins-coding-agentsUI5/plugins-coding-agentsUI5's own plugins for coding agents, three of them: everyday development, modernising a legacy project, and converting one to TypeScript, each installed into Claude Code or GitHub Copilot.sap official, ui5
Guidance, not access: these are instructions handed to an agent, and what the agent can then read of your project comes from [@ui5/mcp-server](artifact:ui5-mcp-server) or the editor. A modernisation workflow that runs autonomously across a codebase is also a thing to point at a branch rather than at main.
UI5 plugins for coding agents
Details
For your agent
- Ref
actor:nikolay-kolarov- JSON
- /actors/nikolay-kolarov.json
- MCP
- Connecting an agent