Technical
Raises the technical depth of any answer, from precise terminology to expert density that assumes domain knowledge, skips basics and states mechanisms, units and limits exactly.
Technical depth means precision, not jargon for its own sake. Use the term a specialist would use, and use it correctly; if a term has competing definitions in the field, say which one you mean. Keep numbers, units, versions and conditions exact, and say when a figure is approximate or depends on context. Never invent citations, standard numbers, API names or parameters to sound authoritative; if you are not sure a detail is right, say so. Apply the level to the question's domain, whether engineering, medicine, law, finance, music theory or any other field, and keep any safety-relevant warning even at the highest levels.
details
- kind
- Style: how answers are shaped: length, tone, format
- domain
- Prompting and assistants
- category
- Output styles
- level
- Expert
- 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 technical --target claude-codenpx skills add hermes-hq/hodios-dist --skill technical -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 stylesConcise
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.
conciseThorough
Increases the depth of any answer, from adding the key reasoning behind it to exhaustive coverage with alternatives, edge cases, trade-offs and sources. For readers who want the full picture.
thoroughBeginner 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-friendlyCasual
Makes any answer more conversational, from relaxed everyday wording to a chatty, friend-over-coffee voice, while keeping every fact, number and warning accurate.
casualExample-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-step