Sunday, April 5, 2026
Daily picks
15
articles scored
#1 GOLDGuideReddit r/ClaudeAI
I gave Claude Code a 285-line operating manual and 5 lifecycle hooks inside my Obsidian vault. After a month, it basically runs my work documentation for me.
- You can wire up Claude Code's session hooks (SessionStart, UserPromptSubmit, PostToolUse, PreCompact, Stop) in `.claude/settings.json` to fully automate work documentation in an Obsidian vault
- SessionStart injects your active projects, recent git changes, and open tasks so Claude already knows your context — no more "let me catch you up" at the start of every session
- UserPromptSubmit classifies your messages before Claude responds: say "just had a 1:1 with Sarah, she wants error monitoring before release" and it automatically creates the 1:1 note, updates Sarah's person file, logs the decision, and adds the win to your brag doc
- PostToolUse validates every .md Claude writes (frontmatter, wikilinks, correct folder) before mistakes compound; Stop auto-archives completed projects and checks for orphan notes
- The 285-line CLAUDE.md is the keystone — consistent note schema is what makes synthesis work, not clever prompting
#2 SILVERTutorialReddit r/ClaudeAI
I got Claude Code to stop burning 40K tokens by just figuring out my codebase
- Most Claude Code sessions waste 25K–66K tokens just re-exploring your codebase at the start of every conversation; codesight fixes this in one command
- Run `npx codesight scan` and it writes compact context files into `.codesight/` — architecture overview, all API routes, DB schema, UI components, env vars, and an import graph with "blast radius" analysis
- Add one line to CLAUDE.md pointing Claude at `.codesight/CODESIGHT.md` and future sessions start from a pre-computed map instead of rediscovering everything (~12x fewer orientation tokens on real production codebases)
#3 BRONZEGuideReddit r/ClaudeCode
Senior engineer best practice for scaling yourself with Claude Code
- Git worktrees let you run 4–8 Claude Code agents in parallel on the same repo, each on its own branch — if Claude Code made you 10x faster, worktrees multiply that again depending on how many agents you can manage at once
- Without a structured planning step first (like the compound-engineering-plugin's multi-agent brainstorm → plan → execute → review flow), parallel worktrees create collisions and confusion rather than speed