Check and improve ABAP code quality using abaplint and Clean ABAP principles. Use this skill when users ask to check, lint, validate, review, or analyze ABAP code for syntax errors, clean code compliance, code quality, best practices, or adherence to Clean ABAP guidelines. Also use when users ask to set up abaplint, configure abaplint.json, or run abaplint on their ABAP project. Triggers include requests like "check this ABAP code", "lint my ABAP", "run abaplint", "configure abaplint", "is this clean ABAP", "review my ABAP", or "analyze ABAP code quality".

Help with ABAP Cloud development including the 3-tier extensibility model, ABAP Cloud language version restrictions, wrapper patterns for unreleased APIs, clean core principles, and key user vs developer extensibility. Use when users ask about ABAP Cloud, ABAP for Cloud Development, clean core, 3-tier model, tier 1 tier 2 tier 3, wrapper pattern, released APIs, language version, restricted ABAP, embedded Steampunk, developer extensibility, key user extensibility, or ABAP Cloud readiness. Triggers include "ABAP Cloud restrictions", "clean core", "wrapper class", "tier model", "released API alternative", "ABAP language version", "Steampunk", or "extensibility model".

Help with migrating classic ABAP custom code to ABAP Cloud including custom code adaptation, identifying unreleased API replacements, generating wrapper classes for unreleased objects, ATC Cloud Readiness checks, handling incompatible language constructs, and step-by-step migration workflows. Use when users ask about migrating to ABAP Cloud, custom code migration, cloud readiness, unreleased API replacement, wrapper pattern, ATC cloud checks, code adaptation, classic to cloud migration, S/4HANA cloud migration, or clean core compliance. Triggers include "migrate to ABAP Cloud", "cloud readiness check", "unreleased API", "replace with released API", "custom code adaptation", "wrapper for unreleased", "ATC cloud", "clean core migration", "move to tier 1", or "ABAP Cloud compatibility".

Use when building business objects with the ABAP RESTful Application Programming Model (RAP): CDS view entity, behavior definition BDEF, behavior implementation ABAP class, managed RAP, unmanaged RAP, validation, determination, action, draft-enabled, service definition, service binding, OData V4, projection view, business object BO, S/4HANA BTP ABAP environment cloud development.

Skills for SAP ABAP, ABAP Cloud, RAP, CDS, OData, testing, security, migration, and BTP development

Help with modern ABAP SQL features and AMDP (ABAP Managed Database Procedures) including inline declarations, window functions, GROUP BY, HAVING, PRIVILEGED ACCESS, string functions, aggregate expressions, common table expressions (CTE), AMDP classes, AMDP procedures, AMDP table functions, CDS table functions, and AMDP scalar functions. Use when users ask about ABAP SQL, modern SQL, SELECT, window functions, CTE, common table expression, AMDP, SQLScript, AMDP table function, CDS table function, aggregate, GROUP BY, HAVING, UNION, INTERSECT, EXCEPT, PRIVILEGED ACCESS, ABAP SQL expressions, built-in SQL functions, or database procedures. Triggers include "ABAP SQL query", "window function", "CTE", "AMDP", "table function", "GROUP BY", "aggregate", "PRIVILEGED ACCESS", "inline SELECT", or "SQLScript".

Help with ABAP Unit testing including test class setup, assertions, test doubles, mocking frameworks, dependency injection, CDS test environments, SQL test environments, RAP BO test doubles, and test fixtures. Use when users ask about ABAP unit tests, test classes, test methods, CL_ABAP_UNIT_ASSERT, test doubles, mocking, CDS test environment, SQL test environment, RAP testing, ABAP test injection, test seams, behavior-driven testing, TDD in ABAP, test isolation, or writing automated tests for ABAP code. Triggers include "write a unit test", "create test class", "mock a dependency", "test a CDS view", "test a RAP BO", "test double", "assertion", "test fixture", "test isolation", or "ABAP unit".

