coding-standard

## Project Context - Git user: !`git config user.name` (!`git config user.email`) - OS username: !`whoami` - CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f` - AGENTS.md: !`find . -maxdepth 1 -name "AGENTS.md" -type f` - project-discovery.md: !`find . -maxdepth 3 -name "project-discovery.md" -type f` - Rules directory: !`find . -maxdepth 4 -type d -path "*/.claude/rules/coding-standards"` ## Step 1: Determine Mode Determine which mode to operate in based on the user's request: | Mode | When | Initial Status | Then | |------|------|----------------|------| | Creating new | Building a coding standard from scratch | `proposed` | → Step 2 | | Converting existing | User provides an existing document (ADR, etc.) to convert | `accepted` | → Step 2 | | Updating existing | Modifying an existing coding standard | — | Read the existing coding standard, → Step 3 | ## Step 2: Evaluate Appropriateness Coding standard documents are **not a replacement for automated tooling**. Before proceeding, evaluate whether the proposed coding standard falls into one of these categories: - Conventions that should be enforced by linters or formatters (variable naming, indentation, whitespace, import ordering, bracket placement, line length, semicolons) - Common language conventions that are well-known or easily discoverable from the language's own documentation and community norms (type declaration style, etc.) If the proposed coding standard falls into one of these categories: 1. Warn...