# documentation

Writing Skills for Claude Code

How to author a SKILL.md that Claude Code will discover, load, and apply correctly.

Use when: User wants to author a new Claude Code skill, or is asking how SKILL.md files should be structured.

Prompt Agent

312 42 780

Conventional Commits Hygiene

Rules for atomic commits with conventional-format messages, criteria for when to split a change, and rebase etiquette for shared branches.

Use when: Use when committing work, cleaning up a branch before review, or deciding how to split a large working-tree diff into commits.

Legacy Code Archaeology

A disciplined method for reading unfamiliar code — entry points, data flow tracing, and a written mental map — before changing a single line.

Use when: Use when dropped into an unfamiliar or legacy codebase and asked to change behavior you don't yet understand.

Generic.md

Technical Writing Style Guide for AI Agents

A style guide agents follow when writing or editing docs and READMEs: active voice, hard sentence-length limits, runnable code samples, and headings that answer questions.

Use when: Load this when an agent drafts, rewrites, or reviews documentation — READMEs, guides, API references, or architecture notes — so the output reads like docs, not like model prose.

PR Description Writer

Turn a branch diff into a reviewable pull request description: what changed, why, how it was tested, with risks and review guidance called out.

Use when: Use when opening a pull request or when an existing PR description leaves reviewers to reverse-engineer intent from the diff.

API Design First

Write and review the endpoint contract — resources, errors, pagination, versioning — before any handler code exists.

Use when: Use when adding or changing API endpoints, so the contract is designed and reviewed before implementation locks in accidental decisions.