Help with abapGit workflows including repository setup, cloning, serialization, branching strategies, transport-vs-git workflows, CI/CD integration, and .abapgit.xml configuration. Use when users ask about abapGit, git for ABAP, ABAP version control, abapGit clone, abapGit pull, abapGit push, branching strategy for ABAP, abapGit configuration, serialization, deserialization, transport vs git, gCTS, abapGit CI/CD, or managing ABAP code in git repositories. Triggers include "set up abapGit", "clone a repo", "push ABAP to git", "abapGit branching", "abapGit configuration", ".abapgit.xml", "transport vs git", or "CI/CD for ABAP".

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.

Configure ATC Cloud Readiness and Clean Core checks using the SAP Cloudification Repository for Released APIs. Use when users ask about ATC check variants for cloud readiness, clean core compliance, released API checks, cloudification repository setup, objectReleaseInfo JSON files, SAP Cloud ERP or SAP Cloud ERP Private API validation, or migrating custom code to ABAP Cloud. Triggers include "configure ATC cloud readiness", "set up clean core check", "cloudification repository URL", "released APIs check", or "which JSON file for my S/4HANA version".

Help with ABAP authorization and IAM (Identity and Access Management) including authorization objects, authorization checks, IAM apps, business catalogs, business roles, restriction types, CDS access control (DCL), privilege access annotations, and role-based access in ABAP Cloud and on-premise. Use when users ask about authorization, AUTHORITY-CHECK, authorization object, IAM app, business catalog, business role, restriction type, CDS access control, DCL, access control, privilege annotation, role assignment, PFCG role, S_DEVELOP, or securing ABAP applications. Triggers include "authorization check", "create authorization object", "CDS access control", "IAM app", "business catalog", "business role", "PFCG", "restrict access", or "role-based security".

Discover available commands and catalogs in SAP Automation Pilot via API. Use when you need to find what executors/commands exist, get command definitions, or explore a catalog before generating new commands. Essential for complex command generation involving multiple services.

Generate SAP Automation Pilot commands with dynamic expressions, jq transformations, and composite workflows. Use when creating commands, building orchestration flows, or working with Automation Pilot expressions.

Review production commands, inputs, and catalogs for Automation Pilot. Validates file structure, naming conventions, security requirements, mandatory patterns, and best practices. Use when reviewing .command.json, .input.json, or .catalog.json files.

Manage SAP Automation Pilot content (commands, catalogs, inputs, webhooks, MCP servers) via Content API. Use when importing or exporting commands, deploying MCP servers, listing catalogs, or managing automation content programmatically.

Debug and troubleshoot SAP Automation Pilot execution failures. Use when executions fail, need to investigate errors, check execution health (pass/fail summary), or understand error patterns. Provides error pattern matching with suggested fixes.

Monitor and manage SAP Automation Pilot executions via API. Use when triggering commands, checking execution status, retrieving logs, aborting or pausing executions, or troubleshooting failed runs.

Master the ExecuteScript executor for Automation Pilot commands. Covers script execution parameters, Base64 encoding, timeout/exit code handling, stdin/parameters/environment patterns, and language-specific wrappers (Python, Node.js, PowerShell). Use when building commands that execute shell scripts or custom code.

Master the HTTP executor for Automation Pilot commands. Covers HTTP executor parameters, expression sanitization, timeout/retry configuration, response transformers, and HTTP-specific error handling. Use when building commands that make HTTP/REST API calls.

Create and configure SAP Automation Pilot MCP server definitions and tool configurations. Use when building MCP servers, defining tools, or setting up Automation Pilot MCP configs.

Manage SAP Automation Pilot scheduled executions via API. Use when creating, listing, updating, or deleting schedules for recurring or one-time command execution.

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.

