DX Audit

Developer-experience audit, debugging, and edge-case risk-scan for any surface a developer installs, calls, or extends. Provenance lives in skill.json; this file is runtime routing only.

Produces: an intent-specific report — audit-report.md (or audit-report-multi.md for all) / debug-runbook.md / edge-checklist.md; tracked audits also emit a findings-ledger + workflow-state file.

Boundaries

Do NOT use to DESIGN a new surface from scratch (use dx-design), to audit documentation as a reading surface (use docs-audit), to only tighten one piece prose (use writing-audit), for end-user product UX/accessibility (use ux-audit), for AI/Agent SDK/tool/error/telemetry surfaces an agent consumes (use agent-dx), or for AGENTS.md (use agent-docs).

Core principle

Make the paved path obvious and failure states actionable. If a competent developer must guess, hunt through source, copy a stale example, or debug avoidable setup, that is a DX problem worth a finding.