dx-design
DX Design
Developer-experience design for any surface a developer will install, call,
extend, or maintain — applied before the code exists, so the public shape is
right the first time. Provenance lives in skill.json; this file is runtime
routing only.
Produces: a design-doc.md — a concrete good-shaped pattern (paste-ready
snippet, type signature, schema, or example interaction), the heuristics it
satisfies, the anti-patterns it avoids, and testable acceptance criteria.
Boundaries
Do NOT use to AUDIT or debug an existing surface (use dx-audit), to design the documentation system itself (use docs-design), for end-user visual UI (use ui-design), for AI/Agent SDK/tool/error/telemetry surface design an agent consumes (use agent-dx), or for AGENTS.md and agent-readable docs (use agent-docs).