SkillSkilltypeA procedure an agent follows. Indexed here, never written here.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

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.

The two parts of a web component an agent is most likely to get subtly wrong, written by the team that owns the components. **accessibility** covers ARIA, keyboard behaviour and screen readers; **styling** covers CSS shadow parts, custom states and custom properties — the sanctioned way to restyle a component from outside its shadow root, as against the ways that break on the next release. They live in the library's own repository rather than a separate one, so they version with the components they describe.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Provides
Agent guidanceUI5Agent 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.

Who is behind it

UI5UI5OrganisationMaintains this
In the atlas: maintains 8
@UI5
maintainera-z-ivanovPersonContributes to this
In the atlas: contributes to 2
@a-z-ivanov
Cahit GürgücPersonContributes to this
In the atlas: contributes to 3
@aborjinik
Adrian BobevPersonContributes to this
In the atlas: contributes to 10
@adrian-bobev
Ajinkya PatilPersonContributes to this
In the atlas: contributes to 112
@ajinkyapatil8190
Andreas KunzPersonContributes to this
In the atlas: contributes to 19
@akudev
Aleksandar TerzievPersonContributes to this
In the atlas: contributes to 3
@aleksandar-terziev
Alexandar MitsevPersonContributes to this
In the atlas: contributes to 3
@alexandar-mitsev
Ben BrennanPersonContributes to this
In the atlas: contributes to 2
@bbrennanbasis
Benjamin ReimPersonContributes to this
In the atlas: contributes to 9
@BenReim
Julian DaxPersonContributes to this
In the atlas: contributes to 2
@brodo
117 contributors

Before choosing this

Conditions

PracticalFunctional boundary

Two skills, narrowly scoped: nothing here scaffolds an application or answers what a component's API is — that is @ui5/webcomponents-mcp-server, which reads the same library's documentation.

What it declares

Every artifact

Type
Skill
Origin
By SAP

As a skill

Distributed through
does not say

Tasks this contributes to2Beta

Get an agent to follow the SAP Fiori design guidelinesA 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.Freestyle, Fiori elements, Web ComponentsCoversthe accessibility and styling slice, inside the library's own repository
What it does

Two 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.

All options on the Agent guidance page →
Restyle a UI5 Web Component without breaking on the next releaseA 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.Web ComponentsCoversthe sanctioned techniques, and the selectors that do not work at all
What it does

The 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.

All options on the Agent guidance page →

Connections1

README

quoted from UI5/webcomponents under Apache-2.0, read
UI5/webcomponents/README.mdOn GitHub

UI5 icon

CI npm Package Version REUSE status

What are UI5 Web Components?

  • A rich set of enterprise-grade reusable UI elements driven by a lightweight framework (~20K gzipped for the framework part).
  • Suitable for building anything from static web sites to complex web applications.
  • Usable with any current or future web development framework (React, Angular, Vue, etc.).
  • Implement the SAP Fiori design and follow the SAP Fiori Design Guidelines for a consistent UX.
  • Created and maintained by SAP as part of the UI5 product family.

Why use web components?

  • Future-proof: being web standards, they are compatible with any version of any web development framework.
  • Encapsulated: the HTML/CSS in the shadow DOM are protected from interference by the web page and vice versa, making them stable in any environment and suitable not only for apps, but also for libraries and micro-frontends.
  • Elegant: being custom HTML elements, they hide implementation complexity behind a single HTML tag, making them easily usable with the standard DOM APIs.

Where can I see them in action?

More Resources

OpenUI5
1. What is UI5/OpenUI5?

OpenUI5 is an open source JS framework that lets you build enterprise-ready web applications, responsive to all devices, running on almost any browser of your choice. It's based on JavaScript, using jQuery as its foundation and follows web standards. It eases your development with a client-side HTML5 rendering library including a rich set of controls and supports data binding to different data models (JSON, XML and OData).

2. How do UI5 Web Components relate to OpenUI5?

UI5 Web Components…

  • …are not built on top of UI5, but rather lightweight and independent UI elements.
  • …are not a successor of UI5, but rather a complementary offering.
  • …bring the relevant UI5 qualities and SAP Fiori UX to the HTML level, usable with any web framework.

UI5 Web Components are good for…

  • …web applications which already use a different web framework.
  • …static web sites built without web frameworks, to just add a few interactive UI elements.

UI5 remains what it is: the best choice for…

  • …building complete enterprise-ready and responsive web applications.
UI5 Web Components for React

UI5 Web Components for React is a wrapper implementation around UI5 Web Components which makes using them in React even more comfortable. The current version of React (react 18) has some shortcomings when it comes to handling Custom Elements, namely the binding of boolean attributes as well as adding event listeners to custom event names like selection-change. With the help of UI5 Web Components for React, you can use the UI5 Web Components in React as if they were native React components. In addition to that, this library is also offering TypeScript definitions for all components, some complex layout components built on top of UI5 Web Components as well as Charting Components.

UI5 Web Components for Angular

UI5 Web Components for Angular is a wrapper implementation around UI5 Web Components which to make it work with Angular without needing to use the CUSTOM_ELEMENTS_SCHEMA or NO_ERRORS_SCHEMA schemas. Moreover, all Angular-specific features, such as two-way data binding and Angular Form support, work out of the box.

How to Use

  1. Install the NPM module(s) that ship the desired UI5 Web Component(s), for example if you need ui5-button:

    npm install @ui5/webcomponents
  2. Import the desired UI5 Web Component(s) to your app:

    import "@ui5/webcomponents/dist/Button.js"; // loads and defines ui5-button
  3. Use the UI5 Web Component(s) as you would use any HTML element:

    <ui5-button>Hello world!</ui5-button>

    For more information, see Importing UI5 Web Components and Understanding UI5 Web Components APIs.

