cap-developerlisted

## What I do Provide correct, lean, idiomatic guidance for CAP development — from project setup and CDS modeling through declarative annotations and programmatic event handlers. ## Runtime Choice When in a new project, use the globally installed `@sap/cds-dk` (cli: `cds`). Defer the language choice until necessary. This choice is only necessary once code is added or the app is deployed. When only working with cds models, you can simply start with `cds w` without needing to define a runtime. ## MCP Server Always use the CAP MCP server to: - Search CAP documentation before guessing at APIs or annotations - Read the effective CDS model of an existing project before adding or changing anything Never use the CAP MCP server as Fiori/SAPUI5 documentation. It contains useful information about how CAP integrates with Fiori/SAPUI5 but is not a complete reference for those frameworks. **Caveat on release notes and version tables:** MCP search results sourced from release notes or version recommendation tables may be outdated — they reflect what was true *at the time of that release*, not necessarily today. Always cross-check version-specific claims (e.g. "recommended Node.js version") against live sources like `cds version`, `npm view`, or the current Getting Started page rather than trusting a snapshot from a past release note. ## Project setup rules Start a new project with: ```sh cds init <name> # creates a subdirectory; omit <name> to init in cwd cd <name> cds watc