dev-playbook

Dev Playbook

A growing collection of development skills for Claude Code.

Skills

problem-description

Generate an interactive, self-contained HTML walkthrough to explain complex technical problems step by step with concrete data and manual navigation controls.

Triggers on: "make me a walkthrough", "explain step by step with data", "interactive explanation", "make an animation", "walk me through with real examples"

brainstorm-reviewer

Review completed brainstorming sessions and verify the /superpowers:brainstorming process was followed correctly, with a strict pass/fail compliance report.

Triggers on: "review the brainstorm", "check the brainstorm", "verify brainstorming"

drive-to-legacy

A 6-phase systematic approach to fully understand an unfamiliar codebase, producing a comprehensive ARCHITECTURE.md with mermaid diagrams.

Phases:

1. User Stories - What the app does from the user's perspective
2. Project Identity and Component Map - Tech stack, files, component tree
3. Data Model - Entities, types, relationships
4. Business Logic - Rules, validation, cascades, fallbacks
5. API Reference - Every query with exact params, filters, and Why
6. Build and Deploy - How to run and ship

Triggers on: "explore this project", "understand this code", "I need to port this", "how does this app work", "document this codebase"

---

How to Use

Option 1: Install as a Plugin (recommended)

Install directly from GitHub:

claude plugin install github:ThodsaphonSonthiphin/dev-playbook

After installation, skills are available globally. Use them by name:

/dev-playbook:drive-to-legacy

Or just describe your task naturally - the skill triggers automatically when Claude detects matching keywords (e.g., "explore this project", "I need to port this code").

Option 2: Add as a Marketplace

If you want to track updates from this repo:

claude plugin marketplace add https://github.com/ThodsaphonSonthiphin/dev-playbook

Then install:

claude plugin install dev-playbook

Update to latest version later:

claude plugin update dev-playbook

Option 3: Copy to Your Personal Skills

If you just want to use a single skill without installing the full plugin:

# Copy the skill folder to your personal skills directory
cp -r skills/drive-to-legacy ~/.claude/skills/drive-to-legacy

The skill will be available immediately in your next Claude Code session.

Option 4: Add to a Project

Copy the skill into your project's .claude/skills/ directory so anyone who clones the repo gets it:

# From your project root
mkdir -p .claude/skills
cp -r /path/to/dev-playbook/skills/drive-to-legacy .claude/skills/drive-to-legacy

This makes the skill available to everyone working on that project.

Option 5: Local Testing During Development

Test the plugin locally without installing:

claude --plugin-dir /path/to/dev-playbook

---

Using Skills in Claude Code

Once installed, skills work in three ways:

1. Automatic trigger - Just describe your task. If your words match the skill's trigger conditions, Claude loads and follows the skill automatically.

You: "I need to understand how this legacy app works"
Claude: (loads drive-to-legacy skill automatically)

2. Slash command - Invoke directly by name:

/drive-to-legacy

Or with the plugin namespace:

/dev-playbook:drive-to-legacy

3. Ask Claude to use it - Simply mention the skill:

You: "Use the drive-to-legacy skill to explore this codebase"

---

Adding New Skills

1. Create a new folder under skills/:

   skills/
     drive-to-legacy/
       SKILL.md
     your-new-skill/        <-- add here
       SKILL.md
   

2. Write your SKILL.md with frontmatter:

   ---
   name: your-new-skill
   description: Use when [triggering conditions]
   ---
   

3. Bump the version in .claude-plugin/plugin.json

4. Commit and push

Versioning

This plugin uses semantic versioning in .claude-plugin/plugin.json:

• Patch (1.0.x): Typo fixes, clarifications
• Minor (1.x.0): New skills added, existing skills enhanced
• Major (x.0.0): Breaking changes to skill behavior

License

MIT