.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/aaddrick/claude-pipeline
home/skills/aaddrick/claude-pipeline
aaddrick avatar

aaddrick/claude-pipeline

21 skills · 2 total installs

View on GitHub
$npx skills add aaddrick/claude-pipeline
SkillInstalls
write-docblocksUse when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files2adapting-claude-pipelineUse when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target…—brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.—bulletproof-frontendBulletproof CSS and frontend design principles from "Handcrafted CSS" by Dan Cederholm.—dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies—executing-plansUse when you have a written implementation plan to execute in a separate session with review checkpoints—handle-issuesBatch process GitHub issues via batch-orchestrator.sh with rate limit handling and session resumption—implement-issueUse when given a GitHub issue number and base branch to implement end-to-end—improvement-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.—investigating-codebase-for-user-storiesUse when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code—process-prProcess PR based on code review - if approved, create follow-up issues, merge, close; if changes requested, re-run implement-issue—review-uiComprehensive UI/CSS review using parallel agents. Each agent reviews against a specific UI design fundamentals section.—subagent-driven-developmentUse when executing implementation plans with independent tasks in the current session—systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes—test-driven-developmentui-design-fundamentalsname: ui-design-fundamentals description: Use when designing UI components, reviewing frontend code, choosing colors, spacing, typography, or layout.—using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in…—using-skillsUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions—writing-agentsUse when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool—writing-plansUse when you have a spec or requirements for a multi-step task, before touching code—writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment—