justin/ai-workflow-course
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

style(no-slop): remove every em-dash + banned words across all modules + capstone

Browse Source 
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
This commit is contained in:
Claude (agent)
2026-06-22 23:21:09 -04:00
parent 513d7e7ac8
commit 389ac2e460
99 changed files with 1324 additions and 1315 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/09-issues-and-the-task-layer/lab/issue-template.md
+5 -5
View File
@@ -1,5 +1,5 @@
<!--
Well-formed issue skeleton — Module 9 of "The Workflow".
Well-formed issue skeleton for Module 9 of "The Workflow".
Copy this for each issue you draft. Fill every section. Write it for a STRANGER: a teammate you've
never met, future-you who's forgotten, or an agent with no memory. Delete these comments as you go.
@@ -9,17 +9,17 @@
below is what matters and ports anywhere.
-->
# Title: <specific, scannable — someone reading 40 titles should know what this is>
# 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 — what the user can't do today.>
- For a feature: the motivation, i.e. what the user can't do today.>
## Acceptance criteria
<The checklist that defines DONE. Concrete and verifiable. This is the most important section —
<The checklist that defines DONE. Concrete and verifiable. This is the most important section:
it is the definition of done for a human AND the spec for an agent.>
- [ ] <verifiable statement, e.g. "`done 99` prints a clear error and exits non-zero">
@@ -41,4 +41,4 @@
- **Type:** bug | feature | chore
- **Priority:** high | med | low
- **Ready:** yes/no (acceptance criteria solid enough to start?)
- **Route to:** human | agent — and one sentence on WHY (in terms of the issue's clarity/scope)
- **Route to:** human | agent, plus one sentence on WHY (in terms of the issue's clarity/scope)