Receber por email

Explorar skills

9.836 skills encontradas

product-discovery

30

Orientação especializada em descoberta de produto para pesquisa de usuário e validação de problemas. Abrange sprints de descoberta, descoberta contínua e operações de pesquisa, útil para atividades como entrevistas com usuários, testes e análise competitiva.

Design e Frontend #test por ncklrs

performance-marketer

30

Orientação especializada em marketing de performance para aquisição paga, CRO e otimização de crescimento. Utilize para criar campanhas de anúncios, otimizar landing pages, analisar CAC/LTV e planejar estratégias de retargeting em plataformas como Google Ads, Meta Ads e LinkedIn Ads.

Marketing #ai #test por ncklrs

architecture-patterns

30

File-by-file architecture planning with ADR format, dependency ordering, and testability gates. Use when designing system architecture or creating ADRs. TRIGGER when: architecture plan, system design, ADR, file breakdown, component design. DO NOT TRIGGER when: simple config edits, single-file bug fixes, documentation-only changes.

Design e Frontend #test por akaszubski

code-review

30

10-point code review checklist covering correctness, tests, error handling, type hints, naming, security, and performance. Use when reviewing PRs or evaluating code quality. TRIGGER when: code review, PR review, review checklist, code quality check. DO NOT TRIGGER when: writing new code, debugging, refactoring without review context.

Desenvolvimento #test por akaszubski

skill-integration

30

Patterns for agent skill discovery, referencing, and composition using progressive disclosure architecture. Use when building agents, composing skills, or optimizing context usage. TRIGGER when: skill discovery, agent integration, skill composition, progressive disclosure. DO NOT TRIGGER when: implementing features, writing tests, documentation-only changes.

Escrita e Conteúdo #test por akaszubski

quality-scoring

30

Multi-dimensional data assessment for training quality evaluation including IFD scoring, factuality, and reasoning validation. Use when scoring training data or evaluating dataset quality. TRIGGER when: quality scoring, data assessment, IFD, factuality, training data quality. DO NOT TRIGGER when: code quality, test coverage, documentation, non-data tasks.

Dados e Análise #ai #test por akaszubski

planning-workflow

30

7-step planning workflow for pre-implementation design. Enforced by plan_gate hook, critiqued by plan-critic agent. Use when creating plans, design documents, or architecture decisions before implementation. TRIGGER when: plan, planning, /plan, design document, architecture decision. DO NOT TRIGGER when: implementation, coding, testing.

Desenvolvimento #test por akaszubski

scientific-validation

30

Scientific method for validating claims with pre-registration, power analysis, statistical rigor, and Bayesian methods. Use when testing hypotheses, running experiments, or validating claims from papers. TRIGGER when: validate, hypothesis, experiment, backtest, evidence, statistical test. DO NOT TRIGGER when: routine coding, config changes, documentation, non-experimental tasks.

Desenvolvimento #ai #test por akaszubski

refactoring-patterns

30

Safe refactoring techniques — extract, inline, rename, move, simplify conditionals, and decompose functions. Use when restructuring code without changing behavior. TRIGGER when: refactor, extract method, rename, inline, simplify, decompose, clean up, code smell. DO NOT TRIGGER when: adding features, fixing bugs, writing tests, documentation.

Desenvolvimento #test por akaszubski

observability

30

Structured logging, debugging (pdb/ipdb), profiling (cProfile/line_profiler), and performance monitoring. Use when adding logging, debugging issues, or optimizing performance. TRIGGER when: logging, debug, profiling, performance monitoring, metrics, stack trace. DO NOT TRIGGER when: feature implementation, testing, documentation, config changes.

Desenvolvimento #test por akaszubski

error-handling

30

Error handling strategy — exception hierarchies, retry patterns, circuit breakers, graceful degradation, and error boundaries. Use when designing error handling, implementing retries, or building resilient systems. TRIGGER when: error handling, exception, retry, circuit breaker, fallback, graceful degradation, resilience. DO NOT TRIGGER when: writing tests, documentation, config changes, simple bu

Design e Frontend #test por akaszubski

foundry-solidity

29

Endereço de administrador de teste usado em testes de fork.

Design e Frontend #test por tenequm