user-facing-error-messages
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Audit and rewrite user-facing error messages so users can self-serve instead of emailing support. Use when auditing error messages across an app, improving or rewriting error wording, reviewing toasts, alerts, flash messages, form validation copy, or empty/failure states, or when a message feels opaque, blame-y, or ends in "contact support". Covers the four-part rubric (what / why / next / escape), an inventory-and-triage audit workflow, rewrite templates, and security-safe disclosure rules. Do NOT use for exception architecture, typed errors, or developer-facing logging (use error-handling skill); for the security rules around what errors may safely disclose in auth/crypto paths (use security skill); or for the visual styling of alerts, toasts, and banners (use frontend-aesthetics skill).
In this repository36 other files it gives its agents.
- address-feedbackSkill
- apple-to-android-port-specSkill
- architectural-decisionsSkill
- await-claude-reviewSkill
- backlog-groomingSkill
- bug-squashing-methodologySkill
- ci-debuggingSkill
- collect-skillsSkill
- comprehensive-pr-reviewSkill
- concurrencySkill
- continue-epicSkill
- cve-remediationSkill
- de-slopifySkill
- discord-ralph-recapSkill
- distribute-skillsSkill
- documentationSkill
- error-handlingSkill
- file-naming-conventionsSkill
- frontend-aestheticsSkill
- git-workflowSkill
- max-quality-no-shortcutsSkill
- mutation-testingSkill
- preflightSkill
- prompt-engineeringSkill
- quick-testSkill
- review-diffSkill
- scan-issue-writerSkill
- securitySkill
- skill-craftSkill
- spec-decompositionSkill
- statusSkill
- stay-greenSkill
- testingSkill
- tracer-codeSkill
- triage-and-planSkill
- vibeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.