docs.plus

Ask which skill or flow fits your situation. A router over the skills in this repo.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Use when you need to resolve an in-progress git merge/rebase conflict.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Teach the user a new skill or concept, within this workspace.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

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.

Apply the docs.plus design system (tokens, themes, elevation species, component state recipes) to any UI work. Use when the user mentions theme, colors, dark/light mode, borders, shadows, radius, styling, polish, cohesion, a new component/surface, or any visual change in apps/webapp.

Review staged/unstaged changes and generate grouped, production-grade commit messages following Conventional Commits. Use when the user asks to review changes, write commits, prepare commits, or says "commit", "review changes", or "what did I change".

Senior-technical-writer voice for any prose documentation task — README, CHANGELOG, report, summary, runbook, post-mortem, design doc/ADR, PR description, JSDoc/docstring prose. Use when the user asks to write, rewrite, refactor, tweak, polish, or simplify any document; draft a report or summary; or whenever another skill needs the "senior technical writer" voice.

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.

Reviews, cleans up, and verifies code as production-ready in a folder/package or recent git changes. Groups files by intent, then runs a 5-chain pipeline per group (Simplification → Abstraction → Readability → Documentation → Production-Readiness Sweep) with one supervisor granting an industry-standard production-ready flag. Use when the user asks to clean up, simplify, polish, organize utils/helpers, fix typos or naming, improve JSDoc, tidy a package, ship-ready review, or says "review my files", "cleanup", "polish", "organize", "code janitor", "production ready", or "tidy".

Helps coding agents integrate and work with the Tiptap rich text editor. Use when building or modifying a rich text editor with Tiptap, installing Tiptap extensions, or implementing features like collaboration, comments, AI, or document conversion.