100xprism

When the user wants to write, rewrite, or improve marketing copy for any page — homepage, landing, pricing, feature, about, or product pages; "headline help," "CTA copy," "value proposition," "tagline," "hero section," "make this more compelling," "conversion copy," or complete Figma-ready full-page copy (see Full-Page Mode below). For email copy, see email-sequence. For popups, see popup-cro. For editing existing copy, see copy-editing.

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, onboarding-cro; forms, form-cro; popups, popup-cro.

When the user wants to audit or diagnose SEO issues — "technical SEO," "why am I not ranking," "meta tags review," "my traffic dropped," "Google update hit me," "core web vitals," "crawl errors," "indexing issues," or even a vague "my SEO is bad." For pages at scale, see programmatic-seo. For structured data, see schema-markup. For AI search, see ai-seo.

Coder<->reviewer handoff loop (Claude<->Codex, roles swappable) with self-instrumented per-round cost tracking. Loops locally via HANDOFF.md until approved, then opens a PR with the full transcript.

Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.

When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.

When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.

When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.

Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.

When the user wants to reduce churn or build retention systems — 'cancel flow,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'customers are leaving.' For post-cancel win-back sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

Rigorous security and data privacy scan for cloud deployments. Covers GCP infrastructure hardening, data privacy (PII/GDPR/CCPA), API security, container security, and compliance. Audits deployed infrastructure and config — not a code-diff review.

Write B2B cold emails and follow-up sequences that get replies — "cold outreach," "prospecting email," "outbound email," "SDR emails," "nobody's replying to my emails." Covers subject lines, openers, body copy, CTAs, personalization, and multi-touch follow-ups. For warm/lifecycle sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

Quality gate runs FIRST. **Do NOT commit if any gate fails.**

When the user wants competitor comparison or alternative pages for SEO and sales enablement — 'alternative page,' 'vs page,' '[Product] vs [Product],' 'battle card,' 'competitor teardown.' Covers four formats: singular/plural alternatives, you vs competitor, competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

Connect, authenticate, and verify any SaaS CLI tool. Reads credentials from `.env`. Never prints secrets.

When the user wants to plan content strategy or decide what topics to cover — "what should I write about," "blog strategy," "topic clusters," "editorial calendar," "content pillars," "content roadmap," "I don't know what to write." For writing individual pieces, see copywriting. For SEO audits, see seo-audit. For social media, see social-content.

When the user wants to edit, review, or improve existing marketing copy — 'edit this copy,' 'proofread,' 'polish this,' 'tighten this up,' 'too wordy,' 'sharpen the messaging.' Use when copy exists and needs improving, not rewriting from scratch. For writing new copy, see copywriting.

Act as a Senior Data Visualization Designer for dashboards, analytics pages, and chart-driven UI built in Recharts / visx / D3 / Plotly — chart-type decision tree, dashboard layout heuristics, color-blind safe palettes, empty/loading/error states, library trade-offs. For a one-off chart or plot, prefer a platform-native charting skill (e.g. dataviz) when present.

Connect to any database — Cloud SQL, PostgreSQL, Snowflake, Databricks, Athena, Presto, or Oracle.

When the user wants to create or optimize an email sequence, drip campaign, or lifecycle email program — "nurture sequence," "onboarding emails," "welcome series," "re-engagement," "email automation," "email cadence," or any multi-email automated flow. For cold outreach, see cold-email. For in-app onboarding, see onboarding-cro.

Run a 100xprism module's evals to check it triggers correctly and produces good output — "do my skills still trigger correctly," "did this change break a skill." Fans eval cases out to parallel subagents with Haiku-graded pass/fail scorecards. For authoring or benchmarking general-purpose skills, prefer a skill-creator plugin when present.

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 popups containing forms, see popup-cro.

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 skill; this is the human-gate interrogation.

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.

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 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.

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 (paid-ads, social-content, email-sequence, etc.).

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 library itself, prefer a motion-framer plugin skill when present; use this for the motion design spec and audit.

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 signup-flow-cro. For email sequences, see email-sequence.

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 pages, see page-cro.

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 from public pricing pages (see page-cro). For pricing decisions, see pricing-strategy.

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 conversion, see page-cro.

Create a GitHub Pull Request with full AI review. Human approves and merges.

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 marketing skills read.

When the user wants SEO pages generated at scale from templates plus a dataset — "programmatic SEO," "pSEO," "directory pages," "location pages," "[keyword] + [city] pages," "integration pages," "generate 100 pages," "templated landing pages." For auditing an existing site, see seo-audit. For planning, see content-strategy.