What problem does it solve? Teams and AI agents working in a repository need a single authoritative statement of the coding discipline — toolchain, style, defensive coding, limits, version control, testing, and definition of done — but writing that page consistently across languages and styles is repetitive and error-prone. This Skill produces that page as a canonical spec document following spec-creator conventions. ## Core Features & Use Cases - Language detection and templates: Detects TypeScript, JavaScript, Rust, or Python from repo signals (Cargo.toml, tsconfig.json, pyproject.toml) and assembles per-language conventions from style-neutral base files. - Two coding styles: Renders the page in Tiger Style (defensive, assertion-heavy, limits everywhere) or Clean Code (readability-first, exceptions, small functions) using language-specific overlays. - VCS-aware sections: Detects jujutsu vs git and emits the matching version-control guidelines, preferring jj when both directories exist. - Use Case: A monorepo with a Rust backend and TypeScript frontend needs coding standards before development starts. The Skill detects both languages, confirms Tiger Style, and writes .specs/development-guidelines.md with toolchain tables, per-language conventions, AI-agent rules, and a definition of done, then indexes it in .specs/README.md. ## Quick Start Ask the AI to add a development-guidelines page to the spec at .specs/ for this repository using Tiger Style.
