Agent guidance
Narrows to the annotations and the floorplan, and it is the one UI5 flavor the independent collections name. The decision here is less which skill writes the application than whether the service behind it is annotated well enough to drive a floorplan at all, which is why 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's list-report checklist belongs beside the generators in 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 and 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 rather than after them.
Showing artifacts, examples and content with confirmed Fiori elements applicability. View All UI5
Overview
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 states this flavor for its project creation, 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 names Fiori elements as what a metadata-driven application over an OData service is built with, with a reference file of its own for the floorplans beside the one for S/4HANA design.
Not covered: At the floorplan and the page type. Neither set states a skill for writing the @UI annotations that drive a list report or an object page against a real service, which is where a generated application either works or does not.
The independent entries that state this flavor serve the door from BTP and do not live behind it. The one of them that reaches a real service, 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, calls itself early-stage in its own README.
This is the one UI5 flavor the independent collections state in their own words, and three of them do. 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 activates its Fiori tools plugin on a request to set up a Fiori elements application, 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 answers a request for a list report over an OData service, 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 reads the other end, checking a service's annotations against a list-report and object-page checklist before an application is generated at all.
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.
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.
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.
Content
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