Skip to content

Add CLAUDE.md self-correction + investigate-where-pointed rules #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
VideoGameTips wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add CLAUDE.md self-correction + investigate-where-pointed rules #2

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
be7bce5
Add CLAUDE.md guidance: investigate where pointed + self-log repeat m…
VideoGameTips May 30, 2026
6608c46
Merge remote-tracking branch 'origin/main' into docs/claude-md-self-c…
VideoGameTips Jun 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,8 @@ Multiplayer browser FPS. Three.js + Socket.IO + Express. Hosted on Railway, repo
- **Commit + push after essentially every change.** Detailed commit messages, end with `Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>`. Push to `main` (PR #1 already merged). Report briefly after.
- **Bias to action.** He often answers tersely ("y", "k", "do it", "go") or dismisses question prompts. Make the reasonable call and keep building rather than over-asking. Ask only when genuinely blocked or a decision is irreversible.
- Requests arrive as a stream of small features; he frequently **playtests and reports bugs** in casual language ("the enemy walked through the wall", "shuriken doesn't work"). Treat those as real bug reports — investigate, don't hand-wave.
- **If he points at a place, look THERE first.** When a report names a feature, system, button, or area ("mobile shooting", "the kill log", "bot AI", "the shop"), grep/read that exact code path before anything else. Start the investigation where he pointed — don't go exploring the whole codebase first.
- **Self-correct: after making the SAME mistake 3+ times, write it into this file.** If you catch yourself repeating an error (wrong cwd, off-by-one parallel array, stale build confusion, etc.) three or more times, immediately add a new entry to the "⚠️ Hard-won gotchas" section above so it stops happening. The gotchas list exists precisely because past mistakes got logged — keep feeding it.
- **New weapons: don't bother verifying they work in a live preview — Andy playtests those himself.** For a new/modified weapon, item, or skin, just `node --check` the files and confirm parallel-array alignment (gotcha #2) + client/server table mirrors (gotcha #4), then commit. (Still verify *bug fixes* and non-weapon behavior changes when practical.)
- Likes **balance**: P2W weapons should be *ridiculously expensive*, not cheap. Fragments/credits should require grind for top-tier items.
- Enjoys **humor + casual banter**; sometimes writes in Chinese/English mix. Match the energy but stay focused on shipping.
Expand Down