claude-config

Make a set of things (code, prose, config, docs) consistent along a dimension the user names, by picking a canonical form and conforming every member to it.

Remove illegal states from data structures by redesigning their types so the illegal states cannot be represented at all.

Remove unnecessary comments from code: tombstones, redundant restatements, and comments a well-named variable or function would replace.

Perform a task with a worker agent, critique it with an adversary agent, and apply the accepted critiques with a reconciler agent.

Replace jargon and imported metaphors in code and prose with concrete, domain-fitting terms a reader understands without translation.

Create a new Claude Code skill following the conventions of existing skills.

Do an editorial review of a post or article and report findings ordered by importance.

Split the current `git` commit into multiple focused, self-contained, easy to review commits.

Resolve conflicts in the current `jj` commit.

Split the current `jj` commit into multiple focused, self-contained, easy to review commits.

Optimize JavaScript library size.

Use when writing, reviewing, or modifying property-based tests, such as those using `fast-check`, or when asked to add test coverage.

Update the project's CLAUDE.md to match its current structure and conventions.

Update implementation to satisfy added, updated, or deleted tests in the current commit.

Add, update, or delete tests for changes in the current commit.

Iteratively improve a context document.

Find opportunities for code reuse in the changed code, both against existing code and within the change itself, without creating bad coupling or contrived abstractions.

Refactor code so each function, class, and module sits at a single level of abstraction and reads top-down as a narrative.

Make prose terse and tight in the style of The Elements of Style by Strunk & White.

Extract a DDD-style ubiquitous language glossary.md file from the current conversation and codebase, flagging ambiguities and proposing canonical terms.

Use when writing, reviewing, or modifying any test files, or when asked to add test coverage.