Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate. Use when you have an enterprise-design, visual-system-architect, or copywriting output and need to convert it into Figma Make–compatible prompts covering hero, features, social proof, CTA, and mobile…
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description. Use when you have a bug report or failing test and want Claude to investigate and fix without step-by-step guidance.
When the user wants to optimize any form that is NOT signup/registration — lead capture, contact, demo request, application, survey, or checkout forms; "form friction," "form completion rate," "form abandonment," "too many fields," "nobody fills out our form." For signup/registration forms, see signup-flow-cro. For…
When the user wants to plan or build a free tool for marketing — "engineering as marketing," "lead gen tool," "ROI calculator," "generator," "grader tool," "audit tool," "should I build a free tool," or giving away something useful to attract leads or links. For content-based lead generation, see content-strategy.
MANDATORY before every commit and push. All gates must pass — Gates 1–3 always run; Gates 4 (Docker) and 5 (Cloud) run only when applicable. Do NOT proceed if any gate fails — fix the issue first.
Adversarial code review before a PR — Claude asks hard questions until you pass the test. Also supports elegant rewrites ("scrap this and implement the elegant solution") and spec-driven development. Use before opening any pull request. For mechanically finding bugs in a diff, prefer a platform-native code-review…
Act as a Senior Frontend Systems Engineer to architect interactive modules — multi-step forms, pricing calculators, faceted search, dashboards, and auth flows. Defines state machines, data flow, error handling, and React component structure. Use when designing complex UI logic for Figma Make prototypes or React…
You are a senior engineering lead and product architect. Given an observation, bug, or gap, conduct a thorough multi-dimensional investigation, find the root cause, plan the resolution, and create a detailed actionable GitHub issue.
When the user wants to plan a product launch, feature announcement, or release strategy — 'Product Hunt,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'launch checklist,' 'GTM plan,' 'we're about to ship.' For ongoing marketing after launch, see marketing-ideas.
You are a release engineer. Execute each phase in order. Each must fully complete before advancing. Do NOT ask for permission. Stop only if something is truly unfixable.
When the user needs marketing ideas, inspiration, or growth strategies for their SaaS or software product — 'how to market,' 'ways to promote,' 'what else can I try,' 'no idea how to market this,' 'brainstorm marketing.' The starting point when someone is stuck on growth. For channel execution, see the relevant skill…
When the user wants to apply psychology, mental models, or behavioral science to marketing — 'cognitive bias,' 'persuasion,' 'why people buy,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' 'nudge' — or to understand how buyers think and decide.
Act as a Senior Motion Designer to specify and ship purposeful UI animation — micro-interactions, transitions, scroll-driven sequences, page transitions, loading states. Outputs easing/duration tokens, Framer Motion + GSAP recipes, and prefers-reduced-motion strategies. For implementing with the Motion/Framer Motion…
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value — "activation rate," "empty states," "onboarding checklist," "aha moment," "users sign up but don't use the product." Use when users sign up but don't stick around. For signup/registration optimization, see…
Apply the Workflow Orchestration methodology for complex, multi-step tasks — plan-first approach, subagent strategy, self-improvement loop, verification before done, elegant solutions, and autonomous bug fixing. Use for any non-trivial task with 3+ steps or architectural decisions.
When the user wants to increase conversions on any marketing page — homepage, landing, pricing, feature, or blog; "CRO," "this page isn't converting," "low conversion rate," "bounce rate," "my landing page sucks" — or just shares a URL asking for feedback. For signup flows, see signup-flow-cro; post-signup activation…
When the user wants help with paid advertising on Google Ads, Meta, LinkedIn, or Twitter/X — 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'retargeting,' 'audience targeting,' 'ad budget,' 'should I run ads.' Covers campaign strategy, targeting, bidding, and optimization. For bulk ad creative, see ad-creative. For landing…
Coder reviewer handoff loop (claude/codex/cursor, roles swappable) with self-instrumented per-round cost tracking. Loops locally via HANDOFF.md until approved, then opens a PR with the full transcript.
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates — "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached," "free users won't upgrade." Covers in-product upgrade moments where the user has already experienced value — distinct…
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion — "exit intent," "lead capture popup," "email popup," "announcement banner," "scroll trigger," "sticky bar," or any interrupt-style conversion element. For forms outside popups, see form-cro. For page-level…
When the user wants help with pricing, packaging, or monetization — 'pricing tiers,' 'freemium,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'how much should I charge,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan.' For in-app upgrade screens, see paywall-upgrade-cro.
When the user wants to create or update their product marketing context document — 'positioning,' 'ICP,' 'ideal customer profile,' 'who is my target audience,' or avoiding repeated foundational info across marketing tasks. Run at the start of a project: it creates .agents/product-marketing-context.md, which all other…