Desenvolvimento

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.

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.

Use when writing or refactoring modern C# with maintainability and performance standards. Keywords: coding standards, C# best practices, refactor C#, records, pattern matching, async best practices.

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.

Resolve an active merge or rebase conflict, including safe renumbering of colliding plans and chronicles.

Critique the user's plan from plan.md

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", "подумай глубоко"

Automated full-scope reconnaissance starting from a domain or domain list. Performs subdomain enumeration, port scanning, technology fingerprinting, OSINT correlation, Google dorking, and Wayback analysis. Use when user provides a domain or list of domains and asks for "recon", "reconnaissance", "attack surface mapping", "subdomain enumeration", "footprinting", or "information gathering". Designed