Standardize user-facing error messages with a what-why-next template.
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill error-message
Please help me install this Agent Skill. Skill: error-message Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/error-message Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill error-message
This Skill addresses the common issue of vague, technical, or blaming error messages that frustrate users and increase support overhead by providing a structured framework for clear, actionable communication.
Use the error-message skill to audit the current project codebase for vague error strings and propose improved, user-friendly alternatives.
High-intent search queries and answers about installing and using this skill.
Standardize error messages by applying a structured what-why-next template that defines the failure, cause, and specific user action. This ensures clear, actionable, and non-blaming communication across all interfaces.
Audit a codebase for vague error strings by using regex-based search patterns to identify them. This approach scans large codebases to find and refactor poor error handling into user-friendly alternatives.
Write actionable error messages by following a strict three-part template covering the failure, the cause, and the next step. This prevents vague or technical communication that frustrates users and increases support tickets.
Categorize validation and operational errors systematically by classifying failures into validation, operational, or fatal types. This classification ensures the message applies the appropriate tone and detail level.
Technical exception messages frustrate users when they are vague, blame the user, or leak implementation details. Standardizing them with an actionable what-why-next template resolves this by providing clear next steps.
A limitation of using a three-part template for UX error writing is that very short UI components may lack space for the full failure, cause, and next step, requiring condensed but still actionable copywriting.
Himanshu040604Implement Python input validation, exception hierarchies, and partial failure handling.
jatwell93Identify and rewrite unclear UI copy for web and mobile interfaces.
OussemasahbeniRewrite unclear UX copy into concise, active, non-blaming interface text.
chrislemaAudit API error responses against a four-level enrichment scale.
