/sap-cap-capire

name: sap-cap-capire
description: |
  SAP Cloud Application Programming Model (CAP) development skill using Capire documentation.
  Use when: building CAP applications, defining CDS models, implementing services, working with
  SAP HANA/SQLite/PostgreSQL databases, deploying to SAP BTP Cloud Foundry or Kyma, implementing
  Fiori UIs, handling authorization, multitenancy, or messaging. Covers CDL/CQL/CSN syntax,
  Node.js and Java runtimes, event handlers, OData services, and CAP plugins.
license: GPL-3.0
metadata:
  maintainer: "Eduard Jiglau"
  maintainer_email: "hello@sap-ai-skills.com"
  website: "https://sap-ai-skills.com"
  version: "2.4.1"
  last_verified: "2026-02-22"
  cap_version: "@sap/cds 9.7.x"
  mcp_version: "@cap-js/mcp-server 0.0.5"
  lsp_version: "@sap/cds-lsp 9.7.x"

SAP CAP-Capire Development Skill

Related Skills

• **sap-fiori-tools**: Use for UI layer development, Fiori Elements integration, and frontend application generation
• **sapui5**: Use for custom UI development, advanced UI patterns, and freestyle application building
• **sap-btp-cloud-platform**: Use for deployment options, Cloud Foundry/Kyma configuration, and BTP service integration
• **sap-hana-cli**: Use for database management, schema inspection, and HDI container administration
• **sap-abap**: Use for ABAP system integration, external service consumption, and SAP extensions
• **sap-btp-best-practices**: Use for production deployment patterns and architectural guidance
• **sap-ai-core**: Use when adding AI capabilities to CAP applications or integrating with SAP AI services
• **sap-cloud-sdk-ai**: Use for SDK-level AI integration (chat completion, streaming, tool calling) in CAP event handlers
• **sap-cloud-sdk-ai-python**: Use for Python-based AI integration with CAP Java or standalone BTP services
• **sap-api-style**: Use when documenting CAP OData services or following API documentation standards
• **sap-dependency-security**: Use for secure dependency, lockfile, supply-chain, and exact MCP server pin controls in CAP service repos

When to Use This Skill

Use this skill when creating CAP projects, modeling CDS entities/services, implementing Node.js or Java event handlers, configuring HANA/SQLite/PostgreSQL persistence, deploying to BTP Cloud Foundry or Kyma, adding Fiori UIs, configuring authorization/multitenancy/messaging, or using CAP MCP/LSP tooling.

Common Issues

| Issue | First check | |-------|-------------| | `cds watch` or `cds serve` fails | Verify `@sap/cds-dk`, Node.js version, and project `package.json` scripts. | | Entity/service not found | Use CAP MCP `search_model` when available, then inspect `db/` and `srv/` CDS files. | | HANA deployment fails | Check HDI service binding, `mta.yaml`, and the HANA deployment references. | | Authorization behaves unexpectedly | Review `@requires`, `@restrict`, XSUAA/IAS bindings, and user role mappings. |

Table of Contents

• [Quick Start](#quick-start)
• [Project Structure](#project-structure)
• [Core Concepts](#core-concepts)
• [AI Integration](#ai-integration)
• [Database Setup](#database-setup)
• [Deployment](#deployment)
• [Bundled Resources](#bundled-resources)

Quick Start

Project Initialization

# Use an approved CAP toolchain:
# - project-local devDependencies
# - user-local npm prefix
# - enterprise-managed Node/CAP installation
# Ensure cds and optional cds-lsp commands are on PATH.
cds --version

# Create new project
cds init <project-name>
cds init <project-name> --add sample,hana

# Start development server with live reload
cds watch

# Add capabilities
cds add hana          # SAP HANA database
cds add sqlite        # SQLite for development
cds add xsuaa         # Authentication
cds add mta           # Cloud Foundry deployment
cds add multitenancy  # SaaS multitenancy
cds add typescript    # TypeScript support

Basic Entity Example

using { cuid, managed } from '@sap/cds/common';

namespace my.bookshop;

entity Books : cuid, managed {
  title       : String(111) not null;
  author      : Association to Authors;
  stock       : Integer;
  price       : Decimal(9,2);
}

entity Authors : cuid, managed {
  name        : String(111);
  books       : Association to many Books on books.author = $self;
}

Basic Service

using { my.bookshop as my } from '../db/schema';

service CatalogService @(path: '/browse') {
  @readonly entity Books as projection on my.Books;
  @readonly entity Authors as projection on my.Authors;
  
  @requires: 'authenticated-user'
  action submitOrder(book: Books:ID, quantity: Integer) returns String;
}

MCP Integration

This skill integrates with the official CAP MCP (Model Context Protocol) server, providing AI agents with live access to your project's compiled CDS model and CAP documentation.

**Available MCP Tools**:

• `search_model` - Fuzzy search for CDS entities, services, actions, and relationships in your compiled CSN model
• `search_docs` - Semantic search through CAP documentation for syntax, patterns, and best practices

**Key Benefits**:

• **Instant Model Discovery**: Query your project's entities, associations, and services without reading files
• **Context-Aware Documentation**: Find relevant CAP documentation based on semantic similarity, not keywords
• **Zero Configuration**: No credentials or environment variables required
• **Offline-Capable**: All searches are local (model) or cached (docs)

**Setup**: See [MCP Integration Guide](references/mcp-integration.md) for configuration with Claude Code, opencode, or GitHub Copilot. MCP package pins are governed by **sap-dependency-security** and validated by `npm run validate:mcp-security`.

**Use Cases**: See [MCP Use Cases](references/mcp-use-cases.md) for illustrative local workflow examples and planning assumptions, not repository-verified ROI.

**Agent Integration**: The specialized agents (cap-cds-modeler, cap-service-developer, cap-project-architect, cap-performance-debugger) au