Wizarck/ai-playbook

Universal AI-dev norms, specs, scripts, and templates for Wizarck org projects (consumed via git submodule).

This repository also configures its own agents. See what ai-playbook tells them →

6Stars on the repository
77Mods indexed here, across every type
5d agoLast push, which is what freshness is scored on
customA LICENSE file GitHub cannot name, so bodies are not copied

ponytail-review

73

Wizarck/ai-playbook

Skill Claude CodeCodex

Use when the user wants a code review focused exclusively on over-engineering — says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness/security review; this one only hunts complexity in the current diff. Gated by the…

not rated 6 5d ago A 83 tokens copy · 75%

ponytail

74

Wizarck/ai-playbook

Skill Claude CodeCodex

Use when the user wants the laziest solution that actually works — types /ponytail, says "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Supports intensity levels lite, full…

not rated 6 changed 4d ago A 99 tokens original

sweep

75

Wizarck/ai-playbook

Skill Claude CodeCodex

Use when the user wants to find code that has quietly stopped being used — types /sweep, asks for a "dead code sweep", "repo entropy", "what can we delete", "orphan files", "unused code", or asks to review a sweep ledger. Adjudicates candidates a deterministic scanner already produced; it never deletes anything and…

not rated 6 5d ago A 100 tokens original

bmad-tea-knowledge

76

Wizarck/ai-playbook

Skill Claude CodeCodex

Use when a testing skill needs a knowledge fragment on fixtures, network-first safeguards, test levels, priorities, data factories, CI burn-in, or any other testing pattern — this is where those fragments live.

not rated 6 5d ago A 48 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: