layer-new

# /layer-new -- scaffold a project layer Creates `docs/layers/<layer-name>/` with the full template structure defined by [principle 28](https://github.com/AnastasiyaW/claude-code-config/blob/main/principles/28-feature-layer-architecture.md). ## When to use - Starting to track a new bounded concern in a long-running project - Refactoring sprawling cross-cutting code into a documented layer - Onboarding a new team member who needs the layer map ## When NOT to use - One-off scripts or pet projects with <5 features (overhead not justified) - Layer name describes a directory (`src` is not a layer) - The "layer" is actually one feature in disguise -- use `/feature-new` inside an existing layer instead ## Arguments ``` /layer-new <layer-name> [--purpose "..."] [--principles P-NN,P-MM] ``` - `<layer-name>` -- kebab-case, single word preferred. Examples: `security`, `data`, `image-processing`, `observability`. - `--purpose` -- one-sentence purpose. If omitted, prompt the user. - `--principles` -- comma-separated Tier 1 principle IDs that govern this layer (e.g. `P-02,P-21`). If omitted, leave placeholder in README. ## Direction (what to do, in order) ### Step 1 -- Verify environment Check the current working directory: 1. Is it a git repository? Run `git rev-parse --show-toplevel`. If not, ask the user whether to initialize one (offer `git init` + private GitHub repo per global rule). 2. Does `docs/` exist? If not, create it. 3. Does `docs/layers/README.md`...