Explorar skills

This skill should be used when facing complex architecture decisions, multi-step root cause analysis, comparing multiple approaches with trade-offs, debugging that requires hypothesis tracking, planning with branching possibilities, or any problem requiring structured step-by-step reasoning with potential revisions. Trigger phrases include 'think through this', 'analyze step by step', 'reason abou

Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and configures test runners. Use when the user asks to "generate tests", "write unit t

Orientação conceitual para Adobe Analytics que explica conceitos centrais (eVars, props, eventos), ajuda a projetar abordagens de rastreamento, suporta fluxos de trabalho de análise e esclarece tópicos de administração/governança. Não se conecta a dados em tempo real.

Vendor-agnostic lab automation framework. Use when controlling multiple equipment types (Hamilton, Tecan, Opentrons, plate readers, pumps) or needing unified programming across different vendors. Best for complex workflows, multi-vendor setups, simulation. For Opentrons-only protocols with official API, opentrons-integration may be simpler.

Esta skill deve ser usada para gerenciar diversos aspectos de um aplicativo no App Store Connect, como upload, atualização de metadados, gerenciamento do TestFlight, tratamento de avaliações, definição de preços, criação de compras no aplicativo e verificação de relatórios de vendas e finanças.

Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics

Systematic root-cause analysis for build failures, test errors, and runtime issues. Use when: "error", "failed", "broken", "debug", "why did this fail", "root cause".

One-question-at-a-time interview to extract what the user wants — each question carries a best-guess + structured options; stop at ~95% confidence. Use when the user says "interview me", "grill me", "I'm not sure what I want", or `/rite-spec` / `/rite-define` flags the ask as underspecified. Not for casual clarification or ideation (use `rite-pressure-test`).

Git staging and commit with smart file grouping. Activated when the user writes "commit", "gca", "make a commit", "commit changes", or after /task, /plan, /do, /review.

Use apenas para diagnosticar, verificar, auditar ou escanear diretórios de skills, diagnosticar skills existentes de agentes de IA locais ou gerar um relatório de saúde de skills local. Não use para criar, instalar, encontrar, recomendar ou aprender a escrever skills.

Gera um bloco de continuação estruturado para transferir o estado do trabalho para uma nova conversa. Use quando o usuário solicitar uma transferência de contexto, entrega ou um bloco para continuar um trabalho específico em um novo chat.

Audit existing UI code against all 30 Laws of UX, scoring compliance 0-60 with prioritized code fixes. Use when user says "review UX", "UX audit", "audit this page", "check UX compliance", "score this UI", "how good is the UX", or "laws-of-ux review".