Typescript Support

TypeScript Support is enabled for both component development and component consumption. Since version 1.11.0, we have been providing TypeScript definitions under an experimental flag, and starting from version 1.19.0, all TypeScript definitions are considered stable.

Is there a CDN I can use?

No, you are expected to import only the components (or other public APIs) that you are going to use and bundle them along with the rest of your application.

Browser and Platform Support

UI5 Web Components are supported by all major modern browsers on the desktop and mobile platforms listed below.

Desktop
Google ChromeMicrosoft EdgeMozilla FirefoxMozilla Firefox ESRApple Safari
Windows (versions 10 & 11)Latest 2 StableLatest 2 StableLatest 2 StableLatestn/a
macOS (Latest 2 versions)Latest 2 StableLatest 2 StableLatest 2 StableLatestLatest 2 Stable
Mobile
Google ChromeApple Safari
Android (Latest 3 versions)Latest 2 Stablen/a
iOS & iPadOS (Latest version)-Latest 2 Stable

Project Structure, Development and Build

This section might be of interest to you mainly if you need to run or build the project locally

Requirements
  • Node.js (version 21 or higher)
  • Yarn (version 1.22 or higher for branches released before v2.15)
  • Yarn v4 is managed via Corepack, run corepack enable in case the yarn command is not found.

Note: The UI5 Web Components project is set up with the Yarn node package manager. This is because it offers functionality that the otherwise preferred npm package manager is currently lacking. Namely, the workspace setting which is currently used in the UI5 Web Components (mono-)repository.

Structure

The UI5 Web Components project contains several packages:

ProjectNPM PackageDescription
mainUI5 Web Components - MainBread-and-butter components (buttons, inputs, popups, pickers, tables, etc.) that are generally found in web apps.
fioriUI5 Web Components - FioriMore semantic components, specific to the Fiori UX (shell bar, side navigation, etc.) that are commonly found in SAP apps.
iconsUI5 Web Components - IconsA rich icons collection (SAP-icons), suitable for enterprise-grade apps
icons-tntUI5 Web Components - Icons TNTA rich icons collection (SAP-icons-TNT), suitable for more technical apps
icons-business-suiteUI5 Web Components - Icons Business SuiteA rich icons collection (BusinessSuiteInAppSymbols), suitable for SAP Fiori apps
baseUI5 Web Components - BaseThe UI5 Web Components framework itself
themingUI5 Web Components - ThemingTheming assets (the default theme and additional accessibility themes)
localizationUI5 Web Components - Localizationi18n functionality and CLDR assets
create-packageCreate Webcomponents PackageAn npm init script for creating new UI5 Webcomponents Packages
playgroundN/AThe playground application
How to run the project locally:
yarn # to install all dependencies
yarn start # to serve the project

A dev server will be started and the browser will open its index URL with a listing of all test pages.

How to start Website (Docs & Samples):

You can start the website app with the following commands:

yarn # to install all dependencies

# start the playground from the project root
yarn start:website

# open http://localhost:3000/webcomponents/nightly/

Note: If you wish to manually install dependencies & run the Playground you can check out our in depth tutorial

Production Build

To build the UI5 Web Components project, run the following commands:

yarn # to install all dependencies
yarn ci:releasebuild # to build the project

Afterwards, you can find the build output in the dist folder of the corresponding package folder. For example, to find the Button component (that belongs to the main package), look inside the packages/main/dist folder.

Limitations

None as of 1.24.0

Known Issues

No major bugs known. To report an issue or view the currently open issues, click here.

Support

We welcome all comments, suggestions, questions, and bug reports. Please follow our Support Guidelines on how to report an issue, or chat with us in the #webcomponents channel of the OpenUI5 Community Slack.

Contribute

Please check our Contribution Guidelines.

Apache-2.0, read
Agent guidance
  1. DanKromp/skillOverflowCollection of 41 agent skills, 37 for SAP development tasks
  2. scaffold-fiori-ai-bridgeAgent skill generating a Joule Frontend Actions bridge for UI5 apps
  3. sap-odata-explorerRust CLI and desktop app for exploring SAP OData services
  4. WerkbankLocal desktop workspace for AI conversations with SAP connectors
  5. SAP Power for KiroSAP skills for the Kiro IDE
  6. SAP Developers MCPHosted MCP server of developers.sap.com tutorials and missions
  7. sap-fiori-guidelinesAgent skill built from the Fiori Design Guidelines
  8. SAP/ui-theme-designer-plugins-for-coding-agentsAgent plugin on the SAP Design System and theming parameters
  9. secondsky/sap-skillsForty SAP development plugins for coding agents
  10. UI5/plugins-coding-agentsUI5 plugins for coding agents

Details

Sources3
sap-ai-mcp-serversdiscovered herechecked
github.com/UI5/webcomponentstree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viasap-ai-mcp-servers
first seen in the atlas
ecosystem and domainui5, ai-and-agents
Flavors1
Web Components
“description: How to make UI5 Web Components applications accessible.” — UI5/webcomponents — skills/accessibility/SKILL.mdchecked
Contributors117
Show 93 more

From the repository’s contributor list, .

History in the atlas2
  1. Entered 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. Entered as its own artifact rather than as a block on the library, which the corpus does not yet hold — the same shape fiori-mcp has inside SAP/open-ux-tools.
  2. First seen.
For your agent
Ref
artifact:ui5-webcomponents-agent-skills
JSON
/artifacts/ui5-webcomponents-agent-skills.json
MCP
Connecting an agent