A curated marketplace of Claude Code plugins for agentic development workflows, featuring tools for architecture, knowledge management, and development automation
Run one exact Ticket through recovery, autonomous work, and its required landing, then write DONE or ESCALATED evidence back to that same Ticket. Use when a hosted trigger, agent runner, or person supplies a specific issue, tracker item, or file Ticket to work end to end. This skill does not select backlog work or…
Recover or start one unattended Ticket from a configured shared Ticket Store, then stop. Use from a scheduled agent trigger to resume one interrupted automation-owned Auto Ticket or select one ready Auto Ticket and invoke run-ticket. This is the low-frequency correctness path beside issue-event triggers, not a backlog…
Sync the manifest-dev plugins from doodledood/manifest-dev into .claude/. Clones the source, copies agents/skills/hooks, removes only previously-synced items that disappeared upstream, and leaves other plugins alone. Pass --all to sync every repo in the fleet and open a PR on each. Use when asked to sync manifest-dev…
Teach the learner to deeply understand a body of work — the current session's changes, a PR, an ADR, or any topic they name — the problem and why it existed, the solution and why it was built that way, and why it matters, incrementally and confirming mastery at each stage before advancing. Use when the user wants to…
Single iteration of PR tending. Reads PR state, classifies new events, routes fixes, reports status. Called by /loop via /tend-pr setup. Can be invoked manually to run a single tick.
Tend a PR through review to merge-readiness. Classifies comments (bot/human, actionable/FP/uncertain), fixes issues via manifest amendment + scoped /do (or directly in babysit mode), tends CI, syncs PR description, and asks before merging. Use when a PR needs tending through review, or to babysit a PR. Triggers: tend…
Author self-sufficient Tickets in the project's store from a finished Manifest, a direct work request, an open question, or follow-up findings from another Ticket. A Manifest becomes one coherent Shaped Ticket by default; split it by Deliverable only when the caller explicitly wants delegation or parallel pickup. Use…
Walk through a PR or large diff together — your own or someone else's — one sub-changeset at a time and one review topic at a time within it. Use when reviewing a substantive PR collaboratively, walking a large refactor, or when the user asks to walk a PR, walk a diff, explain a PR, review collaboratively, or review a…
Design and build user-visible artifacts — pages, dashboards, tools, documents, reports, decks, infographics, posters, forms, emails, games, explorables. Names the purpose, then writes a task model — who is at it, the loop they repeat, what must stay co-visible during it — that the layout has to trace to, asking once…
Review a user-visible artifact against design standards — a page, dashboard, tool, document, report, deck, infographic, poster, form, email, game, or explorable. Renders the artifact (BLOCKED when it cannot), runs machine checks, exercises its states and behavior, and reports graded findings with the fix. Use when…
Create a BRANDGUIDELINES.md that defines how to communicate with your customer. Requires CUSTOMER.md to exist first. Covers voice, tone, language rules, messaging framework, and copy patterns.
Iteratively craft a CUSTOMER.md document that precisely defines your ideal customer profile (ICP). This is the foundational document from which everything else (product, features, brand) derives. Uses parallel research agents and multi-choice workflow with feedback cycles.
Create a DESIGNGUIDELINES.md that defines how to design UI/UX for your customer. Requires CUSTOMER.md to exist first. Covers aesthetic direction, design tokens, typography, color, motion, components, and layout patterns. Bakes in frontend-design skill principles to avoid generic AI aesthetics.
Create a comprehensive SEOSTRATEGY.md covering both traditional SEO and Generative Engine Optimization (GEO) for AI platforms. Requires CUSTOMER.md to exist first. Includes platform-specific tactics for Google AI Overviews, ChatGPT, Perplexity, Claude, and Gemini with effort/impact prioritization.
Creates personalized X/Twitter growth strategy through guided interview. Based on algorithm-derived principles (exposure equation, phase model). Use when asked about X growth, Twitter strategy, building audience, or social media presence.
Build a personalized PR review skill by mining GitHub review history. Extracts review patterns, communication style, priorities, and blind spots — generates a calibrated review-as-me skill that posts inline comments on PRs. Use for onboarding, cloning review style, or creating a reviewer persona.
Find all files relevant to a query with orthogonal exploration for comprehensive coverage. Returns topic-specific overview + file list with line ranges. Uses parallel agents for thorough+ levels to ensure nothing is missed.
Autonomously bring a PR to mergeable state. Resolves merge conflicts, fixes CI failures, addresses review comments, syncs PR description, and requests re-review. Designed for unattended cron execution via loop skill. Use when: "prep pr for merge", "make pr mergeable", "fix pr blockers", "autonomous pr maintenance".
Deep web research with parallel investigators, multi-wave exploration, and structured synthesis. Spawns multiple web-researcher agents to explore different facets of a topic simultaneously, launches additional waves when gaps are identified, then synthesizes findings. Use when asked to research, investigate, compare…
Rewrite branch into clean, narrative-quality commits. Creates backup, reimplements on fresh branch, verifies byte-identical, then replaces original branch history.
Create or update CLAUDE.md with best practices - brevity, universal applicability, progressive disclosure.
★not rated 19 todayA25 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: