add-standards-layerlisted

Add a standards layer for **$ARGUMENTS** to this repository. ## Where layers live - `.claude/rules/common/` — stack-agnostic rules. No frontmatter, loaded in every session. This is where non-negotiable invariants live, because they must apply while a file is being *created* and after `/compact`. - `skills/standards-<name>/` — language and framework layers. These load on demand when the `description` matches the work at hand, which also makes them distributable inside the plugin (`.claude/rules/` is not a plugin component). - `.claude/rules/_template/` — blank canonical stubs to copy from. ## Steps 1. **Confirm there is a real delta.** A layer exists only to say what `common/` does not already say. If the guidance is general, it belongs in `common/` instead — put it there and stop. 2. **Create `skills/standards-<name>/`** with a `SKILL.md` and one file per topic where the layer has a genuine delta. Copy the stubs from `.claude/rules/_template/`; the canonical set is a menu, not a mandate: `coding-style.md` · `patterns.md` · `security.md` · `testing.md` · `hooks.md` Process topics (`agents`, `code-review`, `development-workflow`, `git-workflow`) are `common/`-only and must not be duplicated into a layer. 3. **Write `SKILL.md` as a thin overview**, under 500 lines, that says what the layer covers and points at the topic files. Its `description` is the trigger — name the concrete technologies and concerns so the layer loads when it should: