Agent Skills: building-writing-kits
Build a writing kit, everything a person needs to write a doc themselves (sourced facts, verbatim quotes, the choices a draft made, reader objections, open questions, blanks only they can fill) without the finished prose. Use whenever the user wants material or "inspo" to write a brief, memo, RFC, PR/FAQ, proposal, review, or post in their own words, says they will write it themselves, asks for research or a packet to write from, wants an existing draft taken apart into what went into it, or wants their finished doc checked against the sources.
ID: trevors/dot-claude/building-writing-kits
Install this agent skill to your local
Skill Files
The files that make up building-writing-kits.
More agent skills
- 1k-code-qualityCode quality standards — lint (oxlint), format (oxfmt), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
- error-handlingUse when a task mentions error handling, Wellcrafted Results, result types, defineErrors, trySync, tryAsync, unwrap, thrown exceptions, or deciding whether to propagate, recover from, or present a failure. For recording diagnostics, use logging; for cache lifecycle, use query-layer.
- dev-serverManage Next.js dev servers across worktrees, and the worktrees themselves — create one (`wt new`), find finished ones (`wt stale`), remove them (`wt rm`). Start, stop, and read logs from dev servers. Agents can access logs from any running session, regardless of who started it. Use whenever creating, adding or removing a git worktree in this repo.
- delivery-gateStop hook that blocks Claude from finishing until quality checks pass. Detects rationalization patterns (surface text heuristics), stale learning logs (filesystem mtime), and low disk space. Complements self-audit by mechanically enforcing learning capture habits. Use when Claude should be mechanically blocked from declaring work finished before quality checks and learning capture actually pass.
- plan-treeMaintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.
- write-script-powershellMUST use when writing PowerShell scripts.