OrganisationSAP

SAP

Provides 19
AccessibilityUI5AccessibilitycapabilityMaking 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 codeUI5CAPABAPBTPAgent access to your codecapabilityLetting 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 guidanceUI5CAPBTPABAPAgent 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.AttachmentsUI5CAPABAPBTPAttachmentscapabilityStoring 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.Build and dev-server toolingUI5Build and dev-server toolingcapabilityServing an app locally and building it for deployment — proxying a backend, transpiling, bundling, and shaping the result for whatever will host it.Data bindingUI5Data bindingcapabilityKeeping a control and a model in step in both directions, including the formatting, type conversion and validation that sit between the two.Editor supportUI5CAPABAPBTPEditor supportcapabilityWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.Fiori annotationsUI5CAPABAPFiori annotationscapabilityDescribing 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.GeneratorsUI5CAPABAPGeneratorscapabilityGetting 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 adaptationUI5ABAPBTPKey-user adaptationcapabilityChanging a delivered app without modifying it — moving, hiding and adding elements as a layered set of changes that survive an upgrade.Launchpad and site contentUI5BTPLaunchpad and site contentcapabilityGetting apps, cards, pages and workspaces in front of users in an application launchpad or portal, including content providers, content packages and access roles. Serving the application’s files is [app hosting](capability:app-hosting); extending the surrounding shell is [launchpad plugins](capability:launchpad-plugins).LintingUI5CAPLintingcapabilityCatching 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.LocalizationUI5CAPABAPBTPLocalizationcapabilityServing labels, messages and translated content per user locale, including translatable model elements and per-tenant text overrides.LoggingUI5CAPBTPABAPLoggingcapabilitySeeing 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 navigationcapabilityTurning 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.ThemingUI5ThemingcapabilityApplying a consistent visual identity across every control, including the parameters an app may read and the custom themes an organisation may build.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.

Entries24

Group by24 of 24 entries
EntrySignals
Maintains24
@openui5/sap.ui.corev1.153.0
none

Framework core: module loader, MVC runtime, binding, routing, theming

@sap-theming/theming-base-contentv11.36.5
none

Colour, font and metric definitions of the SAP themes

@sap-ux/cap-config-writerv1.0.45
Functional boundary

Writer module for changing a CAP project's configuration from code

@sap-ux/createv1.5.5
none

Command line for changing features of an existing Fiori project

@sap-ux/fe-fpm-writerv1.3.25
none

Writer of flexible programming model elements into Fiori elements apps

@sap-ux/fiori-mcp-serverv1.15.15
none

MCP server for creating and editing Fiori applications

@sap-ux/i18nv1.0.6
none

Reader and writer for i18n bundles of UI5 or CAP projects

@sap-ux/odata-service-writerv1.0.26
none

Writer that adds an OData service to an existing UI5 project

@sap-ux/odata-vocabulariesv1.1.3
none

OASIS and SAP OData vocabularies with a VocabularyService

@sap-ux/ui5-application-writerv2.1.6
none

Writer of the base structure of a UI5 project from Node code

@sap/joule-work-dev-cli-early-adoptersv0.1.20-alpha.25
none

Pro-code CLI for building and deploying Joule Studio solutions

@ui5/cliv4.0.71
none

UI5 Tooling command line for project setup, dev server and build

@ui5/loggerv4.0.2
none

Internal logger of the UI5 CLI

@ui5/tooling-webcv0.3.1
Archived

Deprecated UI5 Tooling extensions for UI5 Web Components wrappers

Joule in SAP Build Code
none

Joule's generative AI inside SAP Build Code

SAP Build Code
none

Development environment on BTP for UI5, Fiori, mobile and CAP

SAP Cloud Portal Service
none

Role-based portal sites with pages, apps and widgets

SAP Continuous Integration and Delivery
none

Predefined CI/CD pipelines for SAP development projects

SAP Document Management service, integration option
none

APIs and a UI5 component for document management in apps

SAP Web IDE Full-Stack
none

IDE service on SAP BTP for SAPUI5, Fiori and full-stack apps

sap-fiori-guidelines
none

Agent skill built from the Fiori Design Guidelines

SAP/ui-theme-designer-plugins-for-coding-agents
Functional boundary

Agent plugin on the SAP Design System and theming parameters

