Everything in UI5
Type: 4
Domain
Origin
Signals
More
Group by: Capability
Where it runs
Distributed through
Generates
Run with
Collection of 41 agent skills, 37 for SAP development tasks
SAP skills for the Kiro IDE
Host-specific: outside Kiro the automatic context activation is the part that does not come with it, and what remains is prose you would have to wire in yourself. Breadth over depth by design — thirty-five skills across six product areas is an orientation layer, not a substitute for the focused sets in each.
Agent skill built from the Fiori Design Guidelines
Agent plugin on the SAP Design System and theming parameters
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 skill generating a Joule Frontend Actions bridge for UI5 apps
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
Two agent skills for accessibility and styling of web components
Two skills, narrowly scoped: nothing here scaffolds an application or answers what a component's API is — that is [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server), which reads the same library's documentation.
UI5 plugins for coding agents
Guidance, not access: these are instructions handed to an agent, and what the agent can then read of your project comes from [@ui5/mcp-server](artifact:ui5-mcp-server) or the editor. A modernisation workflow that runs autonomously across a codebase is also a thing to point at a branch rather than at main.
Yeoman generator for Application Frontend config in UI5 libraries
It targets the Application Frontend service only — not the HTML5 application repository — fixes authentication to IAS, and always creates new service instances, so reusing existing ones means editing the generated `mta.yaml` afterwards. Version 0.1.0 is the only release.
npm-init wrapper for the Easy-UI5 Yeoman generator
npm initializer adding wdi5 testing to an existing UI5 app
Yeoman meta-generator for scaffolding UI5 projects
Yeoman generator for UI5 tooling-extension projects
Release and repository quiet for 33 months.
Easy-UI5 generator scaffolding a new UI5 application
Yeoman generator for UI5 custom controls distributed via npm
No published releases; repository quiet for 67 months.
Easy-UI5 generator scaffolding a new UI5 library
Yeoman generator for UI5 libraries wrapping UI5 Web Components
No published releases; repository quiet for 35 months.
Yeoman generator for UI5 projects holding several applications
Not for a single-application project with no deployment configuration: for that the README points to [generator-ui5-app](artifact:ui5-community-generator-ui5-app) instead.
Yeoman generator for a UI5 app that loads a React app
Quiet Release and repository quiet for 39 months.
Functional boundary The scaffold is JavaScript and not TypeScript, and `react-router-dom` and UI5 Web Components are not included; its README leaves both for the project to add.
Easy-UI5 generator scaffolding a TypeScript UI5 application
Generator for a TypeScript UI5 FlexibleColumnLayout app on OData
Easy-UI5 generator scaffolding a TypeScript UI5 library
Yeoman generator scaffolding wdi5 test configuration into a UI5 app
No published releases; repository quiet for 27 months.
Command line generator of UI5 custom controls from html
Release and repository quiet for 29 months.
Chrome extension generating OPA5 or wdi5 tests from recorded journeys
Command line generator of UI5 custom controls from html
Release and repository quiet for 29 months.
Easy-UI5 generator scaffolding a Fiori Launchpad plugin
Easy-UI5 generator for a TypeScript Fiori launchpad plugin
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.