How to make UI5 Web Components applications accessible. Covers accessibility APIs (accessibleName, accessibleNameRef, accessibleDescription, accessibleRole, accessibilityAttributes), label-input relationships, invisible messaging, keyboard handling, high contrast themes, and screen reader support. Use when the user asks about ARIA attributes, screen readers, keyboard navigation, accessibility properties, or making their app accessible.
AI Skills Library
Browse skills, plugins, marketplaces, and MCP servers installable with a single command.Verify and configure SAP AI Core credentials, retrieve auth tokens, and manage resource groups. Runs a setup health check, resolves authentication errors, and lists, creates, updates, or deletes resource groups. Use when checking whether AI Core is set up, configuring credentials, getting a Bearer token, or managing resource groups.
Manage the full SAP AI Core deployment lifecycle: scenarios, executables, configurations, and deployments. Lists and inspects scenarios and executables, creates configurations, creates, lists, stops, deletes, or patches deployments, fetches deployment logs, and removes duplicate LLM deployments. Use when managing AI Core deployments and their configurations.
Generate working Java boilerplate for SAP GenAI Hub using the SAP AI SDK for Java (com.sap.ai.sdk). Covers chat completion, streaming, multi-turn conversations, prompt templates, content filtering, data masking, embeddings, RAG/grounding, prompt registry, and Spring Boot streaming. WHEN: user asks for Java or Kotlin code that calls a GenAI Hub model, wants a Java starter project, asks how to use com.sap.ai.sdk in their app, or asks how to integrate AI Core into a Spring Boot or plain Java application. DO NOT USE FOR: JavaScript/TypeScript code — use `aicore-sdk-js`.
Generate working TypeScript/JavaScript boilerplate for SAP GenAI Hub using @sap-ai-sdk/orchestration, @sap-ai-sdk/foundation-models, @sap-ai-sdk/openai (native OpenAI SDK), @sap-ai-sdk/langchain (LangChain), @sap-ai-sdk/document-grounding (RAG), @sap-ai-sdk/prompt-registry, @sap-ai-sdk/llm-batch (batch jobs), @sap-ai-sdk/rpt (tabular prediction), or @sap-ai-sdk/context-registry (data destinations, tabular artifacts, scenario configurations). WHEN: user asks for TypeScript, JavaScript, Node.js, or JS/TS code that calls a GenAI Hub model, wants a TypeScript starter project, asks how to use @sap-ai-sdk in their app, asks how to use LangChain (JS/TS) with SAP AI Core, or wants JS/TS for RAG/document-grounding, prompt templates, batch LLM jobs, tabular (RPT) prediction, or managing data destinations / tabular artifacts / scenario configurations via the Context Registry. DO NOT USE FOR: Java code — use `aicore-sdk-java`.
Use when reimagining, shaping, or reviewing the initial high-level architecture of an SAP AI solution or agent, including numbered capability progression and an AI Native Solution Brief grounded in North Star layers, AI Golden Path, and SAP reference architectures.
Clean up a deployed SAP appFront (Application Frontend) application. Undeploys from Cloud Foundry (optionally deleting service instances and keys) and removes the local output folder if applicable. Every destructive step requires explicit user confirmation. Use when the user asks to clean up, remove, or tear down an appFront app.
Migrate SAP BTP HTML5 applications to the appFront (Application Frontend) deployment model. Handles migration from SAP Neo HTML5 apps, html5-apps-repo with managed approuter, and standalone approuter (approuter.nodejs with localDir routes). Supports Cloud Foundry and Kyma runtimes with XSUAA or IAS authentication. Produces updated mta.yaml, xs-app.json, and xs-security.json files. Use when the user asks to migrate, convert, or move an HTML5 app to appFront.
Validate SAP appFront (Application Frontend) application configuration for correctness and deployment readiness. Checks mta.yaml structure, xs-app.json routing, xs-security.json scopes, service bindings, and CDM configuration, and can optionally validate the live deployed app via afctl and a browser. Use when the user asks to validate, check, or verify an appFront application.
Creates and manages custom SAP Automation Pilot catalogs. Use when a user wants a new catalog, changes its metadata, or requests catalog deletion. Discovery owns finding commands and Inputs within catalogs.
Calls the SAP Automation Pilot REST API through the verified, prebuilt autopi CLI. Use when configuring Bearer authentication, choosing API calls, or validating request payloads. Shared CLI transport for every Automation Pilot skill.
Authors and maintains SAP Automation Pilot commands and composite automations on the tenant. Use when a user wants to create a reusable command, build an orchestration flow (HTTP calls, scripts, polling, batching, conditionals), or change an existing command's contract, executor flow, expressions, or error handling. Also use for production-readiness reviews and local-only command definitions.
Validates the configured SAP Automation Pilot connection and reports its non-secret account summary. Use when a user wants to test connectivity, confirm which tenant is configured, or inspect effective access.
Finds and evaluates existing SAP Automation Pilot catalogs, commands, child dependencies, and reusable Inputs. Use when a user wants to locate something to run, check for an existing capability before building, identify reusable building blocks, or understand a command's contract and behavior. Do not use to create, change, or execute content.
Crafts, explains, and debugs SAP Automation Pilot dynamic expressions against representative input data. Use when a user wants to write a $(...) expression or responseBodyTransformer pipeline, diagnose an expression that returns an unexpected or empty result, or build a non-trivial expression while authoring or repairing a command. Do not use for jq unrelated to Automation Pilot.
Runs SAP Automation Pilot commands and operates their executions. Use to trigger/monitor runs or webhooks, inspect execution data, diagnose failures, analyze history, request single/bulk actions or operator choices, and delete execution history. Do not use to repair command definitions or schedules that failed to trigger.
Creates and manages reusable SAP Automation Pilot Inputs that store configuration and credentials. Use when a user wants to create, change, rotate, explain, or delete an Input. Do not use merely to find an existing Input for a command.
Creates and manages SAP Automation Pilot MCP servers with simplified tool contracts and reusable Input bindings. Use to publish commands as tools, verify injected configuration and client schemas, or change server and tool availability. Command Authoring owns backing-command changes; Executions owns run diagnosis.
Clarify an SAP Automation Pilot design through a structured interview and produce an implementation-ready specification.
Schedules SAP Automation Pilot commands for one-time or recurring execution and manages existing schedules. Use when a user wants to create, inspect, explain, update, enable, disable, or delete a scheduled execution, or diagnose why a schedule did not trigger. Do not use to troubleshoot a command run that the schedule successfully created.
Validates, applies, and interprets SAP Automation Pilot tags. Use when selecting regular or feature tags, configuring priority, retention, auto-abort, or execution logging, filtering resources by tag, or interpreting tag inheritance, origin, and execution lineage from service tags.
Builds, debugs, and optimizes LeanIX automations using built-in actions when possible and scripts only when needed. Covers trigger types, action configuration, script templates, API deployment via MCP, error patterns, and multi-automation strategies. Use when creating new automations, debugging failing scripts, understanding automation triggers, deploying via API, converting Azure Functions, syncing subscriptions between fact sheets, managing tags based on relations, working with GraphQL mutations, auditing workspace automations, or transferring automation ownership.
Comprehensive SAP BTP command line interface (btp CLI) assistant for generating commands, automating multi-step workflows, and troubleshooting errors. Use this skill whenever the user mentions "btp", "BTP CLI", "SAP BTP command line", subaccount management via CLI, entitlement assignment via terminal, service instance creation with btp, role collection assignment from the command line, or any task involving the SAP Business Technology Platform CLI — even if they just say something like "set up my BTP subaccount" or "how do I log in to my global account from the terminal". Also trigger when the user asks about scripting or automating SAP BTP operations, parsing btp output with jq, or managing Cloud Foundry / Kyma environments through the btp CLI.
Build, debug, and create LeanIX Calculations — populate computed fields from other fields and relations. Use when creating new calculations, debugging errors, understanding calculation capabilities, managing workspace calculations, or analyzing existing calculations. Covers target field types, field access patterns, relation data, templates, error patterns, and best practices.
Add a remote service integration to an existing CAP Node.js application using the Calesi pattern. Imports external APIs (from other CAP apps or OData/S4 sources), creates consumption views, wires up delegation and data federation handlers, and validates the result with cds watch. Use when a developer wants to consume an external service in their CAP app.
Expert guidance for building and extending CAP (Cloud Application Programming Model) applications in either Node.js or Java. Covers project initialization, CDS modeling, declarative annotations, and custom handler best practices for both runtimes. Use when building a new CAP app, extending an existing one, or reviewing CAP code for correctness and idioms — regardless of whether the stack is Node.js or Java.
Manage the lifecycle of multi-tenant SAP CAP applications on Kubernetes using CAP Operator custom resources (CAPApplication, CAPApplicationVersion, CAPTenant, Domain, ClusterDomain). Use when deploying, upgrading, configuring domains, rotating credentials, or troubleshooting CAP Operator-managed apps.
Run an interactive CAP trivia quiz. Picks a topic, searches the CAP documentation via MCP, and asks multiple-choice questions using the question tool. Optionally accepts a topic and difficulty. Use when a developer wants to test or deepen their CAP knowledge.
Upgrade a CAP project to the latest CDS version. Drives the cds upgrade CLI for CDS 10+ (pattern detection, false-positive filtering, fix categorisation) and handles manual upgrades for earlier versions (major jumps like 7→8, 8→9 as well as minor/patch updates). Use when a developer needs to upgrade CDS in a CAP project, already has a cds upgrade report, or wants to move to a newer CDS version.
Comprehensive Cloud Foundry CLI (cf CLI v8) assistant for generating commands, automating app deployments, managing services, and troubleshooting errors. Use this skill whenever the user mentions "cf", "cf cli", "Cloud Foundry", "cf push", "cf login", "cf target", app deployment to CF, service binding, buildpacks, routes, domains, orgs and spaces, manifests, or any task involving the Cloud Foundry command line — even if they just say something like "push my app" or "how do I bind a service". Also trigger when the user asks about scaling apps, managing environment variables in CF, creating user-provided services, rolling deployments, SSH into app containers, or writing CF manifests.
Use this skill when the user asks questions about SAP Clean Core Data — including what clean core data is, the five data pillars (data strategy, data governance, data quality, data volume efficiency, data protection), master data management with SAP Master Data Governance, data quality dimensions and the Data Quality Index, data profiling with SAP Information Steward, data volume efficiency and tiering, data lifecycle management and archiving with SAP ILM, data protection principles, SAP Business Data Cloud, SAP Datasphere, SAP Master Data Integration, SAP One Domain Model, the data product economy, or how to achieve clean data as part of RISE with SAP. Also use when the user asks about data KPIs (data volume efficiency, data quality index), governance maturity practices (DAT-01 through DAT-05), or how the RISE with SAP Methodology Dashboard measures data KPIs. For the full dashboard reference, use `clean-core-general`. For broad clean core overview questions, use `clean-core-general` first.
Use this skill when the user asks questions about SAP Clean Core Extensibility — including extension levels (A–D), on-stack vs. side-by-side extensibility, ABAP Cloud development model, ATC setup, KPI measurement (clean core share, technical debt score, unused code share, business modifications), Governance & Maturity Assessment practices (EXT-GOV-01 through EXT-SYS-05), RISE with SAP Methodology, Project Kernseife, the SAP API Policy, SAP Build and Joule Studio, or Get Clean / Stay Clean patterns. Also use when the user asks about the RISE with SAP Methodology Dashboard Extensibility section — Technical Debt Score, Clean Core Level distribution (A/B/C/D), Execution of Customer Objects, Business Modifications, Unused Customer Objects, ATC level mapping, the Customer Objects deep-dive, the Business Modifications deep-dive, or Object Type Harmonization (effective August 2026). For the full dashboard reference, use `clean-core-general`. For broad clean core overview questions, use `clean-core-general` first.
Generates a Clean Core ATC Assessment Dashboard from an SAP ATC findings ZIP export. Produces a self-contained HTML report in SAP Horizon look & feel covering: Technical Debt Score, Potential Score (successor-aware), Clean Core Level Distribution (Level B/C/D per object using worst-finding logic), top objects and packages by debt score, top objects by Level D (P1 error) findings, top referenced SAP objects by impact, and per-package top-3 referenced SAP objects. Use this skill whenever the user provides or mentions an ATC findings ZIP file, wants to analyse their clean core technical debt, asks for a clean core dashboard, wants to understand their Level D / Level C distribution, or asks about technical debt score, potential score, or successor-available findings.
Use this skill when the user asks broad or introductory questions about SAP Clean Core — including what clean core is, why it matters, the five principles (Extensibility, Integration, Data, Business Processes, Operations), the Autonomous Enterprise vision, RISE with SAP Methodology, general KPI measurement across all principles, the cross-principle Governance & Maturity Assessment, how to start a clean core journey, or how to explain clean core to stakeholders. Also use when the user asks about the RISE with SAP Methodology Dashboard in SAP Cloud ALM — what it is, what it measures, how to set it up, the System View, the Operations View, the deep-dive views, data collection tools, or dashboard FAQ topics. Also use when the question spans multiple principles. For deep questions on a single principle, use the principle-specific expert skill.
Use this skill when the user asks questions about SAP Clean Core Integration — including what clean core integration is, the four integration levels A–D, the three architectural patterns (SAP Integration Suite, API-managed connectivity, event-driven architecture), the SAP API policy, integration design guidelines, the ICoE, the SSB, SAP ISAM, stay-clean and get-clean journeys, modernization of IDocs/RFCs/BAPIs, SAP LeanIX as integration repository, end-to-end monitoring with SAP Cloud ALM and AIF, SAP Integration Suite capabilities, SAP Master Data Integration, SAP Datasphere, or the clean core classification of any integration technology. Also use when the user asks about integration KPIs, governance maturity practices (INT-01 through INT-06), or how the RISE with SAP Methodology Dashboard measures integration KPIs. For the full dashboard reference, use `clean-core-general`. For broad clean core questions, use `clean-core-general` first.
Use this skill when the user asks questions about SAP Clean Core Operations — including what clean core operations is, the four cornerstones of clean operations, Conway's Law and its impact on SAP transformations, the Customer Centre of Expertise (cCOE), Solution Standardization Board (SSB), Operations Control Center (OCC), SAP Activate and RISE with SAP Methodology, governance and operational practices (OPS-01 through OPS-08), the six Operations KPI categories, software stack currency, test management, software delivery efficiency, SAP Cloud ALM, SAP Focused Run, SAP Secure Operations Map, or the Autonomous Enterprise vision. Also use when the user asks about the RISE with SAP Methodology Dashboard Operations View — the Operations Score, Security score, System Health score, or Operations Setup score and their metrics, SLAs, and calculation formulas. Also use when the user asks about KPIs or governance maturity for the operations dimension. For broad clean core questions, use `clean-core-general` first.
Use this skill when the user asks questions about SAP Clean Core Business Processes — including what the business processes principle is, business process management (BPM), the fit-to-standard concept, SAP Activate methodology phases (Discover/Prepare/Explore/Realize/Deploy/Run), delta requirements, fit/gap classification (F-SC, F-VS, F-EC, G-EC, G-RP, G-EP, G-EN, G-ET, G-AN), the Solution Standardization Board (SSB), Key Decision Documents (KDDs), standard process archetypes, SAP content for fit to standard, the recommended tools (SAP LeanIX, SAP Signavio Process Transformation Suite, SAP Cloud ALM), the 4 process KPIs (Fit-to-Standard Alignment, FTS Alignment – Gaps, Alignment to Clean Core, Alignment to S/4HANA Target Architecture), or Governance & Maturity Assessment practices for Business Processes (PRO-01 through PRO-05). For broad clean core overview questions, use `clean-core-general` first. For the RISE Dashboard reference, use `clean-core-general`.
Fix HTML bootstrap parameter issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: - `no-deprecated-api` - For missing/deprecated bootstrap parameters (async, compat-version, animation, binding-syntax, etc.) - `no-deprecated-theme` - For deprecated theme values in data-sap-ui-theme - `no-deprecated-library` - For deprecated libraries in data-sap-ui-libs Trigger on error messages containing: "Missing bootstrap parameter", "Abandoned bootstrap parameter", "Redundant bootstrap parameter", "deprecated value", "bootstrap" Automatically applies safe fixes to HTML files containing UI5 bootstrap script tags.
Fix Component.js async configuration issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: - `async-component-flags` - For missing IAsyncContentCreation interface, missing manifest declaration, redundant async flags, async:false errors - `no-removed-manifest-property` - For async flags in inline manifest v2 Trigger on Component.js files with errors about async loading, IAsyncContentCreation, manifest declaration. Automatically adds the IAsyncContentCreation interface and configures manifest properly.
Fix Control renderer issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: - `no-deprecated-control-renderer-declaration` - For missing renderer declaration, string-based renderer declaration, implicit renderer auto-discovery (removed in modern UI5) - `no-deprecated-api` - For missing apiVersion:2 in renderer objects, missing IconPool import when using oRm.icon(), deprecated rerender() override. NOTE: For Library.init() apiVersion errors, use fix-library-init instead. - `ui5-class-declaration` - For non-static renderer property in ES6 classes Trigger on: "missing a renderer declaration", "Deprecated declaration of renderer", "deprecated renderer", "apiVersion" (in renderer context), "IconPool", "rerender", "renderer must be a static property" Converts legacy renderer patterns to modern apiVersion: 2 format with proper module imports.
Fix Content Security Policy (CSP) compliance issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `csp-unsafe-inline-script` with message "Use of unsafe inline script" Trigger on: inline JavaScript in HTML files, script tags without src attribute, onclick/onload handlers in HTML. Also use when user mentions 'security headers', 'inline script warning', 'CSP policy', 'unsafe-inline', or 'Content-Security-Policy'. Provides guidance on moving inline scripts to external files for CSP compliance.
Detect and resolve cyclic module dependencies introduced during UI5 modernization. Trigger when user mentions: "cyclic dependency", "circular import", "undefined module at runtime", "lazy require", "sap.ui.require sync", "import cycle", or when a module returns undefined despite a correct import path. Classic symptom: a module is `undefined` at runtime despite a correct sap.ui.define import path. Auto-fixes 2-node cycles (A↔B) by converting the lesser-used edge to lazy sap.ui.require(). Auto-fixes longer chains (3+ nodes) via hub-based approach. Reports unfixable chains to MODERNIZATION-ISSUES.md. Runs as Phase 3, Step 3.3 (final step) after all other Phase 3 steps.
Fix deprecated control/class/interface/type issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `no-deprecated-api` with messages about deprecated class, interface, type, property, or property of class - Messages like "Use of deprecated class '...'", "Use of deprecated interface '...'", "Use of deprecated property '...'" Trigger on: deprecated control usage in JS `new` expressions, deprecated properties in constructor settings, deprecated interfaces/types in metadata, deprecated controls/properties in XML views, sap.m.MessagePage modernization to IllustratedMessage. Use this skill whenever you see 'deprecated class', 'deprecated property', 'deprecated interface', or 'deprecated type' in linter output, even if the user doesn't explicitly mention deprecation. Provides replacement guidance for deprecated UI5 controls and their properties.
Handle Fiori Elements V2 controller extensions during UI5 modernization. Use this skill when: - Extension controllers use `sap.ui.controller()` AND the manifest has a matching `controllerName` entry (Case B → report only, do not modernize) - Extension controllers use `Controller.extend()` with manifest `controllerName` registration (Case B → report only, do not modernize) - Code contains `registerControllerExtensions` calls (Case A → ControllerExtension.extend + override) - Manifest.json has `sap.ui5/extends/extensions/sap.ui.controllerExtensions` with `controllerName` entries Case B (plain object) is by far the most common. For Case B, do NOT modify controller files — report them and move on. Case A requires actual code modernization. For plain controller definitions in custom (non-Fiori-Elements) apps where `sap.ui.controller()` is just defining a standalone controller, use `fix-js-globals` (Case 9) instead.
Fix JavaScript `no-globals` errors that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `no-globals` rule with message "Access of global variable '...' (...)" in JS files Cases handled (linter CANNOT auto-fix): - Assignments to global namespaces: `sap.myNamespace = {...}` - Global namespace assignment/read inside sap.ui.define - Delete expressions: `delete sap.something` - sap.ui.core.Core direct access (class vs singleton) - jQuery/$ globals: add `sap/ui/thirdparty/jquery` — do NOT replace jQuery API calls - jQuery.sap.* utilities: replace with dedicated modules - Conditional/probing access: `if (sap.ui.something)` - Custom namespace definitions that aren't UI5 modules - sap.ui.controller() factory → Controller.extend (NOT Fiori Elements extensions) - jQuery.sap.declare/require: legacy modules without sap.ui.define Trigger when: "fix no-globals", "global variable error", "sap.ui.getCore", "jQuery.sap" Converts global namespace access to proper sap.ui.define module imports.
Fix Library.init() apiVersion issues and modernize enums to DataType.registerEnum. Use this skill when linter outputs: - `no-deprecated-api` with message "Deprecated call to ... Use the {apiVersion: 2} parameter instead" Trigger on library.js files with errors about: "Deprecated call to", "Lib.init", "Library.init", "{apiVersion: 2} parameter" Adds apiVersion: 2 to Library.init() calls and modernizes enum definitions to use DataType.registerEnum, which is required for type validation when using apiVersion: 2.
Fix runtime-breaking patterns in JS files that the UI5 linter does NOT report. Use this skill when: - Tests fail after modernization with "ReferenceError", "TypeError: Cannot read properties of undefined", or "X is not defined" - The linter shows zero remaining errors but tests still crash at runtime - Phase 3, Step 3.2 of the modernize-ui5-app workflow (runs after the parallel globals batch, before fix-cyclic-deps) - User mentions "runtime errors after modernization", "test failures after modernization", "global namespace still used" - After running fix-js-globals and fix-cyclic-deps, but tests STILL fail - User sees "X is not a constructor" or module loading errors in test output The linter only checks sap.* globals in JS. App-specific namespace patterns (e.g., com.example.app.utils.Module) are invisible to it. This skill detects and fixes those across ALL JS files — app source AND test. NOTE: App-namespace globals in XML files are handled by `fix-xml-globals` — NOT by this skill.
Fix manifest.json issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: - `no-outdated-manifest-version` - For _version not being 2.x - `no-legacy-ui5-version-in-manifest` - For minUI5Version below 1.136 - `no-deprecated-library` - For deprecated libraries in dependencies - `no-deprecated-component` - For deprecated components in dependencies - `no-deprecated-api` - For deprecated view types, resources/js, deprecated model types - `no-removed-manifest-property` - For async flags in manifest v2 Trigger on manifest.json files with errors about version, libraries, components, view types. Automatically updates manifest.json to be modern UI5 compatible.
Fix partially deprecated API usage that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `no-deprecated-api` for Parameters.get, JSONModel.loadData, Mobile.init, ODataModel.v2.createEntry, View.create, Fragment.load, Router constructor - `unsupported-api-usage` for string formatter in JS bindings Trigger on: Parameters.get without object param, JSONModel.loadData with bAsync=false, Mobile.init with homeIcon, createEntry with batchGroupId, View.create/Fragment.load with non-XML type, Router without async:true, formatter as string in JS. Provides specific fix patterns for each partially deprecated API variant.
Fix pseudo module and implicit global issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `no-pseudo-modules` with messages about deprecated enum or DataType pseudo module access - `no-implicit-globals` with messages about module not exported by library or OData globals Trigger on: direct enum imports (sap/ui/core/BarColor), direct DataType imports (sap/ui/core/CSSSize), library.EnumName access, odata.compare/fillUriTemplate/uriEncode in bindings. Provides guidance on proper module imports for enums, DataTypes, and OData expression addons.
Fix deprecated `sap.ui.table.Table` row properties that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `no-deprecated-api` with messages about `visibleRowCountMode`, `visibleRowCount`, `rowHeight`, `fixedRowCount`, `fixedBottomRowCount`, or `minAutoRowCount` Trigger on: deprecated row-related properties on sap.ui.table.Table in JS or XML, modernization to rowMode aggregation. Converts deprecated flat properties to a structured `rowMode` aggregation using `sap.ui.table.rowmodes.Fixed`, `Interactive`, or `Auto`.
Fix XML view/fragment issues that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs these rules: - `no-globals` - For ALL global variable access in XML views — sap.*, jQuery.*, AND app-namespace globals (e.g., com.example.app.utils.Handler.onPress, my.app.formatter.method) - `no-ambiguous-event-handler` - For event handlers without dot prefix or local name - `no-deprecated-api` - For legacy template:require syntax (space-separated) Trigger on XML view/fragment files with errors about global variables, event handlers, formatters, type references in bindings, factory functions, or template:require. Automatically adds core:require declarations, fixes event handler prefixes, and handles .bind($control) for functions that use 'this'. IMPORTANT: The linter reports app-namespace globals in XML under `no-globals` — these MUST be fixed by this skill, NOT deferred to fix-linter-blind-spots. For native HTML or SVG in XML views, use the fix-xml-native-html skill instead.
Fix native HTML and SVG usage in XML views/fragments that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: - `no-deprecated-api` with message "Usage of native HTML in XML Views/Fragments is deprecated" - `no-deprecated-api` with message "Deprecated use of SVG in XML View or Fragment" Trigger on: HTML elements in XML views (html:div, html:span, html:a), SVG elements in XML views, xmlns:html namespace usage. Provides guidance on replacing native HTML with UI5 controls and SVG with UI5 icons or custom controls.
List and explore foundation models available in the SAP AI Core Generative AI Hub: browse providers, model names, versions, capabilities, and executable IDs, and get curl inference examples for deployed models. Use when discovering available models, finding an executable-id or model-name for deployment, or generating inference examples such as chat completions, embeddings, or image generation.
Configure and use the SAP AI Core Orchestration service: build prompt templates, add content filtering, set up document grounding (RAG) pipelines, and call models via the Harmonized API. WHEN: user asks about the orchestration service, Harmonized API, prompt templating with variables, content filtering, grounding, RAG pipeline, document grounding, or building a pipeline that wraps an LLM. DO NOT USE FOR: creating an orchestration deployment — use `aicore-lifecycle-management` for that; credential setup — use `aicore-admin-resources`; browsing or deploying foundation models directly without a pipeline — use `genai-hub-foundation-models`; direct LLM inference without a pipeline — use `aicore-sdk-java` or `aicore-sdk-js`.
Run GenAI evaluations on SAP AI Core: benchmark LLMs and prompts against a test dataset using system-defined and custom (LLM-as-judge) metrics, then retrieve aggregate results. Supports all three evaluation types — prompt registry, orchestration registry, and grounding (RAG) orchestration registry. WHEN: user wants to evaluate or benchmark an LLM / prompt / orchestration config, run a GenAI evaluation, create or list evaluation metrics, define a custom LLM-as-a-judge metric, create a prompt template (prompt registry) or an orchestration-registry config (with or without grounding) for evaluation, create an evaluation configuration or execution, or fetch evaluation results / scores for an execution. DO NOT USE FOR: agent evaluation via the offline aeval service — use `aeval-offline-evaluation`; building a production orchestration/RAG pipeline for inference — use `genai-hub-orchestration`; generic executions, deployments, or artifacts unrelated to evaluation — use `aicore-lifecycle-management`; credentials, resource groups, or object stores — use `aicore-admin-resources`.
Manage the SAP AI Core Context Registry (TCR) — data destinations (HDL connections), tabular artifacts, and scenario configurations — and interactively build and send tabular prediction requests to the SAP AI Core Tabular Prediction service (sap-rpt-1-small / sap-rpt-1-large). Use when working with the context registry, TCR, HDL connections, tabular artifacts, scenario configurations, or sap-rpt tabular predictions in SAP AI Core.
Generate and deploy a pro-code AI agent using LangGraph and SAP GenAI Hub, deploy it to SAP BTP Cloud Foundry, create a Joule capability with A2A (Agent-to-Agent) action, and deploy it to Joule. Supports TypeScript (Express or CAP) and Python. Use this skill whenever the user mentions: building a custom agent for Joule, deploying an AI agent to BTP Cloud Foundry, A2A protocol integration with Joule, pro-code agent extensibility, LangGraph agent on SAP BTP, connecting an external agent to Joule, "bring your own agent" for Joule, creating a Joule capability with A2A action, CAP agent, MTA deployment, or any combination of LangGraph/A2A/Joule/BTP/Cloud Foundry/CAP in an agent development context. Also trigger when the user wants to scaffold, modify, or redeploy an existing A2A agent project.
Comprehensive SAP Joule CLI (formerly sapdas CLI) assistant for managing digital assistants from the command line — compiling capabilities, deploying assistants, running BDD tests, linting, and troubleshooting errors. Use this skill whenever the user mentions "joule cli", "sapdas", "joule compile", "joule deploy", "joule test", "joule login", "joule lint", digital assistant deployment, capability compilation, DAAR files, RTA artifacts, or any task involving the Joule command line interface — even if they just say something like "deploy my assistant" or "how do I log in to Joule from the terminal". Also trigger when the user asks about testing Joule capabilities with Cucumber, linking AI assistants, managing deployed assistants, or automating Joule workflows in CI/CD pipelines.
Build and deploy an application to an open-source Kyma cluster with kyma app push (v3) - from local source, a Dockerfile, or a pre-built image, with exposure via APIRule, Istio injection, and env/secret/config injection. Use when the user wants to push, deploy, or expose an app on Kyma.
Use the open-source Kyma CLI (v3) to manage Kyma modules, deploy applications, provision clusters, and run diagnostics on a Kubernetes cluster. Use when the user wants to install Kyma, enable or disable a module, push an app, open the Kyma dashboard, or troubleshoot a Kyma cluster.
Manage an open-source Kyma module through its full lifecycle with the Kyma CLI (v3) - discover, enable, configure, verify, change managed state, and remove. Use when the user wants to enable, install, add, configure, or remove a Kyma module (e.g. Serverless, Istio, API Gateway), pick a module channel, or manage/unmanage a module.
Diagnose a misbehaving open-source Kyma cluster or module using the Kyma CLI (v3) and kubectl. Use when a module is stuck or not ready, an app is failing, Istio or networking is broken, or the user wants to troubleshoot, diagnose, or inspect a Kyma cluster. Also use when kyma module add/delete itself is failing with an error. Do NOT use for pure module lifecycle tasks (add/enable/remove) where no problem is reported — e.g. "add the Istio module" with no error context → use kyma-module-lifecycle instead; "add the Istio module because sidecar injection is broken" → this skill applies for the diagnosis step.
Use when migrating UI5 apps from legacy FLP sandbox to the new sandbox (New Sandbox). Triggers on /modernize-flp-sandbox, mentions of "flpSandbox.html", "sap-ushell-config", or requests to update sandbox configuration.
Modernize QUnit unit tests and OPA5 integration tests to the UI5 Test Starter concept. Use this skill when: - The linter reports `prefer-test-starter` for *.qunit.html or *.qunit.js files - Test HTML files use manual sap-ui-core.js bootstrapping instead of Test Starter's runTest.js/createSuite.js - Test JS files use Core.ready(), Core.attachInit(), or jsUnitTestSuite instead of sap.ui.define - OPA test HTML files exist with per-test Opa5.extendConfig and manual bootstrapping - An AllJourneys.js orchestrator loads OPA journeys dynamically - OPA journeys call `iStartMyUIComponent` instead of `iStartMyAppInAFrame` - User asks to modernize tests, modernize test infrastructure, or adopt Test Starter Handles unit tests (Core.ready removal, sap.ui.define wrapping) and OPA challenges (page-object imports, Opa5 config, journey orchestration, QUnit 1.x assert modernization, in-window-to-iframe launcher migration). Trigger on: prefer-test-starter warnings, test modernization requests, iStartMyUIComponent.
End-to-end workflow for modernizing a UI5 application. Use this skill when: - User wants to modernize their UI5 app - User mentions "UI5 modernization", "modernize UI5 app", "upgrade UI5", "make app modern UI5 compatible" - User asks to "fix all linter errors", "run full modernization", "modernize my UI5 project" This skill runs the modernization in five phases with a verification gate after each phase. The user picks the verification mode once at the start (full autonomous / half autonomous / manual). The agent applies that mode at every gate without re-asking.
SAP Fiori design guidelines for building enterprise applications. Use this skill when designing, building, or reviewing SAP Fiori applications, implementing SAPUI5 or UI5 Web Components, working with SAP enterprise UX patterns, or needing guidance on buttons, forms, tables, object pages, list reports, navigation, messaging, colors, typography, accessibility, AI/Joule integration, or any SAP Fiori UI element. Triggers on mentions of Fiori, SAPUI5, UI5, SAP UX, SAP design system, or enterprise application design following SAP standards.
SAP Fiori for iOS Design Skill — converts Figma designs from the SAP Fiori iOS UI Kit into correct SwiftUI prototype code with Fiori color tokens, typography, animations, and component guidelines. Use this skill when a designer provides a Figma node ID or component name and wants working SwiftUI code, when asking which Fiori iOS component to use, when mapping Figma variants to SwiftUI, or when adding animations and state transitions to iOS prototypes. Triggers on: Fiori iOS, SwiftUI, iOS prototype, Figma to iOS, FioriButton, FioriTheme, animation, interaction, SAP 72, preferredFioriColor, ObjectItem, FioriSwiftUI.
Defines the BTP account topology — subaccounts, regions, and directory groupings.
Analyses application source code or Terraform code to extract infrastructure signals, then enriches specs/scenario.md.
Elicits BTP destination and destination-certificate requirements and writes specs/connectivity.md.
Guides the Terraform state-chunking architecture, persists it to specs/state-architecture.md, and annotates each task with its target directory and file path.
Generates complete, validated Terraform HCL by executing each task in dependency order.
Establishes governance guardrails — infrastructure, regions, naming, runtime environments, service plans, security, and cost controls.
Inspects local project state and recommends the next command in the BTP IaC greenfield flow.
Translates a plain-language setup description into structured BTP infrastructure requirements.
Identifies authentication and authorisation requirements — IdP trust, role collections, and role collection assignments.
Resolves infrastructure requirements into a dependency-ordered list of BTP entitlements, subscriptions, and service instances.
Consolidates landscape, services, trust, and (optionally) connectivity specs into a single dependency-ordered task list.
Read SAP developer tutorial content from the public developers.sap.com API — catalog, navigation, tutorial HTML/JSON, and full-text search. Use when an agent needs to discover, fetch, or search official SAP tutorials, missions, groups, or concepts without authentication.
How to customize and style UI5 Web Components. Covers CSS shadow parts, CSS custom states, CSS variables, and tag-level styling. Use when the user asks about changing component appearance, colors, spacing, theming, or overriding styles.
TRIGGER: questions about the SAP Design System and SAP Fiori design tokens — which themes exist, what value a theme parameter (e.g. sapButton_Background, sapHighlightColor) has in a given theme, how parameters inherit/extend across the theme chain, which parameters a specific UI component (UI5 control, UI5 Web Component, Fundamental Styles component) consumes. SKIP: how-to questions about UI theme designer as a product (creating, publishing, transporting themes — use ui-theme-designer-help).
Provides customer-facing UI theme designer help from help.sap.com (BTP / Cloud Foundry edition). Use whenever you need to check what is — or is not — documented for customers about UI theme designer: setup, user/role management, themes and theme sets (creating, editing, publishing, transporting, fallback), quick/detailed/expert theming, writing themeable CSS for custom UI5 controls, best practices for custom control theme files, theming integrations with Build Work Zone / S/4HANA / SAPUI5 / SAP GUI, UI theme designer service constraints (rate limits, size limits, theming-specific security and permissions, accessibility), theming error messages and troubleshooting, what's-new. Also use for 'is X documented?' or 'what does the help say about Y?' questions. SKIP: questions about which themes or parameters exist or what values they have (use ui-theme-designer-design-tokens). SKIP: tenant-specific operational questions about a running system ("which themes do we have?", "which users are assigned?").
UI5 development best practices and coding standards derived exclusively from official SAP UI5 guidelines. Use when writing UI5 applications to ensure modern, maintainable code following SAP standards. Covers: async module loading (sap.ui.define, ES6 imports, core:require), ComponentSupport initialization, data binding with OData types, i18n management, CSP compliance (no inline scripts), TypeScript event types (UI5 >= 1.115.0), MCP tooling (get_api_reference, run_ui5_linter), CAP integration patterns, and form creation rules (never SimpleForm, always Form with ColumnLayout).
This skill should be used when the user asks to audit, fix, check, review, or improve accessibility, a11y, ARIA, WCAG compliance, landmarks, labeling, heading levels, focus handling, keyboard navigation, keyboard shortcuts, screen reader support, invisible messaging, reading order, or touch / target size in UI5 application files (views, fragments, controllers). Also use when the user creates a new UI5 view, fragment, or controller and wants it to be accessible, or asks whether a specific control (Dialog, Table, Panel, etc.) meets accessibility requirements.
UI5 MDC (sap.ui.mdc) best practices for OData V4 delegate-based controls. Use when creating/troubleshooting MDC FilterBar, Chart, Field, FilterField, ValueHelp, Link, MultiValueField, or Table. Covers delegate pattern, fetchProperties, PropertyInfo, p13nMode, updateBindingInfo, Condition.createCondition, and per-control API reference.
Use when the user asks to "write a QUnit test", "fix a failing QUnit test", "add a QUnit module", "modernize QUnit tests", "migrate from QUnit 1", or mentions QUnit-specific constructs such as assert.async, nextUIUpdate, Core.applyChanges, sinon sandbox, asyncTest, or QUnit.module. Covers coding standards for OpenUI5/SAPUI5 unit test files: const/let over var, arrow functions over .bind(this), async/await over assert.async(), assert.expect() in every async test, sinon.createSandbox(), descriptive test names, beforeEach/afterEach module isolation, nextUIUpdate vs Core.applyChanges rules, try/finally teardown in helpers, QUnit 1 to QUnit 2 globals migration, and non-ASCII character avoidance.
UI5 smart controls (sap.ui.comp) best practices for OData V2 annotation-driven controls. Use when creating/troubleshooting SmartField, SmartForm, SmartFilterBar, SmartChart, SmartLink, SmartMultiInput, or SmartTable. Covers control selection, annotations (ValueList, FieldControl, SemanticObject, UI.* ), mandatory rules, common error patterns, and per-control API reference.
MUST be loaded before any UI Integration Cards (also called UI5 Integration Cards) task — creating, modifying, validating, previewing, or reviewing a card, its `manifest.json`, its Configuration Editor (`dt/Configuration.js`), or any analytical chart configuration. Provides the official guidelines, validation rules, supported chart types, and Configuration Editor patterns.
This skill should be used in any OPA5 task - creating, modifying, extending, debugging, fixing or reviewing an integration test. Use when the user asks to "write an OPA5 test", "add an OPA5 journey", "fix the OPA5 test failure" or mentions OPA5 or its components - opaTest, page object, journey, waitFor.
UI5 table best practices for freestyle applications. Use when creating/troubleshooting any table: sap.m.Table (ResponsiveTable), sap.ui.table.Table (GridTable), TreeTable, SmartTable, or sap.ui.mdc.Table. Covers control selection matrix, mandatory rules, common errors, and per-control API guidance.
A skill for converting UI5 (SAPUI5/OpenUI5) projects to TypeScript.
Build or refresh a "What's New" digest of recently merged pull requests across one or more GitHub repos. Use when asked to produce a changelog, release digest, or weekly "What's New" report from merged-PR history.