Restate the previous response plainly and concisely. Use only when the user explicitly asks for a simpler human explanation or invokes bro.
Apply correct-by-construction TypeScript engineering standards covering boundary parsing, typed failures, domain modeling, module boundaries, dependency injection, testing, and type safety. Use when writing or reviewing TypeScript.
Audit installed Agent Skills for duplicate copies, unused candidates, oversized descriptions, loaded roots, and prompt-budget pressure. Use when cleaning or debugging skill collections across common agent runtimes.
Apply concrete clarity, concision, structure, grammar, and plain-English checks when editing prose, reviewing drafts, writing reports or articles, or teaching clear writing.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Produce an implementation-ready technical specification using typed contracts, concrete module boundaries, call stacks, data flows, alternatives, file changes, and vertical red-green test slices. Use when the user asks for a tech spec or architecture handoff.
Plan and safely execute tool installations or upgrades only when the user explicitly asks. Covers package managers, CLIs, GitHub releases, desktop apps, setup scripts, environment impact, rollback, and verification. Never modifies the system without explicit user approval.
Edit drafts that sound generic, inflated, repetitive, or conspicuously machine-written. Use when the user asks to deslopify, remove AI mannerisms, make prose sound natural, or preserve their voice while tightening a generated draft.