Help with BAdI (Business Add-In) development and the ABAP enhancement framework including new BAdIs, fallback classes, filter-based BAdIs, enhancement spots, enhancement implementations, key user extensibility, classic BAdIs, and the new enhancement framework. Use when users ask about BAdI, BAdIs, Business Add-In, enhancement spot, enhancement implementation, enhancement framework, BAdI filter, BAdI fallback, BAdI definition, BAdI implementation, key user extensibility, custom logic injection, enhancement point, implicit enhancement, explicit enhancement, or extending SAP standard code. Triggers include "create a BAdI", "implement a BAdI", "enhancement spot", "find a BAdI", "BAdI filter", "fallback class", "key user extensibility", "extend standard", or "enhancement framework".

Help with SAP BTP ABAP Environment setup and development including service instance creation, ADT connectivity, communication arrangements, communication scenarios, inbound/outbound services, destination configuration, identity and access management, software components, and first-project scaffolding. Use when users ask about BTP ABAP Environment, SAP BTP ABAP, Steampunk, ABAP environment service instance, ADT connection to BTP, communication arrangement, communication scenario, communication system, outbound communication, inbound communication, destination service, software component, ABAP system on BTP, or cloud ABAP development setup. Triggers include "set up BTP ABAP", "connect ADT to BTP", "communication arrangement", "communication scenario", "create service instance", "ABAP on BTP", "outbound service", or "first ABAP project on BTP".

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.

Use when deploying a SAP CAP application to SAP BTP: MTA descriptor (mta.yaml), Cloud Foundry manifest, Kyma / Kubernetes deployment, HANA Cloud provisioning, HDI containers, service bindings, environment variables, or build/deploy pipelines.

Use when configuring SAP BTP Destination Service: creating destinations in BTP Cockpit, OAuth2ClientCredentials, OAuth2SAMLBearerAssertion, OAuth2JWTBearer, principal propagation, BasicAuthentication, Cloud Connector on-premise connectivity, reading destinations from CAP with cds.connect.to, or testing destinations locally with cds bind.

Generate SAP BTP (Business Technology Platform) solution architecture diagrams as native draw.io (.drawio) files following the official SAP BTP Solution Diagram guidelines (Fiori Horizon design system) and open them via a configured draw.io MCP server. USE WHEN: user asks to create/draw/design/sketch a BTP diagram, BTP architecture, BTP landscape, BTP solution diagram, BTP reference architecture, SAP Business Technology Platform diagram, or wants to visualize SAP BTP services (CAP, Build, Integration Suite, SAC, AI Core, HANA Cloud, Cloud Foundry, Kyma, Workzone, etc.) and their interdependencies in draw.io / drawio / diagrams.net. DO NOT USE FOR: non-BTP architecture diagrams, generic flowcharts, sequence/UML diagrams, or diagrams that should remain in Mermaid/PlantUML.

Use when working with SAP BTP service bindings in CAP or Node.js applications: VCAP_SERVICES structure, cds bind command, hybrid testing, default-env.json, SERVICE_BINDING_ROOT, Kyma ServiceBinding custom resources, service-manager, xsenv, or binding multiple BTP services locally for development.

Use when setting up SAP Build Work Zone: deploying Fiori apps to Work Zone, content providers, CDM (Common Data Model), role assignments, Launchpad tiles, HTML5 app deployment to BTP, xs-app.json app router configuration, managed app router, or integrating CAP + Fiori apps with SAP Build Work Zone standard edition.

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.

Skills for SAP Cloud Application Programming Model (CAP) development.

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.

Skills for SAP Cloud Application Programming Model (CAP) development: project setup, modeling, troubleshooting, upgrades, and an interactive CAP trivia quiz.

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.

Use when implementing SAP CAP Java handlers with Spring Boot: EventHandler, @Before @On @After annotation, CqnService, PersistenceService, ApplicationService, CdsCreateEventContext, CdsReadEventContext, @ServiceName, @Autowired, CQL Select Insert Update Delete, CAP Java SDK cds4j, cds-framework-spring-boot, pom.xml Maven dependency, Java event handler implementation.

