Agent guidance
One surface at a time, and most of what sits behind this door is SAP's. 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 covers everyday development, modernising a legacy project and converting one to TypeScript, as three plugins rather than one bundle; the Web Components 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 ship inside the component library itself, so accessibility and styling guidance versions with the components it describes; the UI theme designer pluginSAP/ui-theme-designer-plugins-for-coding-agentsOne plugin that teaches a coding agent the SAP Design System, Fiori design tokens, and which theming parameters a given control actually reads, installed into Claude Code or GitHub Copilot.sap official, ui5 carries the design system, the Fiori design tokens and which parameters a given control actually reads; and sap-fiori-guidelinessap-fiori-guidelinesAn agent skill SAP publishes in its AI Skills Library, built from the Fiori Design Guidelines at v1.145: eighteen reference files an agent reads before it picks a control, a page type or an AI pattern.sap official, ui5, published in SAP's skills library rather than by the UI5 team, carries the Fiori design guidelines themselves as reference files dated to one revision. scaffold-fiori-ai-bridgescaffold-fiori-ai-bridgeAn agent skill that makes a UI5 or Fiori app AI-callable: it generates the JavaScript bridge and the SAP Joule Frontend Actions YAML the app needs before an agent can reach into it.independent, ui5 points the other way: it hands an agent the procedure for making a finished application callable by SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btp, not for writing one.
Overview
sap-fiori-guidelines An agent skill SAP publishes in its AI Skills Library, built from the Fiori Design Guidelines at v1.145: eighteen reference files an agent reads before it picks a control, a page type or an AI pattern.
UI5/plugins-coding-agents UI5'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-fiori-guidelines An agent skill SAP publishes in its AI Skills Library, built from the Fiori Design Guidelines at v1.145: eighteen reference files an agent reads before it picks a control, a page type or an AI pattern.
UI5/plugins-coding-agents UI5'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-fiori-guidelines An agent skill SAP publishes in its AI Skills Library, built from the Fiori Design Guidelines at v1.145: eighteen reference files an agent reads before it picks a control, a page type or an AI pattern.
UI5 Web Components agent skills Two 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.
Not covered: At knowledge. What the agent can then read of your project comes from @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 or the editor and not from a skill file, and the plugins say so themselves: installed as skills alone, that server has to be put there by hand. In one place it also stops at a dated reading, since the design-guidelines skill names the revision it was built from and the guidelines keep moving.
The door is lopsided. The sets behind it are mostly SAP's, each about a surface SAP owns, and the community weight sits in collections whose primary door is CAP or BTP and in the entry that answers an outcome of its own. Which half was first here is not established, so the pattern is left unassessed rather than read off the dates the entries happened to enter the atlas.
scaffold-fiori-ai-bridgescaffold-fiori-ai-bridgeAn agent skill that makes a UI5 or Fiori app AI-callable: it generates the JavaScript bridge and the SAP Joule Frontend Actions YAML the app needs before an agent can reach into it.independent, ui5 lives behind the door and answers a question SAP's sets are not about, turning what an application can already do into SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btp Frontend Actions or WebMCP tools. Collections serve the door from elsewhere and are broad SAP collections, not UI5 sets: secondsky/sap-skillssecondsky/sap-skillsForty SAP development plugins installed through the skills command line or the Claude Code and Codex marketplaces, with a record per plugin of what its claims were checked against.independent, btp, SAP Power for KiroSAP Power for KiroA set of thirty-five-plus SAP skills packaged as a power for Kiro IDE rather than Claude Code, spanning BTP, UI5, data and analytics, ABAP, CAP and CLI tooling, with automatic context activation in Kiro.independent, btp and sap-odata-explorersap-odata-explorerA Rust CLI and desktop app for exploring and testing SAP OData services against real systems — catalog discovery, metadata browsing, an F4 value-help picker and a Fiori-readiness linter — with an agent skill shipped beside it.independent, btp name Fiori elements work in their own words, Kiro's is packaged as a power instead of a skill standard, and skillOverflowDanKromp/skillOverflowA collection of 41 agent skills, 37 for CAP, Fiori, BTP, UI5, ABAP, Integration Suite and HANA work and four for creating, reviewing and retiring skills, each with its own eval.independent, cap states no flavor and carries UI5 data binding, controls, i18n and testing as separate skills.
Artifacts
Tasks
Get an agent to follow the SAP Fiori design guidelines
A developer wants the controls, colours and messages an agent writes into a Fiori application to follow SAP's design guidelines, without the guidelines being pasted into the prompt each time.
About how the design rules reach the agent and which slice of them it gets. The guidelines themselves are SAP's and stay at experience.sap.com; whether a built screen passes a design review is not something any of these records establishes, and checking what an agent produced against a stated expectation is agent evals.
sap-fiori-guidelinesThe one entry whose subject is the guidelines rather than a framework. Its frontmatter names the cases it applies to, from buttons and tables through object pages and list reports to colours, typography and Joule integration, and the skill answers the recurring questions before any reference file is opened: that the emphasized button is the primary action and there is one per page or dialog, what each semantic colour means, and that an error prevents a task while a warning lets the user proceed. It also states which of SAPUI5, UI5 Web Components and Fiori elements each kind of application calls for, so an agent choosing between them has the skill's own answer.
Remaining work: Install it with the skills command line. The README names the revision it was built from, v1.145 of May 2026, so a rule that has moved since is the reader's to check against SAP's own page; the skill carries one dated reading rather than a live feed.
SAP/ui-theme-designer-plugins-for-coding-agentsTwo skills in one plugin. One is about using UI theme designer on BTP; the other answers questions about the SAP Design System and the Fiori design tokens, including parameter inheritance and which theming parameters specific UI components use. That last fact is the one a colour change rests on and the one a control's public API does not state, which is why it sits here rather than in the guidelines skill.
Remaining work: Install it as a plugin in Claude Code or GitHub Copilot, each with its own command, or through the skills command line. Nothing in it compiles or deploys a theme, and it states no UI5 flavor, so whether its parameter mapping reaches the Web Components library as well as SAPUI5 controls was not established.
UI5 Web Components agent skillsTwo skills under skills/ in the components' own repository, so they move when the components do. The accessibility one states what the shadow DOM handles on its own, the ARIA roles, keyboard navigation, screen-reader support and high-contrast themes, and then names the properties and the InvisibleMessage API that cover what it does not. That is the part of the design system a guidelines document cannot answer, because it depends on what the component already does.
Remaining work: Get the two skills in front of an agent. Nothing read in the repository on 2026-10-15 names a client they install into, so how they are loaded is the reader's to work out.
secondsky/sap-skillsForty plugins for SAP development, among them one the README lists for SAPUI5 framework development and one for Fiori tools. Whether either carries design-guideline rules was not established: only the plugin list and the install section were read, not the plugin's own skill files. It is listed so a reader who already has it installed can see it was looked at rather than ruled out.
Remaining work: Read the SAPUI5 plugin's own skill files, and the per-plugin verification ledger entry beside it, which records what each claim was checked against.
Make a Fiori application's own actions callable by Joule
A developer wants the things their UI5 or Fiori application can already do, such as reading what is displayed, applying a filter, navigating or pressing a button, exposed as actions an assistant may call, without working out the bridge and the descriptor shapes from scratch.
About the packaged procedure and the files it writes. Deploying the capability descriptor to a SAP Joule tenant and confirming the actions are reachable are outside it and the skill says so; what the application does once an assistant calls in is the application's own behaviour.
scaffold-fiori-ai-bridgeIt asks three questions before it reads any code, whether the target is an application or a library control, which consumer is wanted, and whether tools should be semantic or one per control. Then it reads the manifest, Component.js, the controllers, the views and the models, puts the grouped candidates back for confirmation, and writes the files only after the developer signs off on the list. It carries the runtime limits as rules rather than as notes: a { status, content } return with the content always a string, fifteen seconds an action, ten kilobytes of response, a thousand characters of scenario description, and a com.sap.<namespace>.<ActionName>.v1 name matching in the JavaScript and the YAML.
Remaining work: Deploy the capability descriptor to the Joule tenant through the command line, which the skill states is not its step, and verify the actions are reachable from there. The repository read on 2026-10-15 names no client the skill installs into, so loading it is the reader's to work out.
Modernise a legacy UI5 application with an agent
A developer wants an agent to take an existing UI5 application off deprecated APIs and legacy patterns, following a written procedure rather than whatever the model remembers about the framework.
About the packaged procedure the agent follows. Reading the project, running the UI5 linter and validating the manifest are agent access to your code and come from a server beside the skills; whether the modernised application still works is the developer's to verify, and neither route here claims otherwise.
UI5/plugins-coding-agentsUI5 Modernization is one of three plugins in the repository, published beside the general development plugin and the TypeScript conversion one, so a project being modernised does not load the other two. The repository's own line for it is an autonomous multi-phase workflow that replaces deprecated APIs and removes legacy patterns, and its own README calls it a toolkit for modernising SAPUI5 and OpenUI5 applications. It installs as a plugin into Claude Code or GitHub Copilot, with a command for each.
Conditions: [@ui5/mcp-server](artifact:ui5-mcp-server) is present; the plugin's README states it has to be installed by hand when the skills are installed on their own
Remaining work: Point it at a branch rather than at main, since the workflow is described as autonomous and multi-phase. What it reads of the project, the linter it runs and the manifest check come from @ui5/mcp-server, and reviewing the result is a person's step.
Restyle a UI5 Web Component without breaking on the next release
A developer wants an agent to restyle a UI5 Web Component through the surfaces the library documents, rather than reaching into its shadow DOM in a way that stops working when the component changes.
About the styling rules the agent is handed. Building and publishing a theme is UI theme designer's own job, and whether a particular override survives a given release is between the developer and the component's changelog. Nothing here checks a stylesheet.
SAP/ui-theme-designer-plugins-for-coding-agentsIts design-tokens skill carries the SAP Design System and the Fiori design tokens, including parameter inheritance and which theming parameters specific UI components use. A CSS variable override is only as good as knowing which variable the component consumes, and that is the fact this plugin states and a component's public API does not.
Remaining work: Install it as a plugin in Claude Code or GitHub Copilot, each with its own command, or through the skills command line. It states no UI5 flavor of its own, so whether its parameter mapping covers the Web Components library as well as SAPUI5 controls was not established.
UI5 Web Components agent skillsThe styling skill, one of two shipped under skills/ in the components' own repository. It names four ways in, CSS shadow parts, CSS custom states, CSS variables and tag-level styling, says to use documented shadow parts only, and names the deprecated piercing selectors as not working rather than as discouraged. Living in the library's repository is what ties the guidance to the version of the components it describes.
Remaining work: Get the skill in front of the agent. Nothing read in the components' repository on 2026-10-15 names a client the two skills install into, so how they are loaded is the reader's to establish.
sap-fiori-guidelinesIt states the Web Components flavor in its own frontmatter and its reference files cover colours and typography, so a reader who has it installed has design rules in the session. What was not established is whether it says anything about applying them from outside a shadow root, which is the part of this outcome that goes wrong. Listed so the entry reads as looked at and not established, rather than as ruled out.
Remaining work: Read the colours-and-typography reference file and the Web Components passages beside it.
Content
Show 3 more
Details
Coverage
Designs that place it
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:agent-guidance- JSON
- /capabilities/agent-guidance.json
- MCP
- Connecting an agent