Mine every Claude Code session across all projects for the two things that decide a task's cost - how many tool calls it took and how many wall-clock minutes the user waited - and for token, character, latency, memory and productivity waste down to the individual character; mine the call sequences for composites…
Cut a release — derive the version, close the review, rewrite CHANGELOG, commit, push, wait for CI, tag, wait for the Release workflow and the GitHub release, then wait until the version is live on NuGet.
Implement every open row in IMPROVEMENTS.md, close them, update the docs, verify, commit, push, wait for CI green, cut a release, and wait until the version is live on NuGet.
Re-derive the MCP tool surface from source, bring every repo document back in sync with it, verify with the census gates, then commit and push. No review subagent.
Instructions for amusleh-spotware-com/terse-sharp, covering claude.md, what this is, 🚫 hard gate — develop tersesharp with tersesharp, commands and one project / one test.
Use when reading, searching, navigating, editing, refactoring, building or testing C#/.NET, XAML, .resx localization or Razor/Blazor in a solution served by the TerseSharp MCP server. Teaches which TerseSharp tool replaces which built-in, and how to drive all 88 of them, so a .cs file is never read whole, a symbol is…