CONTEXT JAMMING 01 / 09
Ten Slash
Commands
that earn their keep.
/
Your command library is your operational doctrine.
02 / The Shift

Commands are skills now.

LEGACY
.claude/
└─ commands/
   ├─ dispatch.md
   ├─ ship.md
   └─ ...
→
CANONICAL
.claude/
└─ skills/
   └─ dispatch/
      SKILL.md
Claude Code v2.1.101 merged custom commands into the skills system on April 11, 2026.
.claude/commands/ still works. .claude/skills/ is where the system actually lives.
03 / The Seed

/dispatch

---
name: dispatch
description: Convert a research artifact
  into a Lewis-style longform draft
argument-hint: [research-file] [angle]
allowed-tools: Read Write
--- Read $1 and produce a longform piece on $2.
lead with a scene
bury the thesis at the 60% mark
end on a turn that re-frames the opener
n.b. Anthropic ships a feature called Dispatch in Cowork — phone messages a task, desktop spawns a session. This isn't that. Same verb, different namespace. .claude/skills/ is yours, not theirs.
Every dispatch comes out structurally consistent because the prompt is structurally consistent.
04 / The Ops Belt

/ship & /redteam

/ship
$ git status --short
M  skills/dispatch.md
M  skills/ship.md
A  skills/jam.md
feat(skills): add /jam stress-test command
/redteam
FORK
› reviewing artifact...
⚠ unsupported claim L24
⚠ scrivener err L41
⚠ weak inference L67
disable-model-invocation: true — side effects need explicit triggers.
A red-team running in your main context inherits your assumptions. A forked agent reads cold.
05 / Continuity

/handoff & /skill

SKILL.md
${CLAUDE_SESSION_ID} — a built-in substitution that turns handoffs/ into a session log without you ever writing one on purpose.
Once you've solved a problem twice by hand, the third solve should be a skill.
06 / Publishing

/9x16, /errata, /portal

longform
→
{ }
json
→
9 × 16
7–9 panels per longform draft. Metadata stays separate from payload — JSON survives the curly brace.
Skills that conflate payload and metadata produce JSON files that quietly become unparseable.
07 / The Pivot

/lineage
doctrine, made executable.

PhD
A Theory of Architectural Determinism
Dept. of Doctoral Priors
1998
load-bearing claim
Hassabis SCT → DeepMind world-models. Kaplan AdS/CFT → Constitutional AI.
The command isn't illustrating the doctrine. It's instantiating it.
08 / The Method

/jam

historical
technical
sociological
All load-bearing claims survive contact with three counter-frames.
Three counter-frames from disjoint domains. No bothsidesing. Pick a verdict.
If a claim can't survive /jam, it shouldn't ship.
09 / The Reveal

What you compress reveals what you do.

OPERATING
DOCTRINE
VERSION CONTROLLED
.claude/skills/
  • dispatch/
  • ship/
  • redteam/
  • handoff/
  • skill/
  • 9x16/
  • errata/
  • portal/
  • lineage/
  • jam/
If someone audited your .claude/skills/ directory next week, what would they conclude you actually do?