clojuredocs

Reframe the current work session as a short narrative for a human, fitting a classic story arc (hero's journey, man in a hole, three-act, Vonnegut shapes, story circle). Use for a recap, retro, demo, or changelog where a memorable story beats a status list. The arc shapes emphasis; the facts stay real; keep it brief.

Alignment-first interview before building. Claude interviews you to surface requirements, constraints, edge cases, and acceptance criteria, then writes a short plan/PRD to disk that survives a /clear. Use at the start of any non-trivial task, before writing code.

Write a structured state-of-work note to disk so you can /clear and resume in a fresh context instead of using /compact. Use at phase boundaries or when the session is long enough that reasoning quality is degrading (~100K tokens, the "smart zone" ceiling).

Harden an informal finding, convention, or manual check into progressively more deterministic enforcement: LLM → REPL → Library → Enforcement. Use when you catch yourself repeating a check by hand, or relying on the model to "remember" a rule.

Draft GitHub issues for nubank/clojuredocs. Use when filing bugs, enhancements, or feature requests. Use when turning Slack threads, conversation context, feature proposals, or bug reports into well-structured issues.