implement-ag-playbook

**Usage:** `/implement-ag-playbook PLAYBOOK_NAME [MODE]` **Examples:** - `/implement-ag-playbook onboarding` - Implement all available prompts - `/implement-ag-playbook login 3-frameworks` - Implement only PROMPT-3-FRAMEWORKS.md - `/implement-ag-playbook login react` - Implement only PROMPT-REACT.md Implement the specified playbook based on its existing PROMPT specification files. --- ## Playbook Structure Reference Complete playbooks have this structure (see `v2/playbooks/README.md`): ``` v2/playbooks/[name]/ ├── PROMPT-3-FRAMEWORKS.md # Builds → react-example/, vue-example/, lit-example/ ├── PROMPT-REACT.md # Builds → react/ ├── PROMPT-VUE.md # Builds → vue/ ├── PROMPT-LIT.md # Builds → lit/ └── design/ # Shared assets (mockups, icons, images) ``` **Single-Framework vs 3-Frameworks differences:** - Different fonts (e.g., Playfair Display vs Merriweather) - Different social icons (e.g., Apple vs Facebook) - Different asset filenames (e.g., `logo.svg` vs `logo-3-frameworks.svg`) --- ## Phase 0: Validation 1. **Verify playbook exists** - Check `v2/playbooks/$ARGUMENTS/` exists - List available PROMPT files: - `PROMPT-3-FRAMEWORKS.md` - `PROMPT-REACT.md` - `PROMPT-VUE.md` - `PROMPT-LIT.md` - If MODE specified, verify that PROMPT file exists - If no MODE specified, ask user which to implement 2. **Read the prompt specification** - Read the target PROMPT file(s) - Extract: ...