Error ux
Portable agent skills. Point Kit at a project, install a pack, wire Claude Code, Grok Build, and Codex.
npx -y skills add Zwin-ux/kit --skill error-uxAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Improve user-facing error messages so failures are actionable.
SKILL.md
0.7 KB, as published. Nobody here has run it
Instructions
- List the failure modes a user can hit (CLI, API, UI).
- For each important path, ensure errors say: what failed, why, and what to do next.
- Strip stack traces and internal jargon from end-user surfaces; keep detail in logs.
- Use stable error codes or short names when scripts depend on output.
- Prefer one clear message over nested rethrows that bury the root cause.
- Add or update tests for the friendliest failure cases.
- Report before/after examples for the worst messages.