ClaudeHack

Claude Code / CLAUDE.md

7 hacks

  1. 1.
    Tell Claude to update CLAUDE.md after every mistake(arps18.github.io)

    When Claude repeats a project gotcha, end your prompt with an instruction to write a CLAUDE.md rule so it never happens again.

    0 points·12 hours ago·easy·discuss
  2. 2.
    Have a second Claude session review the plan before coding(arps18.github.io)

    Write the plan in one session, then open a fresh Claude with no context and ask it to review the plan like a staff engineer.

    0 points·12 hours ago·easy·discuss
  3. 3.
    Bootstrap with /init, then ruthlessly prune the draft(code.claude.com)

    Use /init to generate a starter CLAUDE.md, then delete anything inaccurate or obvious before committing.

    0 points·12 hours ago·easy·discuss
  4. 4.
    Load rules only when files match with .claude/rules(code.claude.com)

    Put domain-specific instructions in path-scoped `.claude/rules/` so they load only when Claude touches matching files.

    0 points·12 hours ago·medium·discuss
  5. 5.
    Keep CLAUDE.md under 200 lines so rules actually stick(code.claude.com)

    Trim project memory to under ~200 lines so Claude follows critical rules instead of drowning them in noise.

    0 points·12 hours ago·easy·discuss
  6. 6.
    Commit shared .claude/settings.json for team permissions(docs.anthropic.com)

    Check in project settings so every teammate gets the same allow/deny rules, hooks, and env defaults without redoing /permissions.

    0 points·12 hours ago·intermediate·discuss
  7. 7.
    Use CLAUDE.local.md for personal overrides you never commit(code.claude.com)

    Keep personal shortcuts and machine-specific notes in CLAUDE.local.md (gitignored) instead of polluting the shared CLAUDE.md.

    0 points·12 hours ago·easy·discuss