rite-customizelisted

# /rite-customize: guided project customization Create, list, validate, or scaffold one project-local DevRites customization without forking the pack. Read [`devrites-lib/reference/standards/core.md`](../devrites-lib/reference/standards/core.md), then read `docs/extensions.md` if present; in an installed project, fall back to `.claude/skills/devrites-lib/reference/standards/core.md` plus the user's installed DevRites docs if available. Fast paths: - `list` → run `devrites-engine overrides list` and `devrites-engine extensions list`; stop. - `validate` → run both validators; stop. - `scaffold extension <name>` → create the smallest valid `.devrites/extensions/<name>/skill/SKILL.md` draft after approval, then validate. ## Workflow 1. **Classify the ask.** Pick exactly one target: - `list` → inspect only. - `validate` → validate only. - `override <agent>` → `.devrites/overrides/<agent>.md` - `extension <name>` / `scaffold extension <name>` → `.devrites/extensions/<name>/` - unclear → ask one blocking question with those options. Done when the target kind and path are known. 2. **Load the existing surface.** Read the existing file/dir if present. For overrides, confirm the target agent exists under `.claude/agents/` or `pack/.claude/agents/`. For extensions, check whether `skill/SKILL.md` or `agent.md` already exists. Done when you know whether this is create or update. 3. **Draft the smallest artifact.** - Override: write only added checks/emphasis. Do