Use when building AI/LLM features inside a SAP CAP application: the CAP LLM Plugin (@sap/cds-plugin-llm or @sap-ai-sdk), RAG (Retrieval-Augmented Generation), vector embeddings, chat completions, orchestration, SAP AI Core, or GenAI Hub integration from within a CAP service.

Use when setting up or using the official SAP MCP Server for CAP development, the SAP UI5 MCP Server, or the SAP Fiori Elements MCP Server with AI coding agents (Claude Code, OpenCode, GitHub Copilot, Cursor). Covers installation, configuration, available tools, and combining MCP servers with skills.

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.

Use when adding SAP CAP first-party plugins to a project: @cap-js/change-tracking, @cap-js/audit-logging, @cap-js/attachments, @cap-js/notifications, @cap-js/telemetry, @cap-js/graphql, @cap-js/data-inspector, @cap-js/data-privacy, @cap-js/ai, WebSocket, OData V2 adapter, or the ORD (Open Resource Discovery) plugin. Covers setup, annotations, and configuration.

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.

Use when migrating a SAP CAP project to CDS 10 / @sap/cds 10 (released June 2026): deprecated APIs, breaking changes, Node.js 22 minimum, consolidated service APIs, bypass drafts by default, ieee754compatible defaults, Vitest/ESM migration, native SQLite/Fetch defaults, or preparing for the CDS 10 major version upgrade.

Use when migrating a SAP CAP project to CDS 9 / @sap/cds 9 (released May 2025): deprecated APIs, breaking changes, new parser, @sap/xssec v4 upgrade, @cap-js database services migration, protocol adapter changes, or preparing for the CDS 9 major version upgrade.

