Desenvolvimento

Query Claude Code session history via a DuckDB index over `~/.claude/projects/`. Use when asked about Claude Code activity ("how many tokens today?", "what did I work on this week?") or instead of reading, grepping, or jq-ing session transcripts. Not for codebase search, git log queries, or arbitrary databases.

Diagnoses and fixes Java compile errors, runtime exceptions, and stack traces. Use when user asks to "fix this error", "this won't compile", "I'm getting an exception", "debug this", or "build is failing".

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working. NOT

Expert helper for bash scripting, debugging, and best practices

Use when implementing features or writing code. TDD enforcement is opt-in via --tdd / MEOWKIT_TDD=1. Provides code patterns, skill loading, and coding standards.

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Explains Java code in plain language including design patterns. Use when user asks to "explain this code", "what does this do", "help me understand", "walk me through this", or "how does this work".

Triagem de erros de compilação: detecta a linguagem, carrega padrões de correção e tenta novamente automaticamente. Use para 'build failed', 'fix compilation' e 'type error', encadeando com mk:verify. Não é para erros de tempo de execução (mk:fix) ou depuração arquitetural (mk:investigate).

Use when grading a running build behaviorally — drives the artifact via browser/curl/CLI and grades against rubric criteria with concrete evidence. Triggers on /mk:evaluate, "evaluate this build", "grade the running app", "check the running site against the spec", or after a generator iteration completes. NOT for structural code audit of a diff/PR (see mk:review); NOT for static linting (see mk:li

Reading and managing Apple Mail via JXA. Use when working with email, archiving messages, or processing the inbox.

Refining issues with technical context and structured details. Use when expanding a brief bug, feature, or refactor description into a detailed issue suitable for developers and AI agents.

Drives feature work and bug fixes through a tight failing-test-first loop. Trigger when implementing, fixing, or refactoring behavior in a codebase that already has tests. Skip for spikes, visual-only edits, throwaway scripts, and generated files.