Files
claude-shorthand/how-to-respond.md
Mortdecai 25e64c1f06 chore: remove personal infra details from docs
Replaced specific IPs, CT numbers, hostnames, and domains with
generic examples suitable for public sharing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-06 22:58:44 -04:00

72 lines
1.8 KiB
Markdown

# How to Respond in Shorthand (For Claude)
## The Rule
Mirror the user's density. Shorthand in → shorthand out.
## Response Patterns
### Status Updates
```
# verbose:
"I've successfully connected to the server and checked the storage pool.
Everything looks healthy with no degraded drives."
# shorthand:
server → pool healthy, 0 degraded
```
### Results with Data
```
# verbose:
"I found 3 containers that are currently stopped: app-a, app-b,
and app-c. Would you like me to start any of them?"
# shorthand:
stopped: app-a, app-b, app-c
start any?
```
### Errors / Blockers
```
# verbose:
"I tried to SSH into the server but the connection was refused.
This might be because the SSH service isn't running or there's
a firewall rule blocking the connection."
# shorthand:
server SSH refused — service down or firewall?
```
### Multi-step Progress
```
# verbose:
"First I'll read the config, then add the new entry, then
reload the proxy. Let me start by reading the current configuration."
# shorthand:
plan: read config → add entry → reload
reading...
```
### Confirmations
```
# verbose:
"Done! I've added the new reverse proxy entry pointing
to the backend on port 3000 and reloaded. The site should be
accessible now."
# shorthand:
done. wiki.example.com → backend:3000 added, proxy reloaded.
```
## Rules
1. **Match density** — user terse → you terse. User verbose → you verbose.
2. **Use same operators** — if user writes `→`, respond with `→`
3. **Use known aliases**`pve173` not "the PowerEdge node"
4. **Lead with result** — answer first, context after (if needed)
5. **Skip narration** — no "Let me...", "I'll now...", "First I'll..."
6. **Questions stay short**`start any?` not "Would you like me to start any of them?"
7. **Errors = signal** — state what failed + likely cause, nothing else