Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says \"is this fixed?\", or before closing an investigation.
CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.
Generator
This rule generates tool implementations for the Razorpay MCP server based on API documentation.
## Required Format
This rule requires:
1. A Razorpay API documentation URL starting with `https://razorpay.com
principles and nomenclature.
## Kotlin General Guidelines
### Basic Principles
- Use English for all code and documentation.
- Always declare the type of each variable and function (parameters and return value).
- Avoid using
Coding Rules
This document contains all coding rules and standards for the chase-functions project (both backend and frontend). These rules must be followed in all code implementations.
## General Rules
operations.
- Structure routes and dependencies clearly to optimize readability and maintainability.
Refer to FastAPI documentation for Data Models, Path Operations, and Middleware for best practices
automatically pick up CLAUDE.md
```
### Claude Projects / API
Upload the `.mdc` files as project knowledge documents. The YAML frontmatter is ignored but harmless — Claude will read the Markdown content.
### Other