aw-setup
SolidOne-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".
Install
Quality Score: 86/100
Skill Content
Details
- Author
- mthines
- Repository
- mthines/agent-skills
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
aw
Ships autonomous, end-to-end coding work — implement a feature or fix, all the way to a tested draft PR — from a single opt-in entry point. Detects the task tier (Micro / Lite / Full) and routes: Micro/Lite run single-pass in this context; Full hands off to the aw-planner → aw-executor agents. Use when the user asks to do a task "autonomously", "independently", "in isolation", "in a worktree", "end-to-end", "all the way to a PR", to "ship this", "land this", "take care of this", or "handle this without me" — or invokes `/aw` directly. Opt-in, not a wrapper on casual edits; the routing rule's exclusion list governs when to hold back. Triggers on "implement autonomously", "end-to-end", "in a worktree", "ship this", "/aw".
autonomous-workflow
The phase-based machinery (0–7) behind the `aw` dispatcher — task intake through tested PR delivery in an isolated Git worktree, with optional companion skills for planning, quality gates, TDD, UX, code quality, docs, and CI verification. Companions skip silently if not installed. NOT the entry point and not auto-triggered: a natural-language request to do work autonomously, end-to-end, in isolation, or in a worktree belongs to the `aw` skill, which detects the task tier and routes. Reach for this skill only to read or run the phase machinery directly, bypassing tier detection — invoke with /autonomous-workflow.
aw-tester-chrome
Runs UI verification specs in-session through the claude-in-chrome extension — the Chrome sibling of the aw-tester agent. Reads the same specs.md and aw-target.yml, drives Chrome interactively (navigate → read → act → assert, seeing the page between steps), and emits the same compact verdict block. Runs in the current session against an already-logged-in Chrome, so it is faster than the Playwright sub-agent for local runs, but it needs the browser extension and does not work in remote / CI envs. Falls back to aw-tester when the extension is not connected. Triggers on "run the spec in chrome", "verify with the chrome driver", "aw-tester-chrome", or a "preview-spec run --driver chrome" dispatch.