Use when defining or reviewing CDS data models: entities, aspects, associations, compositions, projections, views, annotations, cuid and managed aspects, or any schema.cds / db/*.cds work in a SAP CAP project. Covers CDL syntax, reuse types from @sap/cds/common, naming conventions, and model-design best practices.

Help with CDS (Core Data Services) view entity development including data modeling, annotations, associations, compositions, access controls, aggregate expressions, built-in functions, and input parameters. Use when users ask about CDS views, CDS view entities, CDS annotations, CDS associations, CDS compositions, CDS access control, CDS metadata extensions, data modeling in ABAP, define view entity, define root view entity, semantic annotations, UI annotations, or building CDS data models for RAP or analytical scenarios. Triggers include "create a CDS view", "define view entity", "add an association", "CDS annotation", "access control", "composition", "CDS hierarchy", "CDS aggregate", "CDS functions", or "data model".

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.

STDIO · npx -y chrome-devtools-mcp@latest

Use when setting up CI/CD pipelines for SAP CAP applications: GitHub Actions, SAP Continuous Integration and Delivery (CICD) service, automated testing, build pipelines, CF/Kyma deployment automation, cds add github-actions, or pipeline configuration for CAP Node.js and Java projects.

Clean ABAP StyleGuides. Apply Clean ABAP guidance when creating, refactoring, reviewing, or explaining ABAP artifacts such as classes, interfaces, reports, function modules, and unit tests.

Check ABAP code for compliance with Clean ABAP principles. Use this skill when users ask to check, validate, review, or analyze ABAP code for clean code compliance, code quality, best practices, or adherence to Clean ABAP guidelines. Triggers include requests like "check this ABAP code", "is this clean ABAP", "review my ABAP for clean code", "validate ABAP against clean code principles", or "analyze ABAP code quality".

Use when reviewing, auditing, or assessing SAP CAP code quality: CDS models, service handlers, test files, MTA descriptors, security annotations, or any cap-related code. Performs structured checks against CAP best practices, identifies anti-patterns, flags missing security/error handling, and suggests improvements aligned with capire documentation.

Generates a complete, screenshot-rich HTML documentation page for any web application by autonomously navigating it with Playwright. Use this skill whenever the user wants to document a tool, generate user documentation, create an onboarding guide for an app, document a new feature, or says things like "document this", "create docs for", "generate documentation for", "make a user guide for", or "document what this tool does". Produces a fully self-contained HTML file with embedded screenshots, feature walkthroughs, and a clean professional design — ready to share with no dependencies. Requires a Playwright MCP connection.

Generate SAP BTP solution diagrams as .drawio XML aligned to the SAP BTP Solution Diagram Design Guideline (Horizon theme), including official colors, area nesting, connector semantics, and draw.io CLI export support.

Use when handling errors in SAP CAP applications: req.reject, req.warn, req.info, req.error, cds.error, HTTP status codes, i18n error messages, @SAP.Messages, validation errors, field-level errors, error targets, global error handlers, and business errors.

Use when working with SAP Fiori Elements UI annotations: UI.LineItem, UI.SelectionFields, UI.Facets, UI.FieldGroup, UI.HeaderInfo, UI.DataField, UI.DataFieldForAction, Criticality, ValueList, Common.Text, @title, UI.Hidden, OData V4 annotation vocabulary, List Report columns, Object Page sections, annotations.cds file.

Use when implementing SAP Fiori Draft support in CAP: @odata.draft.enabled, draft lifecycle events (NEW, EDIT, SAVE, CANCEL, DISCARD), draft validation, Fiori draft messages (CAP Aug 2025 GA), lean draft, or draft-enabled entity queries in SAP CAP Node.js or Java projects.

Use when working with SAP Fiori Elements floorplans: List Report Object Page LROP, Worklist, ALP, Analytical List Page, Overview Page OVP, Flexible Column Layout FCL, manifest.json routing, cds add fiori, Application Generator, OData V4 app setup.

Use when working with SAP Fiori Elements flexible programming model FPM: building blocks macros:Table, macros:FilterBar macros:Chart macros:Field, extension points, custom section, custom column, controller extension, ControllerExtension.extend, custom action, sap.fe.macros namespace, OData V4 extension.

Use when working with SAP Fiori Elements navigation: routing manifest.json, List Report Object Page route, sub-object page, semantic object navigation, intent-based navigation, cross-app navigation, CrossApplicationNavigation, Launchpad target mapping, FCL layout navigation, deep link.

Use when working with SAP Fiori tools in VS Code or SAP Business Application Studio: Application Generator, Page Editor, Guided Development, Service Modeler, cds add fiori, preview SAP Fiori apps locally, deployment with fiori-tools-proxy, or the UI5 Language Assistant for annotation code completion.

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.

Use when building native SAP HANA Cloud database artifacts with HDI (HANA Deployment Infrastructure): HDI container, .hdbtable, .hdbview, .hdbcalculationview, .hdbprocedure, .hdbfunction, .hdbsynonym, .hdbrole, .hdbgrants, .hdbsequence, .hdbtabledata, SQLScript stored procedures, calculation views, column store, .hdiconfig / .hdinamespace, hdi-deploy, or exposing native HANA objects to a CAP service via .hdbsynonym.

Use when building integrations on SAP Integration Suite / Cloud Integration: integration flow (iFlow), adapters (HTTPS, SOAP, OData, SFTP, IDoc, JMS, AMQP, ProcessDirect), content modifier, message mapping, router, splitter, gather, content enricher, Groovy or JavaScript script, externalized parameters, security material (User Credentials, OAuth2 Credentials, keystore), exception subprocess, and Message Processing Log (MPL) monitoring.

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.

HTTP · https://mcp.leanix.net/services/mcp-server/v1/mcp?toolsets=inventory,automations,calculations,custom_reports

Use when implementing internationalization (i18n) or localization in SAP CAP: localized entities, _texts tables, i18n message bundles, @title annotations, locale-aware queries, translating UI labels, or working with @sap/cds/common Currency / Country / Language types.

Use when implementing event-driven patterns in SAP CAP: emitting or consuming events, SAP Event Mesh, CloudEvents format, messaging configuration, topic names, the outbox pattern, or cross-service event communication.

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.

Use when implementing multitenancy in SAP CAP: @sap/cds-mtxs, MTX sidecar, tenant provisioning, tenant subscription, tenant upgrade, HDI per tenant, service-manager, extensibility, tenant lifecycle hooks, SaaS, shared tenant mode.

Use when adding logging, tracing, metrics, or observability to a SAP CAP application: cds.log, @cap-js/telemetry, OpenTelemetry, SAP Cloud Logging, Dynatrace, W3C trace context, outbox metrics, or debugging CAP applications in production.

Help with OData service development in ABAP including OData V2 and V4 services via RAP service bindings, SEGW-based services, service definitions, service bindings, OData annotations, consumption of external OData services, and troubleshooting common OData errors. Use when users ask about OData, OData V2, OData V4, service binding, service definition, SEGW, OData annotations, OData consumption, OData client proxy, HTTP client, communication arrangement, external API consumption, /IWBEP/ errors, or exposing a RAP BO as OData. Triggers include "create OData service", "expose RAP BO", "service binding", "OData V4", "consume external OData", "OData annotations", "SEGW service", or "OData error".

Bootstrap off-stack ABAP Unit testing plus an abaplint static-analysis gate onto an abapGit-serialised ABAP repository, with no live SAP system. Use when you need to run a repo's existing ABAP Unit tests in CI (GitHub Actions) by transpiling serialised ABAP to JavaScript with the abaplint transpiler and open-abap-core and executing them on Node. Covers pinning the transpiler parse dialect to a specific SAP_BASIS release (e.g. v816), breaking a class-under-test free of heavy DDIC drag with a shim or factory seam, authoring minimal domain-less DDIC fixtures, a reproducible npm ci committed-lockfile setup, and wiring the off-stack unit-test job beside the abaplint lint job on every push and pull request. Triggers on "off-stack ABAP Unit", "transpiled ABAP Unit on Node", "abaplint transpiler CI", "run ABAP tests without a SAP system", "ABAP GitHub Actions unit tests", "abaplint new-repo bootstrap". Scope boundary is load-bearing: it verifies orchestration and pure-ABAP logic only; any class calling classic BAPIs, the database, or HTTP is shimmed and remains an on-stack ATC + ABAP Unit concern, and an off-stack green is CI-grade provenance, not an in-system verification.

Generates ready-to-send .emltpl email files for Outlook on Mac. Use when the user asks to send, draft, compose, write, or prepare an email — or when any workflow produces output that needs to be emailed. Trigger phrases include: "send an email", "draft an email", "compose an email", "create an email to", "write an email", "prepare an email", "email this to", "forward this to".

Use when optimizing SAP CAP applications for performance: slow queries, N+1 problem, SELECT columns projection, HANA execution plan, SELECT.foreach, SELECT.pipeline, streaming large data, calculated elements, database index, query optimization, limit results.

Tracks pre-sales activity hours, manages time entries, and produces weekly Excel timesheet reports. Use this skill whenever the user wants to log time, create a time entry, update hours, check weekly activity, build a timesheet report, query logged hours, or email a weekly report. Trigger phrases: "log hours", "add time entry", "log my time", "update my hours", "timesheet", "weekly report", "how many hours did I log", "log my activity", "pre-sales hours", "time entry for", "what did I log".

Creates Microsoft Outlook calendar reminders from plain language in any conversation. Use this skill whenever the user wants to set a reminder, schedule something, create a calendar event, or says things like "remind me", "don't let me forget", "set a reminder", "add to my calendar", "every Monday remind me", "show me my reminders", or "set up sprint reminders". Generates a standard .ics file and opens it directly in Outlook for Mac — one click to confirm and the event lands in Exchange with a popup alarm. Supports timed reminders, all-day reminders, recurring weekly reminders, team-aware events (colleague name noted in description), sprint setup (4 events in one command), and listing all upcoming reminders. If direct opening is unavailable, the user can double-click the file manually to import it. Direct calendar creation via Microsoft Graph is not yet supported in Joule (tracked in JWD-491). Full seamless experience requires Claude Desktop on macOS.

Help with RAP (RESTful ABAP Programming Model) development including behavior definitions, EML statements, managed and unmanaged BOs, draft handling, actions, validations, determinations, side effects, and business events. Use when users ask about RAP, BDEF, BDL, EML, behavior definitions, behavior pools, managed BO, unmanaged BO, draft-enabled BO, RAP actions, RAP validations, RAP determinations, RAP side effects, RAP business events, create/read/update/delete in RAP, or building transactional Fiori apps with ABAP Cloud. Triggers include "create a RAP BO", "write a behavior definition", "EML syntax", "managed vs unmanaged", "enable draft", "add an action", "add a validation", "RAP handler method", or "RAP saver class".

Help with RAP business events and enterprise eventing including event definitions in behavior definitions, raising events from RAP handler methods, event bindings, SAP Event Mesh integration, event consumption, and event-driven architecture patterns in ABAP Cloud. Use when users ask about RAP business events, enterprise events, event mesh, eventing, raising events, event binding, event definition, event consumption, event-driven, asynchronous processing, event topics, or publish-subscribe in ABAP. Triggers include "RAP event", "business event", "raise event", "event mesh", "event binding", "enterprise eventing", "event-driven", "publish event", "consume event", or "asynchronous event".

Find released ABAP classes for ABAP Cloud Development. Use when user asks about ABAP classes for specific functionality like email, UUID generation, time/date handling, JSON/XML processing, RAP, string processing, random numbers, regex, Base64, HTTP calls, unit testing, PDF rendering, parallel processing, application logs, or any other ABAP Cloud class lookup.

Use when integrating SAP CAP applications with remote services: external OData, S/4HANA integration, cds.connect.to, cds import edmx, BTP Connectivity, Destination Service, mashup, req.query delegation, REST service, remote service proxy, service binding, hybrid testing.

Agent Skills that extend AI coding agents with SAP ABAP, ABAP Cloud, RAP, CDS, OData, testing, security, migration, and BTP development workflows and domain knowledge.

Executes SAP ABAP Development Tools (ADT) REST operations for object discovery, source management, object creation, activation, testing, transport handling, history, where-used analysis, message classes, and text elements. Use when working with an SAP ABAP system and the required ADT operation is unavailable through the currently configured MCP tools.

Agent Skill that generates SAP Business Technology Platform (BTP) solution diagrams following the official SAP BTP Solution Diagram Design Guideline (Horizon theme), producing .drawio XML with official SAP Horizon colors, atomic design system shapes, and exporting to PNG/SVG/PDF/JPG via the draw.io desktop CLI.

Skills for generating production-quality SAP BTP solution diagrams (Horizon theme) via draw.io desktop CLI

A single parameterized presales demo for SAP CX AI. Launch with "start the [industry] B2B commerce demo", "start the [portal name] demo", or all three combined — e.g. "start the pharma VeriSupply B2B commerce demo". Covers 25 industry verticals in B2B Commerce mode and a distinct Sales and Service CRM mode with 9 acts. All scenarios are high-fidelity illustrative simulations using mock data — no live SAP system is connected. Activate on any combination of industry name, portal brand, and business process in the trigger statement.

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.

Generate SAP Fiori Launchpad URLs from app names using AppList.json. Looks up app information by name and constructs proper FLP URLs with required parameters like sap-client and sap-language.

Agent Skills that extend AI coding agents with SAP LeanIX workflows and domain knowledge via the LeanIX MCP server.

Agent Skills for SAP LeanIX — reusable, portable instructions that extend AI coding agents with LeanIX-specific workflows and domain knowledge.

Use when implementing security and authorization in SAP CAP: authentication, @requires, @restrict, role-based access, XSUAA, IAS, grant, to, where clause, req.user, user roles, instance-based authorization, row-level security, xs-security.json, scopes, role templates, user attributes.

Use when implementing SAP CAP service handlers: service.js, service.ts, ApplicationService, before/on/after, event handler, custom action, custom function, cds.ql, SELECT INSERT UPDATE DELETE, srv.run, CRUD implementation, CAP Node.js business logic, handler registration.

SmartRecruiters offer breakdown — generate India CTC salary breakdowns and formatted PDF offer letters for candidates in the SmartRecruiters recruiting workflow. Use when structuring compensation packages, calculating take-home salary, computing PF, HRA, Gratuity, or Professional Tax for Indian hires. Also use for side-by-side CTC comparison across multiple offer values (simulate mode) to support salary negotiation in SmartRecruiters. Triggers on: CTC calculation, India salary structure, offer letter India, SmartRecruiters offer, SR offer breakdown, HRA Metro Non-Metro, Employee PF, Employer PF, Gratuity 4.81%, Professional Tax, income tax old regime, aviation allowance, flight allowance, cabin crew salary, INR salary breakdown, India compensation structuring, offer letter PDF generation, CTC simulate, what-if salary, take-home comparison.

Use when implementing state machines, status workflows, or status-based transitions in SAP CAP: @flow annotations, status-transition flows (Gamma status, production ready cds 9.5+), custom state machines, action-based status changes, or validating entry/exit conditions for entity states without writing boilerplate handler code.

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.

Use when writing or reviewing tests for a SAP CAP application: unit tests, integration tests with cds.test, Vitest setup (recommended since CAP April 2026), jest setup, mocking services or databases, testing actions/functions, or test data management in SAP CAP Node.js projects.

Meeting scribe. Use this skill whenever the user wants to turn a recorded meeting into follow-ups — fetch the meeting transcript, extract per-person action items, optionally find related emails, then deliver them either as 1-1 direct messages or a single summary posted to a group chat. Triggers on "meeting notes", "action items", "meeting follow-ups", "who owes what after the call", "summarize the meeting and assign tasks".

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?").

SAPUI5 / OpenUI5 plugin for coding agents. Creates and validates UI5 projects, accesses API documentation, runs UI5 linter, retrieves development guidelines and best practices for UI5 development.

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.

Use when creating SAPUI5 custom controls: Control.extend(), renderer pattern, metadata definition with properties, aggregations and events, lifecycle hooks (init, onBeforeRendering, onAfterRendering, exit), TypeScript custom controls, or reusable UI5 control development.

Use when working with SAPUI5 OData V4 data binding: ODataModel bindList bindContext bindProperty, requestContexts setProperty getObject requestObject, $auto $direct batch group, requestSideEffects, ODataListBinding.create Context.delete, controller data access.

Use when working with SAPUI5 i18n internationalization: ResourceModel, i18n.properties message bundle, i18n text binding in XML views, UI5Date.getInstance, DateFormat, NumberFormat, supportedLocales, fallbackLocale, oBundle.getText parameters, localization.

Complete UI5 modernization toolkit with workflow and specialized fix patterns for modernizing SAPUI5/OpenUI5 applications

Use when working with SAPUI5 testing: wdi5 WebdriverIO E2E test, OPA5 integration test, QUnit unit test, wdio-ui5-service, browser.byControl selector, page object pattern, UIVeri5 migration, UI5 test automation, wdio.conf.js ui5 service, jasmine mocha test runner.

SAPUI5 / OpenUI5 plugin for coding agents. Converts JavaScript-based UI5 projects to TypeScript.

A skill for converting UI5 (SAPUI5/OpenUI5) projects to TypeScript.

STDIO · npx -y @ui5/mcp-server