SAP
Entries
Framework core: module loader, MVC runtime, binding, routing, theming
Colour, font and metric definitions of the SAP themes
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Writer module for changing a CAP project's configuration from code
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
MCP server for creating and editing Fiori applications
Reader and writer for i18n bundles of UI5 or CAP projects
Writer that adds an OData service to an existing UI5 project
OASIS and SAP OData vocabularies with a VocabularyService
Writer of the base structure of a UI5 project from Node code
Pro-code CLI for building and deploying Joule Studio solutions
UI5 Tooling command line for project setup, dev server and build
Internal logger of the UI5 CLI
The declared repository is archived.
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
Joule's generative AI inside SAP Build Code
Development environment on BTP for UI5, Fiori, mobile and CAP
Role-based portal sites with pages, apps and widgets
Predefined CI/CD pipelines for SAP development projects
APIs and a UI5 component for document management in apps
IDE service on SAP BTP for SAPUI5, Fiori and full-stack apps
Agent skill built from the Fiori Design Guidelines
Knowledge about theming, not a theme build: nothing here compiles a theme or deploys one, and it says nothing about a custom control's own parameters.
Agent plugin on the SAP Design System and theming parameters
Key-user adaptation and personalisation for UI5 apps on SAP BTP
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
Details
History
- @openui5/sap.ui.coreThe 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-agentscapability: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-agentsThe 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-guidelinesRead 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 optionAdd 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/loggerFiled 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-serverMCP 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-serverIt 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.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-agentsEntered 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-serverTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/fiori-mcp-serverPlacement 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/loggerTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @ui5/loggerPlacement assumes cap for everything it accepts.
- @ui5/loggerPlacement 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
- Ref
actor:sap- JSON
- /actors/sap.json
- MCP
- Connecting an agent