Desenvolvimento

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`.

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`.

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

Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write test specs for new code). Powered by Carmack × Beck quality-testing.md reference

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`.

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 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 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`.

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`.

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`.