// Query @ui5/mcp-server before writing SAPUI5 controllers, XML views, control APIs, or model bindings. Triggers on views and controller extensions in app/.
Query @cap-js/mcp-server before writing CDS entities, types, aspects, services, or CAP service handlers. Triggers on schema and service files in db/ and srv/.
Query @sap-ux/fiori-mcp-server before writing CDS annotations, Fiori Elements config, or manifest.json. Triggers on annotation files in app/ and manifests.
| name | sap-ui5 |
| description | Query @ui5/mcp-server before writing SAPUI5 controllers, XML views, control APIs, or model bindings. Triggers on views and controller extensions in app/. |
| paths | ["**/app/**/*.xml","**/app/**/ext/**/*.js","**/app/**/ext/**/*.ts"] |
Before writing, modifying, debugging, or fixing SAPUI5 controllers, XML views, or control bindings, you MUST query the UI5 MCP server and apply its guidance.
Use mcp__ui5__* tools — primarily mcp__ui5__get_api_reference, mcp__ui5__get_guidelines,
mcp__ui5__run_ui5_linter, and mcp__ui5__get_project_info.
mcp__ui5__get_api_reference for control APIs, or mcp__ui5__get_guidelines for project-level patternsmcp__ui5__run_ui5_linter to catch deprecated APIsThis skill covers:
sap.m, sap.f, sap.uxap namespacesapp/**/ext/controller/*.js)sap.ui.define for all modules — no globalsdata-sap-ui-async="true"jQuery.sap.*, sync loading, sap.ui.getCore())this refers to the ExtensionAPI instance