CDS Modeling
Combined developer assistant for SAP Customer Experience (CX) covering three capabilities: CX API Explorer (finds and scaffolds OCC, Sales Cloud v2, and Service Cloud API calls from api.sap.com), CAP CDS Assistant (generates CDS entities, annotations, service definitions, and extension patterns using cap.cloud.sap), and CX Error Resolver (diagnoses Commerce Cloud, Sales/Service Cloud v1/v2, CAP, and BTP errors using public SAP Help and KBAs). Grounded in public SAP sources only via live web search; no authentication required.
Executes local scaffolding for a SAP CAP (Node.js) multitenant project — auto-detecting existing @sap/cds and @sap/cds-mtxs (or legacy @sap/cds-mtx) versions in the target project, or asking for the target version on greenfield projects, then running the actual cds init / cds add commands. Complements conceptual multitenancy guidance skills by handling the executable setup step. Does not handle deployment to Cloud Foundry/Kyma, XSUAA/IAS setup, or SaaS Registry subscription.
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".
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.