writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

@mattpocockTypeScript wizard. Building Total TypeScript - a comprehensive, production-grade TypeScript course. Ex-Vercel, Stately.
TypeScript wizard. Building Total TypeScript - a comprehensive, production-grade TypeScript course. Ex-Vercel, Stately.
Curated from public sources. This profile has not been claimed.
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Stop. That last message did not land: re-pitch it.
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Teach the user a new skill or concept, within this workspace.
Compact the current conversation into a handoff document for another agent to pick up.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
A relentless interview to sharpen a plan or design.
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
Writing, exploit: shape raw material into an article, paragraph by paragraph.
Writing, explore: mine raw fragments, no structure yet.
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.
Conduct a retrospective on a coding session.
Grill me about specs for the workflows I want to build, within this workspace.
Implement a specification in code.
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.