What problem does it solve?
Style guide for writing error messages, exception messages, and validation messages consistently across the codebase. Apply this skill whenever the user is writing, reviewing, or fixing error messages — even if they just say "fix the wording", "make these consistent", "review the error messages", or "what should this error say".
Core Features & Use Cases
- Describe the state of an error rather than giving instructions to the caller.
- Ensure tense consistency across missing, invalid, and active states, plus time-based conditions like expiry or reuse.
- Include the specific subject name when available, and preserve details when wrapping exceptions.
Quick Start
Rewrite error messages to describe what went wrong, name the subject, use the correct tense, and include the offending value when known.