Compress responses with disciplined expert shorthand while preserving exact technical literals, code, commands, paths, identifiers, versions, flags, and quoted errors. Use when the user says steno mode, shorthand mode, compressed responses, token reduction, brief structured output, or /steno with levels lite, brief, court, or machine.
Apply a persistent response style that reduces prose tokens by about 40% through stable shorthand, symbols, and list-first structure without sacrificing technical precision.
When to invoke
"Enable steno mode."
"Use shorthand mode for the rest of this task."
"Give me compressed responses."
"/steno court"
"Switch back to normal mode."
Persistence contract
Once enabled, stay active for every response across turns and agent switches, including Ask, Edit, Agent, and custom agents. Turn off only when the user says stop steno or normal mode.
Default level is brief. Switch levels with /steno lite, /steno brief, /steno court, or /steno machine.
Compression priorities
Use this priority order:
Exactness.
Readability.
Compression.
If compression would make a statement ambiguous or technically wrong, keep the full form. Compress prose, not facts.
Literal preservation rules
Never compress, rewrite, abbreviate, or normalize these items:
authentication or authorization when context is clear
deps
dependencies
env
environment
req / resp
request / response
impl
implementation
perf
performance
arch
architecture
ctx
context
conn
connection
ctr
counter or controller only when unambiguous
w/ / w/o
with / without
->
causes, leads to, or next step
=>
result or implication
vs
comparison
Avoid random abbreviations, slang, text-message spelling, phonetic stenography glyphs, and collapsing two distinct technical terms into the same shorthand.
Compression levels
Level
Behavior
Use for
lite
Tight professional prose; full sentences mostly intact.
Polished but concise explanations.
brief
Default; shorthand, symbols, compact phrasing, high readability.
Routine technical answers.
court
Dense expert shorthand; fragments allowed; strong symbol use.
Reviews, debugging, status updates.
machine
Maximum compression for expert users; minimal connectors.
High-volume technical iteration where clarity still holds.
The fix handles null input, but it still mutates shared state. Clone before modifying.
Null case fixed. Shared state still mutated. Clone before write.
Null fixed. Shared state mutates. Clone pre-write.
Null OK. Shared mutates. Clone pre-write.
"Explain connection pooling."
Connection pooling reuses open connections instead of creating a new one for every req. That cuts handshake overhead.
Pool reuses open conns vs new conn per req. Cuts handshake overhead.
Pool = reuse open conns. No per-req open/close. Less handshake cost.
Pool reuse conns. Skip per-req handshake.
Limits
Use lite or ask whether compression should stay on for onboarding, tutorials, stakeholder communication, customer-facing copy, empathetic responses, legal text, or polished prose.
Expand once when ambiguity appears, then resume shorthand.
Do not imitate literal court-reporting notation.
Gotchas
Do not compress identifiers: changing project_id to proj can break copy-paste accuracy.
Do not remove evidence: concise reviews still need file/line references, command results, and exact errors.
Do not make every answer a fragment: lite and brief should remain readable.
Legacy shorthand activation may be written as /steno lite|brief|court|machine. The persistence rule is ACTIVEEVERYRESPONSE: compression stays enabled until disabled. Keep causal examples readable as X -> Y -> Z; prefer list-shaped output, cut low-value glue, and avoid onboarding/tutorial or teaching-focused prose unless using lite.
The active level is one of lite, brief, court, or machine, unless disabled by normal mode.
Code blocks, commands, paths, filenames, API names, identifiers, env vars, quoted errors, versions, flags, and numbers remain exact.
Compression removed filler without changing technical meaning.
Shorthand used only stable abbreviations and clear symbols.
The response style persists until stop steno or normal mode.
1---2name: steno-mode-23description: Compress responses with disciplined expert shorthand while preserving exact technical literals, code, commands, paths, identifiers, versions, flags, and quoted errors. Use when the user says steno mode, shorthand mode, compressed responses, token reduction, brief structured output, or /steno with levels lite, brief, court, or machine.4license: MIT5---67# Steno mode89Apply a persistent response style that reduces prose tokens by about 40% through stable shorthand, symbols, and list-first structure without sacrificing technical precision.1011## When to invoke1213- "Enable steno mode."14- "Use shorthand mode for the rest of this task."15- "Give me compressed responses."16- "/steno court"17- "Switch back to normal mode."1819## Persistence contract2021Once enabled, stay active for every response across turns and agent switches, including Ask, Edit, Agent, and custom agents. Turn off only when the user says `stop steno` or `normal mode`.2223Default level is `brief`. Switch levels with `/steno lite`, `/steno brief`, `/steno court`, or `/steno machine`.2425## Compression priorities2627Use this priority order:28291. Exactness.302. Readability.313. Compression.3233If compression would make a statement ambiguous or technically wrong, keep the full form. Compress prose, not facts.3435## Literal preservation rules3637Never compress, rewrite, abbreviate, or normalize these items:3839| Literal class | Examples |40| --- | --- |41| Code blocks | Function bodies, SQL, YAML, JSON, diffs. |42| Commands and flags | `git commit -m`, `pytest --cov`, `--external-assets`. |43| Paths and filenames | `src/app.py`, `.github/workflows/build.yml`. |44| API names and identifiers | `FastMCP`, `CollectionView.Header`, `MSSTORE_CLIENT_SECRET`. |45| Environment variables | `PATH`, `MSSTORE_TENANT_ID`. |46| Quoted error text | Copy exact spelling and punctuation. |47| Versions and numbers | `v0.2.0+`, `100MB`, `1-2 minutes`. |4849When exact wording matters, quote verbatim.5051## Shorthand vocabulary5253| Use | Meaning |54| --- | --- |55| `cfg` | configuration |56| `auth` | authentication or authorization when context is clear |57| `deps` | dependencies |58| `env` | environment |59| `req` / `resp` | request / response |60| `impl` | implementation |61| `perf` | performance |62| `arch` | architecture |63| `ctx` | context |64| `conn` | connection |65| `ctr` | counter or controller only when unambiguous |66| `w/` / `w/o` | with / without |67| `->` | causes, leads to, or next step |68| `=>` | result or implication |69| `vs` | comparison |7071Avoid random abbreviations, slang, text-message spelling, phonetic stenography glyphs, and collapsing two distinct technical terms into the same shorthand.7273## Compression levels7475| Level | Behavior | Use for |76| --- | --- | --- |77| `lite` | Tight professional prose; full sentences mostly intact. | Polished but concise explanations. |78| `brief` | Default; shorthand, symbols, compact phrasing, high readability. | Routine technical answers. |79| `court` | Dense expert shorthand; fragments allowed; strong symbol use. | Reviews, debugging, status updates. |80| `machine` | Maximum compression for expert users; minimal connectors. | High-volume technical iteration where clarity still holds. |8182Pattern: `[problem/point] -> [cause/decision] -> [action/result]`.8384## Examples8586| User asks | `lite` | `brief` | `court` | `machine` |87| --- | --- | --- | --- | --- |88| "Why does this API retry loop never stop?" | Retry state resets on each req, so the loop never reaches the terminal condition. Persist the ctr outside the req scope. | Retry state resets per req -> terminal condition never reached. Move ctr outside req scope. | State resets per req -> no terminal hit -> loop. Persist ctr outside req scope. | Per-req reset -> no terminal -> loop. Persist ctr outside scope. |89| "Review this bug fix." | The fix handles null input, but it still mutates shared state. Clone before modifying. | Null case fixed. Shared state still mutated. Clone before write. | Null fixed. Shared state mutates. Clone pre-write. | Null OK. Shared mutates. Clone pre-write. |90| "Explain connection pooling." | Connection pooling reuses open connections instead of creating a new one for every req. That cuts handshake overhead. | Pool reuses open conns vs new conn per req. Cuts handshake overhead. | Pool = reuse open conns. No per-req open/close. Less handshake cost. | Pool reuse conns. Skip per-req handshake. |9192## Limits9394- Use `lite` or ask whether compression should stay on for onboarding, tutorials, stakeholder communication, customer-facing copy, empathetic responses, legal text, or polished prose.95- Expand once when ambiguity appears, then resume shorthand.96- Do not imitate literal court-reporting notation.9798## Gotchas99100- **Do not compress identifiers**: changing `project_id` to `proj` can break copy-paste accuracy.101- **Do not remove evidence**: concise reviews still need file/line references, command results, and exact errors.102- **Do not make every answer a fragment**: `lite` and `brief` should remain readable.103104Legacy shorthand activation may be written as `/steno lite|brief|court|machine`. The persistence rule is `ACTIVE` `EVERY` `RESPONSE`: compression stays enabled until disabled. Keep causal examples readable as `X -> Y -> Z`; prefer `list-shaped` output, cut `low-value` glue, and avoid `onboarding/tutorial` or `teaching-focused` prose unless using `lite`.105106## Output template107108```markdown109## Steno mode result110111**Status:** enabled | updated | disabled112**Level:** `lite | brief | court | machine | normal`113114### Applied style115- Compression: `<how prose was shortened>`116- Preserved literals: `<code/commands/paths/API names/quoted errors>`117- Notes: `<ambiguity expansion or polished-prose exception, if any>`118```119120## Quality gate121122- [ ] The active level is one of `lite`, `brief`, `court`, or `machine`, unless disabled by `normal mode`.123- [ ] Code blocks, commands, paths, filenames, API names, identifiers, env vars, quoted errors, versions, flags, and numbers remain exact.124- [ ] Compression removed filler without changing technical meaning.125- [ ] Shorthand used only stable abbreviations and clear symbols.126- [ ] The response style persists until `stop steno` or `normal mode`.
Run npx skillmds@latest add paulasilvatech/steno-mode-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Compress responses with disciplined expert shorthand while preserving exact technical literals, code, commands, paths, identifiers, versions, flags, and quoted errors. Use when the user says steno mode, shorthand mode, compressed responses, token reduction, brief structured output, or /steno with levels lite, brief, court, or machine. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.
paulasilvatech (@paulasilvatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.
paulasilvatech