UI flexibility service
none

Key-user adaptation and personalisation for UI5 apps on SAP BTP

vscode-ui5-language-assistantv0.0.1-security
none

VS Code extension for SAPUI5 and OpenUI5 XML views and manifest

Details

History16
  • @openui5/sap.ui.coreprovides[capability:ui5-testing] → The same sentence with where each part runs, three sources and the test_level propertyThe edge carried no source, so what the package answers for this capability was an unattributed claim. The three parts are each stated by SAP's own documentation, and the level the package covers, unit and integration, is the comparison the capability now declares. End-to-end is left absent rather than entered as a no: the OPA page's restrictions are the capability's boundary and are recorded there. The other six edges were not read for this job and are unchanged.
  • SAP/ui-theme-designer-plugins-for-coding-agentsprovides.agent-guidance.facets.installs_into → Claude Code, GitHub Copilotcapability:agent-guidance widened the installs_into property to the UI5 door. The plugin's own README carries two install commands, one for the Claude Code marketplace and one for the Copilot one, and a third route through the skills command line that names no client.
  • SAP/ui-theme-designer-plugins-for-coding-agentsdescription.what_it_solves → The same sentence with parameter inheritance named, followed by the three install routes.The plugin's own README read on 2026-10-15 lists parameter inheritance beside component consumption in the design-tokens skill, and the entry said nothing about how the plugin gets in front of an agent. Both are facts a reader needs before the parameter mapping is any use to them.
  • sap-fiori-guidelinesentry → createdRead out of the SAP AI Skills Library repository, which the atlas holds as source:sap-ai-skills-library rather than as an artifact because the registry keeps other people's code in their own repositories. This skill is SAP's own code in that repository, so it is entered from its SKILL.md, README and references directory, as plugins/aicore-skills was on 2026-09-25. Hard rule 7: skills are indexed, never authored here.
  • SAP Document Management service, integration optionserves_ecosystems → ui5, capAdd CAP to served ecosystems from documented CAP integration; preserve the existing BTP/UI5 contribution and source dates. CAP plugin restrictions do not apply to the service itself.
  • @ui5/loggerprovides → capability:ui5-build-toolingFiled under logging, which is a running service's log output. This is the UI5 CLI's internal logger, described by its own README as internal — it answers nothing a reader would pick for logging, and belongs where the tooling that depends on it lives.
  • @sap-ux/fiori-mcp-serverprovides → capability:agent-code-accessMCP is how this is delivered, not what it answers — artifact_type carries the transport. It helps an agent work on real code rather than exposing a running service to one, which is a different capability.
  • @sap-ux/fiori-mcp-serverecosystem → ui5It creates and edits Fiori applications and ships from SAP/open-ux-tools; nothing about it is CAP's. Typed cap by placement, which defaults every candidate to the primary door. serves_ecosystems keeps it behind the CAP door, where a CAP developer building a Fiori front end still finds it.
  • @sap-ux/fiori-mcp-serverlinks.docs → https://github.com/SAP/open-ux-tools/tree/main/packages/fiori-mcp-serverlinks.repo is the whole of SAP/open-ux-tools, which carries much else besides this. Naming the package directory says which part of the monorepo the artifact is — and it is what lets a sweep tell this entry apart from the next package in the same repository.
  • SAP/ui-theme-designer-plugins-for-coding-agentsentry → createdEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.
  • @sap-ux/fiori-mcp-serverartifact_type → mcp-serverTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
  • @sap-ux/fiori-mcp-serverdescription.one_line → SAP's Fiori MCP server, run as `fiori-mcp`, letting a coding assistant create and edit Fiori applications directly rather than describing the steps.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
  • @ui5/loggerartifact_type → packageTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
  • @ui5/loggerecosystem → ui5Placement assumes cap for everything it accepts.
  • @ui5/loggerdescription.one_line → UI5 CLI's internal logger, described by its own readme as internal — it appears here because other UI5 tooling depends on it.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
  • First entry seenDiscovered via bestofui5, npm registry · npm:sap cap plugin, The discovery pass, npm registry, GitHub API · SAP/open-ux-tools, GitHub API · SAP, Added by hand, SAP AI Skills Library · github.com/SAP/ai-skills-library — skills/sap-fiori-guidelines, sap-ai-mcp-servers.
For your agent