Build on UI5
Before you build, check what is there. If you find something close, think about contributing to it. If you find nothing, start building.
Check what is there
Search by the use case, not by a package name: the same need often sits under a capability you would not guess. The capability map and Browse hold everything in UI5.
What gets built on UI5
Found something? Contribute
Where an artifact does most of what you need, a fix, a test or a page of documentation reaches everyone who already uses it. Read where it stops and its open and closed issues first: someone may have asked already. Then contribute to a project. These are the places where evidence or a second hand counts most.
Not known yet
- Get an agent to follow the SAP Fiori design guidelines
Not known yet for secondsky/sap-skills, 3 of 4 artifacts cover it
- Get test code for a Fiori elements screen without writing selectors by hand
Not known yet for @openui5/sap.ui.core, 2 of 3 artifacts cover it
- Restyle a UI5 Web Component without breaking on the next release
Not known yet for sap-fiori-guidelines, 2 of 3 artifacts cover it
One artifact stands
- Change promotiongit-env-branches
- Fiori annotations@sap-ux/odata-vocabularies
- Frontend performance@satiroglu/kaev
- Importing and exporting table dataui5-cc-spreadsheetimporter
- Knowing the maintenance status of a releaseui5-task-check-eocp
- Routing and navigation@openui5/sap.ui.core
- Task and approval UIsSAP Task Center
- Vulnerability scanningaudit-summary
Nothing there? Build
Use cases no recorded artifact covers, and capabilities with no artifact in UI5. Unmapped means the atlas holds nothing, not that nothing exists: search once more, then build a library or extension.
Use cases nothing covers
Every assessed use case in UI5 has an artifact that covers it.
Capabilities with no artifact
Read in the atlas
Build and dev-server tooling
- UI Composition with Application Frontend ServiceUI Composition with Application Frontend ServiceWhy shared UI code is hard, and what Application Frontend changes about it. The piece first lays out the three usual answers and what each costs — copying files at development time and repatching every consumer, publishing an npm package and rebuilding every consumer, or hosting the code separately and paying for it in CORS and session handling, or in an extra network hop through a server-side proxy. It then shows a fourth that only this service can do: runtime server-side composition without the hop, configured through routes in the consuming application's xs-app.json, across three cases — a reusable application embedded in a consumer, and two further composition shapes. Read alongside the generator, which scaffolds the mta.yaml, xs-app.json and zipper configuration this model needs.Vadim Tomnikov, published 2026-05-18
- How to consume UI5 custom libraries in BAS or VS CodeHow to consume UI5 custom libraries in BAS or VS CodeConsuming a custom UI5 library from a UI5 application locally, using yarn workspaces to resolve the dependency instead of adjusting the project before every deploy. The post is honest about its own history: the author had asked the question on SAP Community, found a workaround that needed a pre-deploy edit, and only later learned the workspace approach that removes it. Generator-based setup throughout, and 2021-vintage — yarn workspaces, generator-ui5-library and generator-easy-ui5.published 2021-04-06
Generators
- UI5 MCP Server Got Extended for UI Integration Cards GenerationUI5 MCP Server Got Extended for UI Integration Cards GenerationVersion 0.2.1 of the UI5 MCP Server adds three tools for UI Integration Cards: get_integration_cards_guidelines feeds an agent current best practices and API versions, create_integration_card scaffolds a new card project, and run_manifest_validation checks the generated manifest against the schema. The post frames these as closing the same gaps as the server's existing tools — an LLM's outdated or wrong card API knowledge — this time for scaffolding and validating a card rather than a full app.daniel_vladinov, published 2026-01-22
- Give Your AI Agent Some Tools: Introducing the UI5 MCP ServerGive Your AI Agent Some Tools: Introducing the UI5 MCP ServerAnnounces @ui5/mcp-server, SAP's open-source MCP server for UI5 development, and walks through its initial six tools. get_project_info, get_api_reference and run_ui5_linter (which applies UI5 linter fixes) read the project's own version, manifest and code rather than an LLM's training data, which is what agent access to your code explains. create_ui5_app scaffolds a new JavaScript or TypeScript project, standalone or inside an existing CAP application, from templates with pre-configured OData model setups, which is generators.published 2025-09-03
- Useful CAP CDS and Fiori Commands to Accelerate Development and DeploymentUseful CAP CDS and Fiori Commands to Accelerate Development and DeploymentA command-by-command walkthrough of @sap/cds-dk's cds add and fiori add generators: cds add xsuaa writes an XSUAA security configuration from the CDS model's authorization annotations, and cds add hana together with cds deploy --to hana switches persistence from the default SQLite database to SAP HANA Cloud. cds add mta and fiori add deploy-config, from @sap/generator-fiori, build the Cloud Foundry deployment descriptor together, adding a destination-service block and an xs-app.json that routes the Fiori app's calls through a named destination.TiaXu, published 2022-10-19