Person
GDamyanov
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 codeCAPUI5Agent 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.Agent guidanceCAPUI5Agent 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.AttachmentsCAPUI5AttachmentsStoring 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.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.DocumentationCAPUI5DocumentationFinding 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.Fiori annotationsCAPUI5Fiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.GeneratorsCAPUI5GeneratorsGetting 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.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.LintingCAPUI5LintingCatching in the editor what would otherwise be caught at deploy time, or not at all — problems in source code and models and in the project's configuration, found by rules rather than by review.LLM integrationCAPUI5LLM integrationCalling 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.LoggingCAPUI5LoggingSeeing 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.TelemetryCAPTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.ThemingUI5ThemingApplying a consistent visual identity across every control, including the parameters an app may read and the custom themes an organisation may build.Touch operationUI5Touch operationOperating 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 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 by13 of 13 entries
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
@sap-ux/cds-annotation-parser@sap-ux/cds-annotation-parserParses annotations out of CDS source, so tooling can read what a model says about its UI without compiling it.sap official, cap
Parser for annotations in CDS source
@sap-ux/cds-odata-annotation-converter@sap-ux/cds-odata-annotation-converterConverts CDS annotations into their OData form, which is the translation Fiori tooling needs to reason about a service the way a client sees it.sap official, cap
Converter from CDS annotations to their OData form
@sap-ux/create@sap-ux/createSAP Fiori tools as a command: npx @sap-ux/create changes the features of a Fiori project that already exists, through its add, generate, convert, remove, update and change subcommands.sap official, ui5
Command line for changing features of an existing Fiori project
@sap-ux/eslint-plugin-fiori-tools@sap-ux/eslint-plugin-fiori-toolsESLint rules from the Fiori tools team, aimed at the parts of a project their generators produce.sap official, cap
ESLint rules for projects the Fiori tools generators produce
@sap-ux/fiori-annotation-api@sap-ux/fiori-annotation-apiThe programmatic API Fiori tooling uses to read and write annotations on a project, rather than editing the files as text.sap official, cap
Programmatic API for reading and writing project annotations
@sap-ux/fiori-docs-embeddings@sap-ux/fiori-docs-embeddingsFiori documentation indexed as embeddings, which is what makes it searchable by something other than a person scrolling it.sap official, cap
Fiori documentation indexed as embeddings
@sap-ux/fiori-generator-shared@sap-ux/fiori-generator-sharedThe shared functions and types the Fiori generators are built from; a dependency of theirs rather than a generator itself.sap official, cap
Shared functions and types of the Fiori generators
@sap-ux/fiori-mcp-server@sap-ux/fiori-mcp-serverSAP's Fiori MCP server, run as fiori-mcp, letting a coding assistant create and edit Fiori applications directly rather than describing the steps.sap official, ui5
MCP server for creating and editing Fiori applications
@sap-ux/telemetry@sap-ux/telemetryLibrary for sending usage telemetry datasap official, cap
Library for sending usage telemetry data
@ui5/webcomponents@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
SAP's UI elements as standard custom elements
SAP-samples/adaptation-project-exercisesSAP-samples/adaptation-project-exercisesA UI5Con workshop on building SAPUI5 Adaptation Projects, which customise a released application through controller and fragment extensions without changing its source, run in SAP Business Application Studio.sap official, ui5
UI5Con workshop on building SAPUI5 Adaptation Projects
UI5 Web Components agent skillsUI5 Web Components agent skillsTwo skills shipped inside the UI5 Web Components repository itself, under skills/: one for accessibility, covering ARIA and keyboard behaviour, and one for styling through shadow parts and custom properties.sap official, ui5
Two skills, narrowly scoped: nothing here scaffolds an application or answers what a component's API is — that is [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server), which reads the same library's documentation.
Two agent skills for accessibility and styling of web components
Details
For your agent
- Ref
actor:gdamyanov- JSON
- /actors/gdamyanov.json
- MCP
- Connecting an agent