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

Voice + consistency: vary stock formulas, vendor-balance orient.py, unify loop (#48,#49,#51) (#68)

Browse Source 
Co-authored-by: claude <claude@jpaul.io>
Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #68.
This commit is contained in:
Claude (agent)
2026-06-22 17:45:33 -04:00
committed by Claude (agent)
parent f7011d4211
commit f743bb671b
12 changed files with 35 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/23-working-with-existing-codebases/README.md
+4 -4
View File
@@ -144,10 +144,10 @@ in unfamiliar code," they encode *exactly* what careful means, as steps the AI f
## The AI angle
A generic "onboarding to a legacy codebase" guide would tell a human to read the README and ask a
senior dev. What's specific here is that **the AI is both the thing reading the codebase and the
thing most likely to confidently misread it** — and the bigger the repo, the wider that gap between
"sounds authoritative" and "is correct."
Onboard a human to a legacy codebase and the advice is familiar: read the README, ask a senior dev.
What's specific here is that **the AI is both the thing reading the codebase and the thing most
likely to confidently misread it** — and the bigger the repo, the wider that gap between "sounds
authoritative" and "is correct."
So the AI-specific discipline is verification, not exploration. The model is genuinely excellent at
the grunt work of orientation — reading a hundred files, summarizing structure, tracing a call path —
modules/23-working-with-existing-codebases/lab/orient.py
+6
View File
@@ -49,8 +49,14 @@ SIGNALS: dict[str, str] = {
"README.md": "Has a README — read it first",
"CONTRIBUTING.md": "Has contributor guidance — read before changing",
"ARCHITECTURE.md": "Has an architecture doc — rare and valuable",
# Committed AI-instruction files. Name the real ones across vendors — singling out one
# would both miss files and cut against the vendor-neutral point (Module 5).
"AGENTS.md": "Has a committed AI instructions file (Module 5)",
"CLAUDE.md": "Has a committed AI instructions file (Module 5)",
"GEMINI.md": "Has a committed AI instructions file (Module 5)",
".cursorrules": "Has a committed AI instructions file (Module 5)",
".cursor/rules": "Has a committed AI instructions file (Module 5)",
".github/copilot-instructions.md": "Has a committed AI instructions file (Module 5)",
}
# Common test-runner hints keyed off a present signal file.