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, 2 of 3 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
One artifact stands
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.