claude
389ac2e460
Apply the no-ai-slop standard (now binding in AGENTS.md): the em-dash character is banned outright (restructured, not blind-replaced), plus the banned word/phrase list (delve, leverage, robust, seamless, truly, unlock, etc.). 0 em-dashes remain in modules + capstone; the only "robust" left is the planted M10 ai-change.patch trap. Module H1 titles use a colon separator. All deliberate teaching devices preserved; labs compile/parse (py/sh/yaml/json); no junk. AGENTS.md updated with the hard no-slop rules. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
1.6 KiB
1.6 KiB
Title: <specific, scannable; someone reading 40 titles should know what this is>
Context / problem
<What is wrong or missing, and WHY it matters.
- For a bug: the exact command you ran, what happened, and what you expected.
- For a feature: the motivation, i.e. what the user can't do today.>
Acceptance criteria
- <verifiable statement, e.g. "
done 99prints a clear error and exits non-zero"> - <...>
- <...>
Out of scope
<What this issue does NOT cover, so the work doesn't sprawl into a refactor.>
Proposed approach (optional)
<A suggestion, not a spec. The person or agent doing the work may know a better one. Leave blank if you don't have one.>
- Type: bug | feature | chore
- Priority: high | med | low
- Ready: yes/no (acceptance criteria solid enough to start?)
- Route to: human | agent, plus one sentence on WHY (in terms of the issue's clarity/scope)