Casual
Makes any answer more conversational, from relaxed everyday wording to a chatty, friend-over-coffee voice, while keeping every fact, number and warning accurate.
Casual changes the voice, never the accuracy. Keep every fact, number, step and safety warning exactly right; a relaxed tone is no excuse for vagueness. Do not use slang the reader may not understand, profanity, emoji or memes unless the user does first, and do not pretend to have personal experiences. Read the room: for serious or sensitive topics (health worries, grief, money trouble, legal problems) stay at the lower levels and keep it kind rather than jokey. Code, commands and quoted text stay exact.
details
- kind
- Style: how answers are shaped: length, tone, format
- domain
- Prompting and assistants
- category
- Output styles
- level
- Beginner
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install casual --target claude-codenpx skills add hermes-hq/hodios-dist --skill casual -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-prompting@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Output stylesPlain language
Lowers the reading effort of any answer, from swapping jargon for everyday words to a grade 6 reading level, keeping every fact accurate. Use for the general public or second-language readers.
plainConcise
Shortens answers by leading with the result and cutting preamble, recaps and filler, from light trimming to bare answers. Use when you want less reading and the same substance.
conciseBeginner friendly
Adapts answers for newcomers by defining jargon, explaining why each step matters and avoiding assumed knowledge, from light glossing to full guidance. Use when the reader is new to the topic.
beginner-friendlyExample-led
Leads with concrete examples, from one illustrative case after the explanation to an example before every rule, so readers see the idea in action before the abstraction.
example-ledStep by step
Structures answers as ordered, numbered steps the reader can follow and check, from a short numbered list to detailed steps with expected results. Use for procedures, setups and how-to answers.
step-by-stepVisual
Shapes answers visually, from tables where they help to diagrams, timelines and structured layouts throughout, so relationships and comparisons are seen rather than read.
visual