Agent guidance
Narrows to the application somebody wrote by hand, where the question is which pattern an agent should follow and which it should take out. 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 answers both halves and keeps them apart, with one plugin for creating and developing and a second whose whole job is replacing deprecated APIs in a project that already exists, 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 answers the day-to-day pieces as separate skills: data binding, custom controls, i18n and testing.
Showing artifacts, examples and content with confirmed Freestyle applicability. View All UI5
Overview
Two of the door's SAP-published sets state this flavor. 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 is written for creating UI5 projects, replacing deprecated APIs in an existing one and converting a JavaScript project to TypeScript, 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 SAPUI5 as what full Fiori applications on BTP and S/4HANA are built with.
Not covered: At the framework rather than the project. Both are instruction sets: the project read, the UI5 linter and the manifest check belong to @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, and the plugins state that installing the skills on their own leaves that server to be installed by hand.
The door's own independent entry, 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, states no flavor, and the collections that do state a UI5 flavor state Fiori elements instead, so the community presence here rests on a collection that states no flavor and whose own skill list is freestyle UI5.
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 serves this door from CAP and states no flavor, so it answers in all of them. Its own skill list names UI5 data binding, custom controls, i18n and testing as separate skills, which is freestyle work by any reading.
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.
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