Desenvolvimento

通过 SSH 或 Docker 使用 Kali Linux CLI 工具执行授权渗透测试。 覆盖：信息收集、漏洞分析、嗅探与欺骗、Web/API 渗透、漏洞利用、密码攻击、无线、云原生安全、RFID/NFC、VoIP/ICS、逆向工程、取证分析、后渗透/C2、报告生成。

The Mileva Method (CRISP) — Phase 1: Clarify. Problem definition, eliciting, painkiller test, buy vs build, AI justification gate, Go/No-Go. Use at the start of any AI implementation project. Triggers on "clarify", "phase 1", "start discovery", "define the problem", "what problem are we solving", or at the beginning of a new client engagement.

Ganchos de segurança para Claude Code – 700 ganchos pré-construídos que previnem exclusão de arquivos, vazamento de credenciais, desastres com Git e desperdício de tokens durante sessões autônomas de codificação com IA. Com mais de 9.200 testes, instale-os usando npx cc-safe-setup.

Gera casos de teste de software. Suporta a saída de casos de teste agrupados por módulo.

TRIGGER when: user asks to trace a specific route, schema object, file, table, RPC, or error string through its evidence. Covers `route_trace`, `schema_usage`, `file_health`, `auth_path`, `trace_file`, `preflight_table`, `trace_edge`, `trace_error`, `trace_table`, `trace_rpc`.

TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r

TRIGGER when: user asks about relationships, dependency paths, import hotspots or cycles, symbol impact, or blast radius of a proposed change. Covers `graph_neighbors`, `graph_path`, `flow_map`, `change_plan`, `imports_deps`, `imports_impact`, `imports_hotspots`, `imports_cycles`, `symbols_of`, `exports_of`.

Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.

Padrões de programação assíncrona para JavaScript/TypeScript, Python e outras linguagens.