aaddrick/claude-pipeline
21 skills
$npx skills add aaddrick/claude-pipelineSkillInstalls
adapting-claude-pipelineUse 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 workflowsbrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.bulletproof-frontendBulletproof 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 dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesexecuting-plansUse when you have a written implementation plan to execute in a separate session with review checkpointshandle-issuesBatch process GitHub issues via batch-orchestrator.sh with rate limit handling and session resumptionimplement-issueUse when given a GitHub issue number and base branch to implement end-to-endimprovement-loopUse 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 whinvestigating-codebase-for-user-storiesUse when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from codeprocess-prProcess PR based on code review - if approved, create follow-up issues, merge, close; if changes requested, re-run implement-issuereview-uiComprehensive 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.subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionsystematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixestest-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeui-design-fundamentals--- name: ui-design-fundamentals description: Use when designing UI components, reviewing frontend code, choosing colors, spacing, typography, or layout. Use when CSS looks off, components feel unbalausing-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in .worktrees/using-skillsUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questionswrite-docblocksUse when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple fileswriting-agentsUse when creating new agents, editing existing agents, or defining specialized subagent roles for the Task toolwriting-plansUse when you have a spec or requirements for a multi-step task, before touching codewriting-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment