compound-engineering

Report a bug in the compound-engineering plugin

Triage and categorize findings for the CLI todo system

Create engaging changelogs for recent merges to main branch

Create or edit Claude Code skills with expert guidance on structure and best practices

Enhance a plan with parallel research agents for each section to add depth, best practices, and implementation details

Use this agent when you need to verify that a UI implementation matches its Figma design specifications. This agent should be called after code has been written to implement a design, particularly after HTML/CSS/React components have been created or modified. The agent will visually compare the live implementation against the Figma design and provide detailed feedback on discrepancies. Examples: - <example> Context: The user has just implemented a new component based on a Figma design. user: "I've finished implementing the hero section based on the Figma design" assistant: "I'll review how well your implementation matches the Figma design." <commentary> Since UI implementation has been completed, use the design-implementation-reviewer agent to compare the live version with Figma. </commentary> </example> - <example> Context: After the general code agent has implemented design changes. user: "Update the button styles to match the new design system" assistant: "I've updated the button styles. Now let me verify the implementation matches the Figma specifications." <commentary> After implementing design changes, proactively use the design-implementation-reviewer to ensure accuracy. </commentary> </example>

Use this agent PROACTIVELY when design work isn't coming together on the first attempt. If you've made 1-2 design changes and the result still feels off, suggest using this agent with 5x or 10x iterations for deeper refinement. This agent takes screenshots, analyzes what's not working, implements improvements, and repeats N times to systematically fix design issues. Perfect when colors feel wrong, layouts aren't balanced, or the overall aesthetic needs work that single changes can't achieve. <example>Context: User asks to change button color but result still looks off. user: "Change the button to blue" assistant: [makes change, takes screenshot] "The button is now blue, but I notice the overall color balance still feels off. Would you like me to use the design-iterator agent with 5 iterations to systematically improve the color harmony and visual balance?" <commentary>PROACTIVE USE: After a simple change doesn't fully resolve the design issue, suggest the design-iterator to do deeper work.</commentary></example> <example>Context: User's design request leads to something that doesn't look right. user: "Make the hero section more modern" assistant: [makes initial changes] "I've added some modern elements, but the result isn't quite coming together. This looks like it needs iterative refinement. Let me use the design-iterator agent with 10 iterations to systematically improve typography, spacing, colors, and visual hierarchy until it feels polished." <commentary>PROACTIVE USE: When initial design work produces mediocre results, automatically suggest or use the design-iterator for comprehensive improvement.</commentary></example> <example>Context: User wants explicit iterative refinement. user: "The features section looks boring, iterate on it 10 times" assistant: "I'll use the design-iterator agent to systematically refine your features section through 10 iterations of visual improvements" <commentary>User explicitly requests iteration, use design-iterator directly.</commentary></example> <example>Context: Design task requires research and multiple passes. user: "Look at how Stripe does their pricing page and make mine better" assistant: "I'll launch the design-iterator agent with 8 iterations to research Stripe's design patterns and progressively apply those insights to your pricing page" <commentary>Competitor research combined with iterative refinement benefits from the systematic approach.</commentary></example>

Use this agent when you need to review and edit text content to conform to Every's specific style guide. This includes reviewing articles, blog posts, newsletters, documentation, or any written content that needs to follow Every's editorial standards. The agent will systematically check for title case in headlines, sentence case elsewhere, company singular/plural usage, overused words, passive voice, number formatting, punctuation rules, and other style guide requirements.

Use this agent when you need to synchronize a web implementation with its Figma design by automatically detecting and fixing visual differences. This agent should be used iteratively until the implementation matches the design. <example> Context: User has just implemented a new component and wants to ensure it matches the Figma design. user: "I've just finished implementing the hero section component. Can you check if it matches the Figma design at https://figma.com/file/abc123/design?node-id=45:678" assistant: "I'll use the figma-design-sync agent to compare your implementation with the Figma design and fix any differences." <uses Task tool to launch figma-design-sync agent with the Figma URL and local URL> </example> <example> Context: User is working on responsive design and wants to verify mobile breakpoint matches design. user: "The mobile view doesn't look quite right. Here's the Figma: https://figma.com/file/xyz789/mobile?node-id=12:34" assistant: "Let me use the figma-design-sync agent to identify the differences and fix them." <uses Task tool to launch figma-design-sync agent> </example> <example> Context: After initial fixes, user wants to verify the implementation now matches. user: "Can you check if the button component matches the design now?" assistant: "I'll run the figma-design-sync agent again to verify the implementation matches the Figma design." <uses Task tool to launch figma-design-sync agent for verification> </example> <example> Context: User mentions design inconsistencies proactively during development. user: "I'm working on the navigation bar but I'm not sure if the spacing is right." assistant: "Let me use the figma-design-sync agent to compare your implementation with the Figma design and identify any spacing or other visual differences." <uses Task tool to launch figma-design-sync agent> </example>

Use this agent when you need to create or update README files following the Ankane-style template for Ruby gems. This includes writing concise documentation with imperative voice, keeping sentences under 15 words, organizing sections in the standard order (Installation, Quick Start, Usage, etc.), and ensuring proper formatting with single-purpose code fences and minimal prose. Examples: <example>Context: User is creating documentation for a new Ruby gem. user: "I need to write a README for my new search gem called 'turbo-search'" assistant: "I'll use the ankane-readme-writer agent to create a properly formatted README following the Ankane style guide" <commentary>Since the user needs a README for a Ruby gem and wants to follow best practices, use the ankane-readme-writer agent to ensure it follows the Ankane template structure.</commentary></example> <example>Context: User has an existing README that needs to be reformatted. user: "Can you update my gem's README to follow the Ankane style?" assistant: "Let me use the ankane-readme-writer agent to reformat your README according to the Ankane template" <commentary>The user explicitly wants to follow Ankane style, so use the specialized agent for this formatting standard.</commentary></example>

This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. Triggers on "edit for style", "review article", "check grammar", "Every style guide", "proofread", "copy edit", or requests to check written content for grammar, punctuation, mechanics, and style compliance.

This skill should be used when managing file-based todos in the todos/ directory. Triggers on "create a todo", "add todo", "triage todos", "list pending items", "manage work items", "track technical debt", or requests to create, complete, or manage development tasks using markdown-based todo files.

This skill should be used when creating distinctive, production-grade frontend interfaces. Triggers on "build a landing page", "create a component", "design a UI", "make a web page", "build frontend", "React component", "Vue component", or requests for visually striking, memorable web interfaces that avoid generic AI aesthetics.

This skill should be used when building AI agents using prompt-native architecture where features are defined in prompts, not code. Use it when creating autonomous agents, designing MCP servers, implementing self-modifying systems, or adopting the "trust the agent's intelligence" philosophy.

This skill should be used when writing Ruby gems following Andrew Kane's patterns. Triggers on "create a gem", "write a Ruby library", "Andrew Kane style", "gem API design", "minimal gem", "Searchkick patterns", or requests for clean, dependency-free, production-ready Ruby library code.