Use when creating or updating maintenance scripts in scripts/. Enforces patterns for validation, postinstall hooks, build utilities, CLI argument parsing, exit code conventions, CI/CD integration, and internationalized user feedback. Ensures scripts are robust, testable, and follow established conventions.
Use when creating or updating test files that need to leverage existing test utilities. Enforces consistent discovery and reuse of shared testing infrastructure including base utilities, mocking libraries, and established test patterns. Ensures tests benefit from centralized test helpers rather than duplicating…
Use when creating or updating test files for CLI commands, utilities, and routes. Enforces consistent test structure, Mocha patterns, proper assertion usage, execution isolation, error handling validation, and integration with the project's test infrastructure.
Use when adding user-facing text in CLI commands, API routes, or utilities. Enforces consistent use of bundle.getText() for all translatable strings, descriptive key naming, and multi-language synchronization across i18n/ property files.
Use when creating or updating TypeScript configuration files. Enforces consistent compiler options, module resolution strategies, type generation from JavaScript sources, declaration file management, and dual-config patterns for mixed JS/TS projects. Ensures TypeScript integration supports both ESM and type safety…
Use when creating or updating shared utility modules. Enforces consistent patterns for error handling, internationalization, type safety, lazy loading, caching, and integration with the CLI infrastructure. Ensures utilities are reusable, maintainable, and follow established conventions.
Use when creating or updating VitePress documentation site configuration. Enforces consistent config structure, sidebar generation patterns, theme customization, Mermaid integration, navigation organization, and deployment settings. Ensures documentation site maintains proper structure and user experience.
Automate docs updates and command documentation generation. Use for generate-command-docs, enhance-command-docs, sidebar generation, and VitePress build checks.
Cursor rule "cursorrules" from SAP-samples/hana-developer-cli-tool-example, covering hana-cli — ai coding assistant context, about hana-cli, when to use hana-cli, key patterns and connection setup.
150+ SAP HANA database tools for AI assistants. Query tables, import/export data, profile data quality, compare schemas, manage backups, monitor performance, and more. Connects to SAP HANA Cloud and on-premise databases.
109 6d agoA
tokens not measured
originalApache-2.0
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Query @cap-js/mcp-server before writing CDS entities, types, aspects, services, or CAP service handlers. Triggers on schema and service files in db/ and srv/.
Query @sap-ux/fiori-mcp-server before writing CDS annotations, Fiori Elements config, or manifest.json. Triggers on annotation files in app/ and manifests.
Query @ui5/mcp-server before writing SAPUI5 controllers, XML views, control APIs, or model bindings. Triggers on views and controller extensions in app/.
Instructions for SAP-samples/cap-agentic-engineered, covering conversational style, code quality, commands, development rules and mcp servers: query before writing sap code.
150+ SAP HANA database tools for AI assistants. Query tables, import/export data, profile data quality, compare schemas, manage backups, monitor performance, and more. Connects to SAP HANA Cloud and on-premise databases.