claude-code-lab
CLAUDE.md0 starsChanged 2 months agoMITView on GitHub
This is the hands-on lab repository for the CodeChup Claude Code Academy (cc.codechup.com). It is a tiny TypeScript task-tracker CLI (labtrack) plus a matching HTTP API, intentionally seeded with a handful of small, real bugs — see BUGS.md. This .claude/ is deliberately minimal: just enough to make "run Claude Code against a real small project" realistic for lessons that use this repo as a demo target. It is not this project's own dogfooded setup (see claude-code-training's .claude/ for that). -…
In this repository3 other files it gives its agents.
- commit-msgSkill
- new-componentSkill
- review-securitySkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Every bug in BUGS.md ships with a failing test at its -start tag and a passing one at its -solution tag.
- Very specific: line 34
Never log a secret's value, even a placeholder one (BUGS.md B7) — log that it's configured, and where it came from, not what it is.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md — claude-code-lab
This is the hands-on lab repository for the CodeChup Claude Code Academy
(cc.codechup.com). It is a tiny TypeScript task-tracker CLI (labtrack) plus a matching
HTTP API, intentionally seeded with a handful of small, real bugs — see BUGS.md.
This .claude/ is deliberately minimal: just enough to make "run Claude Code against a
real small project" realistic for lessons that use this repo as a demo target. It is not
this project's own dogfooded setup (see claude-code-training's .claude/ for that).
Commands
npm ci # install
npm test # vitest
npm run typecheck # tsc --noEmit
npm run lint # eslint + prettier --check
npm run format # prettier --writeConventions
- Core logic lives in
src/store.ts. The CLI (src/cli.ts) and the API (src/api/server.ts) are thin wrappers around it — fix a bug at the source, not in both wrappers. - Every bug in
BUGS.mdships with a failing test at its-starttag and a passing one at its-solutiontag. Don't "fix" a bug by loosening or deleting its test. - This repo is public and its 98
lesson/*tags are cited by name from published lessons: never delete or move a lesson tag, and never commit a private hostname, path, or a personal email as the commit author, and never aClaude-Session:trailer in a commit message. See.claude/rules/public-hygiene.mdand README.md "Tag contract";npm run hygiene,node scripts/check-public-hygiene.mjs --commits origin/main..HEADand--identityare the checks. - Never log a secret's value, even a placeholder one (
BUGS.mdB7) — log that it's configured, and where it came from, not what it is..gitleaks.tomldocuments this repo's secret-scanning baseline (gitleaks detect --config .gitleaks.toml) — a scanner is a backstop for that habit, not a substitute for it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

