Stats
Actions
Available In
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
AI-powered development tools. 0 agents, 6 commands, and 10 skills for planning, research, design, and workflow automation.
Create engaging changelogs for recent merges to main branch
Enhance a plan with parallel research agents for each section to add depth, best practices, and implementation details
Reproduce and investigate a bug using logs and console inspection
Resolve all TODO comments using parallel processing
Resolve all pending CLI todos using parallel processing
Visually compares live UI implementation against Figma designs and provides detailed feedback on discrepancies. Use after writing or modifying HTML/CSS/React components to verify design fidelity.
Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.
Detects and fixes visual differences between a web implementation and its Figma design. Use iteratively when syncing implementation to match Figma specs.
Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance.
Gathers comprehensive documentation and best practices for frameworks, libraries, or dependencies. Use when you need official docs, version-specific constraints, or implementation patterns.
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step. It applies when a brainstorm or plan document exists and the user wants to improve it.
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
No model invocation
No model invocation
Executes directly as bash, bypassing the AI model
Executes directly as bash, bypassing the AI model
This is a clone with everything I didn't use (and all MCPs) removed.
cd ~/my-claude-plugins
git clone [email protected]:merlyn-huntress/compound-engineering-plugin-no-mcp.git
claude
/plugin
Go to Marketplace > Add Marketplace and enter the full path your checkout - e.g. /Users/me/my-claude-plugins/compound-engineering-plugin-no-mcp.
Within this Marketplace, install the plugin compound-engineering-no-mcp.
/workflows:brainstorm <paragraph of topic that needs exploring>/workflows:plan <paragraph of task to plan>/workflows:work <path to plan.md to implement>/workflows:compoundoriginal plugin README follows:
A Claude Code plugin marketplace featuring the Compound Engineering Plugin — tools that make each unit of engineering work easier than the last.
/plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin
/plugin install compound-engineering
/add-plugin compound-engineering
This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode, Codex, Factory Droid, Pi, Gemini CLI, GitHub Copilot, and Kiro CLI.
# convert the compound-engineering plugin into OpenCode format
bunx @every-env/compound-plugin install compound-engineering --to opencode
# convert to Codex format
bunx @every-env/compound-plugin install compound-engineering --to codex
# convert to Factory Droid format
bunx @every-env/compound-plugin install compound-engineering --to droid
# convert to Pi format
bunx @every-env/compound-plugin install compound-engineering --to pi
# convert to Gemini CLI format
bunx @every-env/compound-plugin install compound-engineering --to gemini
# convert to GitHub Copilot format
bunx @every-env/compound-plugin install compound-engineering --to copilot
# convert to Kiro CLI format
bunx @every-env/compound-plugin install compound-engineering --to kiro
Local dev:
bun run src/index.ts install ./plugins/compound-engineering --to opencode
OpenCode output is written to ~/.config/opencode by default, with opencode.json at the root and agents/, skills/, and plugins/ alongside it.
Codex output is written to ~/.codex/prompts and ~/.codex/skills, with each Claude command converted into both a prompt and a skill (the prompt instructs Codex to load the corresponding skill). Generated Codex skill descriptions are truncated to 1024 characters (Codex limit).
Droid output is written to ~/.factory/ with commands, droids (agents), and skills. Claude tool names are mapped to Factory equivalents (Bash → Execute, Write → Create, etc.) and namespace prefixes are stripped from commands.
Pi output is written to ~/.pi/agent/ by default with prompts, skills, extensions, and compound-engineering/mcporter.json for MCPorter interoperability.
Gemini output is written to .gemini/ with skills (from agents), commands (.toml), and settings.json (MCP servers). Namespaced commands create directory structure (workflows:plan → commands/workflows/plan.toml). Skills use the identical SKILL.md standard and pass through unchanged.
Copilot output is written to .github/ with agents (.agent.md), skills (SKILL.md), and copilot-mcp-config.json. Agents get Copilot frontmatter (description, tools: ["*"], infer: true), commands are converted to agent skills, and MCP server env vars are prefixed with COPILOT_MCP_.
Kiro output is written to .kiro/ with custom agents (.json configs + prompt .md files), skills (from commands), pass-through skills, steering files (from CLAUDE.md), and mcp.json. Agents get includeMcpJson: true for MCP server access. Only stdio MCP servers are supported (HTTP servers are skipped with a warning).
All provider targets are experimental and may change as the formats evolve.
Sync your personal Claude Code config (~/.claude/) to other AI coding tools:
# Sync skills and MCP servers to OpenCode
bunx @every-env/compound-plugin sync --target opencode
# Sync to Codex
bunx @every-env/compound-plugin sync --target codex
# Sync to Pi
bunx @every-env/compound-plugin sync --target pi
# Sync to Droid (skills only)
bunx @every-env/compound-plugin sync --target droid
# Sync to GitHub Copilot (skills + MCP servers)
bunx @every-env/compound-plugin sync --target copilot
npx claudepluginhub merlyn-huntress/compound-engineering-plugin-no-mcpPersonalized coding tutorials that use your actual codebase for examples with spaced repetition quizzes
AI-powered development tools. 29 agents, 24 commands, 18 skills, 1 MCP server for code review, research, design, and workflow automation.
gvkhoslaStructured implementation planning, interactive annotation review, and autonomous plan execution
umputunIterative plan review and execution workflow for Claude Code
serbanghitaSpec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation
NikiforovAllComprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
anthropicsHarness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
affaan-m