All Skills

`task-agent`/`review-agent`: use when broker delivery, ordering, acknowledgement, DLQ, backpressure, or replay changes; skip synchronous retry without message semantics.

Select evidence-bearing context for a downstream consumer after work when claims, artifacts, validation, unresolved decisions, or omissions must cross a boundary.

`analysis-agent`/`task-agent`/`review-agent`: use when fixtures, factories, seeds, isolation, cleanup, or sensitive test-data rules change; skip when test data is unaffected.

`analysis-agent`/`task-agent`: use when commit timing, payloads, schema, ordering, idempotency, or retry changes; skip when no domain-event decision is required.

`analysis-agent`/`task-agent`/`review-agent`: use when Go context, goroutine, channel, error, interface, or resource semantics affect behavior; skip generic or non-Go work.

`analysis-agent`/`task-agent`/`review-agent`: use when latency, throughput, bundle, memory, CPU, query, rendering, or resource cost needs a budget; skip without performance risk.

Use `task-agent` to update source-backed documentation or `review-agent` to assess documentation impact and accuracy when public behavior or operator workflows change. Skip work with no audience-facing behavior change.

Analyze an API, schema, migration, or compatibility decision with `analysis-agent`, or implement its bounded contract change with `task-agent`. Do not select it when no data or public-contract surface is affected.

Use `analysis-agent` to map user-flow, interaction-state, accessibility, content, and recovery impact when experience behavior changes. Skip backend-only work with no experience effect and question-only requests.

`analysis-agent`/`task-agent`/`review-agent`: use when merges, rebases, conflicts, history rewrite, generated files, or recovery need evidence; skip when Git is irrelevant.

`task-agent`/`review-agent`: use when structured errors, logs, correlation, redaction, propagation, or safe diagnostics change; skip when logging/error handling is unaffected.

`analysis-agent`/`task-agent`/`review-agent`: use when a service split affects ownership, deployment, scaling, isolation, contracts, or data; skip without a split decision.

`analysis-agent`/`task-agent`/`review-agent`: use when personal-data purpose, retention, deletion, sharing, telemetry, or provider handling changes; skip legal-only work.

`analysis-agent`/`task-agent`/`review-agent`: use for structure, workspace or package bootstrap, config, scripts, or quality gates; skip without an initialization decision.

`analysis-agent`/`task-agent`/`review-agent`: discover source of truth, candidate owner, and change surface before planning; hand known candidates to impact inspection.

`analysis-agent`/`task-agent`: use when a use case coordinates authorization, domain work, transactions, or external effects; skip transport, storage, and rule-only work.

`analysis-agent`/`task-agent`/`review-agent`: use when authoring SKILL.md, triggers, decisions, references, registry, routing, or validation; skip when no Skill content changes.

`analysis-agent`/`task-agent`/`review-agent`: use when SQL changes affect NULL, cardinality, constraints, locks, precision, or dialect semantics; skip tool-only work.

Analyze candidate task nodes, dependencies, collisions, and critical path before a consumer accepts or rejects a final DAG.

Use `analysis-agent` for integration decisions or `task-agent` for cross-system/external changes involving contracts, retries, idempotency, authentication, or reconciliation. Skip isolated work with no integration edge.

Use when an installed-client change has a confirmed iOS or iPadOS target and changes Apple mobile platform behavior.

`analysis-agent`/`task-agent`/`review-agent`: use when uploads, object storage, streaming, MIME, scanning, access, retention, or cleanup changes; skip without file/storage impact.

`analysis-agent`/`task-agent`/`review-agent`: use when repeated failure needs a new hypothesis or proof path; skip an initial failure with verified cause and a different action.

`analysis-agent`: use when raw requests need behavior, actors, scope, non-goals, constraints, deliverables, acceptance, or test traceability; skip when structure already exists.

`task-agent`: use when local, server, global, derived, optimistic, persisted, form, auth, or cache state ownership changes; skip when state boundaries are unaffected.

`analysis-agent`/`task-agent`/`review-agent`: use when behavior needs deterministic seams for time, randomness, UUIDs, collaborators, or external I/O; skip when seams are adequate.

Use with analysis-agent or task-agent for task-local transaction, isolation, and conflict decisions. Do not use without a transaction decision or as task owner.

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt engineering that scales, AI UX that users trust, and cost optimization that doesn't bankrupt you. Use when: keywords, file_patterns, code_patterns.

Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.

Semantic search, similar content discovery, and structured research using Exa API

Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.