superpowers

Connects to 100+ external APIs (Google Workspace, GitHub, Slack, Notion, HubSpot, LinkedIn, Airtable, and more) via the Maton API Gateway with managed OAuth. Use when you need to read/write data from any major platform.

Use this agent when working on backend development or infrastructure tasks. Examples: <example>Context: Backend API implementation. user: "I need to create a REST API for user authentication" assistant: [uses backend-infra-specialist to design and implement the API]</example> <example>Context: Infrastructure setup. user: "Help me set up a CI/CD pipeline for my Node.js project" assistant: [uses backend-infra-specialist to create the pipeline]</example> <example>Context: Database design. user: "What's the best way to model this data for high read performance?" assistant: [uses backend-infra-specialist to advise on data modeling]</example>

Use this agent when the user needs to automate web interactions, scrape data from websites, fill forms programmatically, test web UIs, or control a browser with code. Handles: web navigation, clicking, typing, form submission, screenshots, video recording, cookie/session management, network interception, and multi-tab workflows. Uses the agent-browser skill for all browser control. Examples: <example>Context: User wants to automate a login flow. user: "Can you automate logging into this site and scraping the dashboard data?" assistant: [uses browser-automation agent with agent-browser skill]</example> <example>Context: User wants to fill out a form. user: "Fill out this web form with my data automatically" assistant: [uses browser-automation agent to navigate and fill the form]</example> <example>Context: User wants to screenshot pages. user: "Take screenshots of all these URLs and save them" assistant: [uses browser-automation agent to batch screenshot]</example>

Use this agent when the user is working with Kirby CMS — building pages, editing blueprints, creating templates/snippets, debugging Kirby runtime, querying content, or managing a Kirby project. Uses the kirby-mcp skill for all runtime inspection and content operations. Examples: <example>Context: User is building a Kirby site. user: "Build a contact form page in my Kirby project" assistant: [uses cms-developer agent with kirby-mcp skill]</example> <example>Context: User wants to inspect their Kirby setup. user: "Show me all the blueprints in my Kirby project" assistant: [uses cms-developer agent to list blueprints via MCP]</example> <example>Context: User is debugging Kirby. user: "My home page isn't rendering correctly, help me debug it" assistant: [uses cms-developer agent to render and diagnose]</example>

Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>Since a major project step has been completed, use the code-reviewer agent to validate the work against the plan and identify any issues.</commentary></example> <example>Context: User has completed a significant feature implementation. user: "The API endpoints for the task management system are now complete - that covers step 2 from our architecture document" assistant: "Excellent! Let me have the code-reviewer agent examine this implementation to ensure it aligns with our plan and follows best practices" <commentary>A numbered step from the planning document has been completed, so the code-reviewer agent should review the work.</commentary></example>

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting.

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.

1 hook across 1 event