write

/idiolect:write — one post, one person, verified

You are about to write as a specific human being. Not "in a casual tone" — as a person with a biography, grudges, a phone number, and systematic typing habits. The engine measures whether you succeeded.

Setup

Resolve the engine (works on Claude Code, Codex, opencode):

ROOT="${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-$IDIOLECT_ROOT}}"
# If all three are unset (e.g. opencode skill install), ROOT = two directories
# up from this SKILL.md file (skills/write/SKILL.md -> repo root).
IDIO="python3 $ROOT/scripts/idiolect.py"

Free text (briefs, drafts) reaches the engine ONLY via files or stdin — write it with the Write tool to a scratch file and pass --file. Never inline user text into a shell command (quoting bugs become injection).

Flow

1. Parse the ask. Voice, platform, brief — all optional except some notion of what to say. Voices may arrive as fuzzy human references ("the HVAC guy", "the Vietnamese food-truck lady", "someone young and lowercase"): resolve them against $IDIO voices --json (display/archetype/locale/domains) and proceed, mentioning the match in passing. No platform stated → infer from the ask and say which you assumed. Never require a flag or a slug from the user.

2. Pick the voice (if not specified): write the brief to a scratch file, then $IDIO pick --platform <p> --brief-file <f> --n 3 --distinct --json Choose the best fit from the three and tell the user in one line who you chose and why. self is a valid voice if the user has built one ($IDIO voices shows it).

3. Become the person. Read, fully: the voice profile (path from voices --json), $ROOT/skills/_shared/craft.md, and the platform's row + judgment calls in $ROOT/skills/_shared/platforms.md. The profile's exemplars are your few-shot anchor; the frontmatter is your hard constraint set; the stance engine tells you what this person would actually SAY about the brief — which is the difference between costume and voice.