keepwrightlisted

# keepwright keepwright sets up **and continuously keeps** a high-quality engineering architecture in any git repo — new or existing, any stack. It is both a **scaffolder** (installs the architecture) and a **maintainer** (audits it and keeps it enforced). The craft of building the standard, and the keep that guards it. ## How it works — three layers 1. **Wizard command** (`commands/`) — you drive it; it asks the user the genuine choices via `AskUserQuestion` and orchestrates the rest. This is the "type it and configure" surface. 2. **Deterministic engine** (`scripts/`, run with `bun`) — does the mechanical work: `detect.ts` proposes a config from the repo, `apply.ts` copies templates and substitutes placeholders idempotently (anti-secret scan first), `audit.ts` reports integration coverage. No LLM guesswork in the mechanical path. 3. **Orchestration workflows** (`workflows/*.js`, the Workflow tool) — parallel multi-agent analysis, used *situationally* because it costs tokens: `map-brownfield` (enrich the config from a large repo), `derive-patterns` (mine the repo's design + writing voice → rules + validators), `verify-setup` (adversarial parallel verification). The split is deliberate: **mechanical → script, judgment → LLM/workflow.** ## Commands - **`/keepwright:setup`** — interactive wizard: detect → (optional brownfield map) → configure via questions → apply → auth → (optional derive + verify) → smoke. Accepts `--mode setup|audit|maint