erikdarling

Trade-offs to check before shipping SQL Server code: 54 cards from the Before You Ship That chart, each with one action and what it costs, what it risks, how fast it works, and when it backfires. Covers new and existing queries, tables, and indexes.

1 skill

Read a SQL Server execution plan and explain what is actually slow, and why. Prevents the standard wrong conclusions: cost percentages read as measurements, operators ranked by cumulative time, estimated rows compared to actual without dividing by executions, and missing-index DDL pasted verbatim.

1 skill

Refuses a subagent spawn that names a pinned model id, and enforces your own per-agent-type model rules.

A band above the prompt listing each question the session is waiting on from you, with the recommended answer, trimmed as each is answered. Adds ask_add, ask_resolve and ask_list tools for the model and an /asks command.

Keeps a registry of interactive sessions so /resume-sessions can list and reopen the ones a crash, reboot or closed terminal interrupted. Windows, PowerShell, WezTerm or Windows Terminal.

A band above the prompt with each running subagent's type, model, effort, steps, context, advisor calls and estimated cost, plus a /fleet pane, /steer, /subagent-cost and a subagent_vitals tool.

Refuses force-pushes, pushes to protected branches, git commands that skip hooks and kills by process name; optionally bans folders, keeps subagents out of shared checkouts and stops whole-file reads of big files.

A wall-clock limit for subagents (a warning, then only git, gh and .md/.txt writes) and a nudge for a code-changing subagent that has used a lot of context without editing a file.

Warns as the account's 5-hour and 7-day usage windows fill, tells the model as they near the limit, and refuses new subagents past a set percent.