Explorar skills

Enforces strict test-driven development. Use when implementing ANY feature, bugfix, or refactor — before writing implementation code. Also use when someone says 'add tests', 'write tests', 'test this', 'TDD', or when you're about to write production code of any kind. If you're about to write code and there isn't a failing test for it yet, STOP and use this skill.

Execute qualquer pergunta, plano, PR ou código através de um conselho de Debate Multiagente Diverso (DMAD) composto por 5 consultores de IA com métodos de raciocínio distintos. Os consultores colaboram, revisam-se anonimamente e um presidente sintetiza um veredito, superando empiricamente o debate adversarial.

Desenvolvimento de aplicações CLI em Golang. Utilize ao construir, modificar ou revisar uma ferramenta CLI em Go, focando em estrutura de comandos, manipulação de flags, configuração, versão, códigos de saída, I/O, tratamento de sinais, autocompletar de shell, validação de argumentos e testes unitários. Também aciona quando o código usa cobra, viper ou urfave/cli.

A especificação do processo de teste de unidade Zinc da War3Lib utiliza TaskCreateUT.lua para gerar shells de teste, gerencia injeção de cfg e dependências de cadeia, e emprega UnitTestFramework.assert para asserções e Trace para registro. É usada ao criar ou refatorar testes de unidade de módulos Jass.

Orienta usuários em storytelling, comunicação e influência com 45 técnicas testadas por profissionais do arquivo de Lenny Rachitsky. Ideal para apresentações, conversas com stakeholders, comunicações executivas, pitch de ideias e melhoria da persuasão.

Use when about to claim work is complete, fixed, passing, or done — before committing, creating PRs, or moving to the next task. Also use when you're about to say 'Done!', 'All tests pass', 'Ready for review', 'Fixed', or ANY positive statement about work state. If you haven't run the verification command in this message, you cannot claim it passes.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Use this skill when validating a backend API or WebSocket endpoint end-to-end, including acquiring an OIDC bearer token for authenticated calls. Trigger whenever the user asks to test/validate/smoke-check a backend, write a Hurl test, hit a WebSocket, acquire an access token, exercise an OIDC flow, debug a 401, or verify an endpoint works with real auth. Applies to projects that use Hurl for HTTP

MSW handlers, browser/server workers, test data. Use when setting up API mocking for development or testing, creating mock handlers with variants, or sharing mocks between browser and Node environments.

Use when you need CRAP score and coverage risk analysis to find high-risk code before refactoring or release. Keywords: CRAP score, risk hotspots, cyclomatic complexity, test coverage gaps, coverage threshold.

Deep reasoning mode. Exhaustive analysis with stress-tested assumptions. Triggers: "ultrathink", "/ultrathink", "think deeply", "подумай глубоко"

Use before ANY creative work — creating features, building components, adding functionality, modifying behavior, or starting a new project. Also use when someone says 'build', 'create', 'add', 'implement', 'let's make', or describes something they want built. Do NOT write code until a design is approved and a plan is written.