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.

Core principle

Design the paved path before it sets. The cheapest time to fix a DX problem is before the contract ships — every observable behavior of an interface eventually gets depended on, so name the good-shaped pattern concretely rather than describing principles abstractly.

Activation