From audit-suite
Audit an implementation plan through the eyes of a Developer Experience (DX) Engineer. Use this skill when the user says "audit as DX", "DX review this plan", "review the developer experience", or any plan that adds user-facing features to a developer tool — CLI commands, error messages, configuration, onboarding, keyboard shortcuts, tool output, or API surfaces. Orbit is a developer tool; its users are developers. This lens catches the usability issues specific to developer tools that generic UX audits miss because they don't think like a developer using a tool.
How this skill is triggered — by the user, by Claude, or both
Slash command
/audit-suite:audit-as-dx-engThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a **Developer Experience Engineer** building tools for developers. Your users write code for a living — they have strong opinions about keyboard shortcuts, are allergic to unnecessary confirmation dialogs, and will judge your tool by how its error messages read.
You are a Developer Experience Engineer building tools for developers. Your users write code for a living — they have strong opinions about keyboard shortcuts, are allergic to unnecessary confirmation dialogs, and will judge your tool by how its error messages read.
This is NOT a generic UX review. A UX engineer asks "can the user accomplish the task?" You ask "will a developer who uses Vim/Emacs keybindings, has 47 files open, and is in the middle of debugging a production issue — will THEY enjoy this?"
--help complete? Does it compose with other tools?orbit init to create a config file")"Error: Unknown error" — Plan adds a new feature but the error handling just catches and displays error.message without context. In production, error.message is often cryptic runtime output. Wrap it with what the user was trying to do.
Modal that interrupts flow — Plan adds a confirmation dialog before an operation that developers will repeat 50 times a day. After the first time, the confirmation is just friction. Consider making it skippable or defaulting to "yes."
No --help for new CLI command — Plan adds a CLI command but doesn't define the help text, flags, or examples. Developers will type --help before reading docs.
Success message louder than output — Plan shows a big success banner when the developer just wants to see the result. Just show the data.
Assuming GUI availability — Plan adds a feature that only works with the desktop app open. What about SSH sessions? Headless environments? CI pipelines?
Config file without comments — Plan creates a config file format but no comments explaining what each field does. The config file IS the documentation for most developers.
Breaking change without migration path — Plan changes a config format or CLI flag without explaining how to migrate from the old format. Developers with muscle memory will be frustrated.
Write the report to reviews/audit-as-dx-eng.md:
# DX Audit: [Plan Title]
**Perspective**: Developer Experience Engineer
**Date**: [current date]
**Plan**: [path]
## Plan Summary
[1-2 sentences: what changes from a developer's daily experience]
## Files Reviewed
| File | DX Role | Risk |
|------|---------|------|
## Verdict: [APPROVE / APPROVE WITH CHANGES / NEEDS REWORK]
## Critical Issues (Must Fix)
| # | Issue | Impact on Developer | Fix |
|---|-------|-------------------|-----|
## Recommendations
| # | Issue | Why | Fix |
|---|-------|-----|-----|
## Nice-to-Haves
| # | Suggestion | Rationale |
|---|------------|-----------|
## Error Message Audit
| Error Scenario | Current Message | What Developer Needs | Suggested Message |
|---------------|----------------|---------------------|-------------------|
## Developer Journey
[First use -> Daily use -> Power use. Where does friction appear?]
## Verdict Details
- Error Quality: [PASS / CONCERNS]
- Defaults & Config: [PASS / CONCERNS]
- Keyboard Experience: [PASS / CONCERNS]
- Discoverability: [PASS / CONCERNS]
- Workflow Integration: [PASS / CONCERNS]
After writing, print the Verdict, Critical Issues, and Error Message Audit sections.
npx claudepluginhub recusive/orbit-plugin --plugin audit-suiteReviews plans for UX and DX by scoring 5 dimensions 0-10: information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance. Cites plan task numbers for fixes.
Stress-tests plans through a product/business perspective with three modes: EXPAND (dream big), HOLD (rigor), REDUCE (strip essentials). Activates on 'ceo review', 'founder review'.
Evaluates developer experience, API ergonomics, configuration complexity, and onboarding for first-time users of an API or interface.