claude-featurelisted

# Claude feature ## Guards - If no feature description is provided, stop: `❌ No feature description. Describe what you want to add.` - Do not implement anything. Output the plan and stop. - When the feature description spans two or more independent concerns, write one plan file per concern. Do not bundle them under a single slug. ## Step 1: read the Claude setup Read these in parallel from the project root, skipping any that do not exist: - `CLAUDE.md`: behavior rules, conventions, commands - `.claude/REQUIREMENTS.md`: feature scope and non-goals - `.claude/ARCHITECTURE.md`: decisions already made - `.claude/TASKS.md`: current scope and status Also read these when the feature touches code or UI. Skip them for prose, docs, catalog, or config-only changes: - `.claude/DESIGN.md`: tokens, typography, spacing, and component rules - `.claude/wireframes/index.md` + the surface files relevant to the feature: intended UI layout and behavior. Read `index.md` first, then load only the per-surface files (`.claude/wireframes/<surface>.md`) the feature actually touches. Do not read the whole folder speculatively. When the plan adds or revises a surface, the wireframe file follows `standards/wireframes.md`. Coding standards live in `.claude/rules/`. Claude Code loads them automatically. Path-scoped rules apply to the files they match. ## Step 2: scan relevant source files Based on the feature description, identify and read source files that are directly relevant. Do not read entir