Process Pr
Process PR based on code review - if approved, create follow-up issues, merge, close; if changes requested, re-run implement-issue
Writing Agents
Use when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool
Subagent Driven Development
Use when executing implementation plans with independent tasks in the current session
Ui Design Fundamentals
Use when designing UI components, reviewing frontend code, choosing colors, spacing, typography, or layout. Use when CSS looks off, components feel unbalanced, or accessibility is unclear.
Brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Review Ui
Comprehensive UI/CSS review using parallel agents. Each agent reviews against a specific UI design fundamentals section. Use when reviewing frontend code, CSS, Blade templates, or components.
Implement Issue
Use when given a GitHub issue number and base branch to implement end-to-end
Writing Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Improvement Loop
Use after resolving a bug, failed task, or unexpected agent behavior to improve the pipeline skills, agents, hooks, or scripts that contributed to the problem. Also proactively suggest improvements when recurring patterns or inefficiencies are observed.
Bulletproof Frontend
Bulletproof CSS and frontend design principles from "Handcrafted CSS" by Dan Cederholm. Apply when writing CSS, HTML, Blade templates, or reviewing frontend code. CSS is king — refactor Tailwind when encountered.
Adapting Claude Pipeline
Use when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack and workflows
Handle Issues
Batch process GitHub issues via batch-orchestrator.sh with rate limit handling and session resumption
Investigating Codebase For User Stories
Use when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code
Write Docblocks
Use when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files
Executing Plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Writing Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Using Git Worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in .worktrees/