aw-setuplisted

One-time (but safely re-runnable) setup flow that scaffolds a project's aw-tester aw-target: detects auth strategy, captures storage state, writes .claude/aw-targets/local.yml, and validates with a smoke spec. Re-runs detect the existing aw-target and only re-prompt for what broke or changed. Triggers on "/aw-setup", "setup aw-tester", "scaffold aw-target".
mthines/agent-skills · ★ 13 · AI & Automation · score 79

Install: claude install-skill mthines/agent-skills

# aw-setup — Aw-Target Scaffolding for aw-tester Interactive, idempotent setup flow that scaffolds the `.claude/aw-targets/` config that `aw-tester` needs to run specs. Run it **once** before the first autonomous PR that touches UI. Re-run it when auth drifts, fixtures change, or base URL moves. > **This is the prerequisite for spec-driven UI verification in the > autonomous-workflow.** Without an aw-target file, `aw-tester` cannot run and > the executor's Phase 4 spec verification step skips cleanly. --- ## When to run - **First time:** before running any autonomous feature that touches UI. - **Re-run:** when `aw-tester` reports `auth-refresh-failed`, when the base URL changes, or when seed fixtures are restructured. - **Never auto-triggered by the planner.** The planner halts and tells the user to run `/aw-setup`. The user runs it explicitly. --- ## Idempotency contract **First run:** full guided scaffolding (Phases A–E). **Re-run:** detect `.claude/aw-targets/local.yml` exists, validate each field: - Auth storage state: does the file exist? Is it fresh (< N days old)? - Fixtures: does the seed command resolve? Do references point to env vars that exist? - Smoke spec: run it. If green, done — no prompts needed. - Only prompt for what broke or is missing. - Show a unified diff before overwriting any field in the aw-target file. - Never silently overwrite the auth storage-state file (`.auth/*.json`, or the repo's own convention such as `.browser/auth-state*.jso