implement-ag-playbook

Solid

Implement a playbook from its PROMPT specification files. Supports both single-framework (PROMPT-REACT.md, etc.) and 3-framework (PROMPT-3-FRAMEWORKS.md) modes.

Web & Frontend 812 stars 47 forks Updated 1 months ago Apache-2.0

Install

View on GitHub

Quality Score: 93/100

Stars 20%
97
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

**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: ...

Details

Author
AgnosticUI
Repository
AgnosticUI/agnosticui
Created
5 years ago
Last Updated
1 months ago
Language
TypeScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

kookr-playbooks

How to create, structure, and launch Kookr playbook tasks — reusable agent task templates with dynamic sources and project identity

2 Updated today
kookr-ai
AI & Automation Listed

eforge-playbook

Create, edit, run, list, and promote eforge playbooks — reusable recurring-workflow templates

66 Updated today
eforge-build
AI & Automation Solid

packmind-update-playbook

Use when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills). Triggers on explicit phrases like "update packmind standard", "add a packmind skill", "fix packmind command", "change packmind playbook", "deprecate a standard". Also triggers — even without an explicit request — whenever the conversation reveals an opportunity: a new coding convention was just agreed on, a recurring pattern emerged, a workflow changed, a rule was found outdated, or the user says things like "we always do X", "let us remember to Y", "that is the pattern we use". If there is any chance the conversation established a convention or exposed a gap, invoke this skill proactively. This skill defines a mandatory workflow: do NOT edit artifact files directly — follow all phases regardless of change size.

287 Updated today
PackmindHub
Data & Documents Listed

playbook-writer

Meta-skill that generates compliant PLAYBOOK.md files following the BRAINIAC template. Use when creating or editing modules in the command center. For general readme creation, see create-readme.

2 Updated 1 weeks ago
tuliosousapro
AI & Automation Featured

deal-playbook

Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".

2,274 Updated today
jeremylongshore