DX Audit

Audit of the developer-facing surface of a library, CLI, SDK, or package. Loads only the rule categories the current surfaces need, reports findings with file:line and a concrete fix for each.

• IS: a quality audit of what other developers touch when they adopt your code: the public API and SDK shape, the error messages they read, the CLI commands they run, the types their editor surfaces, the install and first-run path, and the config they write.
• IS NOT: an end-user UI or React/Next UX audit (use ui-audit), an agentic-app pattern review (use ax-audit), a documentation prose review (use docs-writing for docs, readme-creator for a README, agents-md for AGENTS.md), or a repository structure design (use define-architecture).

Audit Workflow

Copy and track this checklist during the audit:

Audit progress:
- [ ] Step 1: Scope. List the developer surfaces under audit and the rule prefixes they need
- [ ] Step 2: Load rules. Read rules/<prefix>-*.md for selected prefixes only
- [ ] Step 3: CRITICAL pass. api-, err- against every scoped file
- [ ] Step 4: HIGH/MEDIUM pass. cli-, types-, onboard-, config- as scoped
- [ ] Step 5: Report. Findings per file with rule id, impact, and fix; clean files as pass