clarinovist

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.

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,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.

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," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

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,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

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," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

When the user wants to review, edit, or improve existing website and marketing copy, especially requests like "review copy", "audit copy website", "polish landing page copy", "improve messaging", "tighten this text", or "copy feedback". Use this for existing copy in frontend/src and frontend/docs. For rewriting from scratch, hand off to copywriting. For structural conversion issues (section flow, CTA placement, friction), hand off to page-cro.

Generate a conventional commit message from staged/unstaged changes and automatically commit.

Create a structured implementation plan for a new feature, refactor, or infrastructure change. Outputs a machine-readable markdown plan with phases, tasks, requirements, and testing criteria.

Create optimized multi-stage Dockerfiles for Next.js frontend and FastAPI backend. Smaller images, non-root user, healthcheck, pinned versions.

Generate a Playwright TypeScript E2E test for a given scenario. Navigates the app step-by-step, uses role-based locators, and saves the test in tests/e2e/.

PostgreSQL query optimization and schema review. Covers EXPLAIN ANALYZE, indexing strategy, JSONB, pagination, and security (parameterized queries).

Run pytest with coverage, identify uncovered lines, and iteratively add tests until 100% coverage is reached.

Surgical code refactoring to improve maintainability without changing behavior. Use for gradual improvements: extract functions, eliminate code smells, improve type safety, apply design patterns.

Document and explain PolyFlow architecture, data flow, service boundaries, and extension points for the Next.js, Prisma, and PostgreSQL stack.

Plan PolyFlow deployments, database migrations, container rollouts, verification checks, and rollback steps for production-safe releases.

Create PolyFlow quality playbooks, test plans, and risk audits for inventory, production, finance, purchasing, sales, auth, and deployment-sensitive flows.

Provides the single source of truth for brand guidelines, design tokens, technology choices, and voice/tone. Use this skill whenever generating UI components, styling applications, writing copy, or creating user-facing assets to ensure brand consistency.

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

Generates detailed implementation plans for complex coding tasks. Use when the user has requirements but needs a structured plan before coding.