[{"data":1,"prerenderedAt":46},["ShallowReactive",2],{"$fCxkBJW_Dw8hSfAadbQXKGFy8jmc2iNc88bvB_0UAjUc":3},{"date":4,"generated_at":5,"picks":6,"candidates_scanned":44,"candidates_scored":45},"2026-04-05","2026-04-05T06:00:00.000000+00:00",[7,21,33],{"rank":8,"title":9,"source":10,"url":11,"category":12,"tldr":13,"score":14,"scores":15,"why":20},1,"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.","Reddit r/ClaudeAI","https://www.reddit.com/r/ClaudeAI/comments/1sc65st/i_gave_claude_code_a_285line_operating_manual_and/","Guide","- 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\n- 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\n- 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\n- PostToolUse validates every .md Claude writes (frontmatter, wikilinks, correct folder) before mistakes compound; Stop auto-archives completed projects and checks for orphan notes\n- The 285-line CLAUDE.md is the keystone — consistent note schema is what makes synthesis work, not clever prompting",64,{"direct_claude_relevance":16,"practical_utility":17,"novelty":18,"source_credibility":19},28,20,11,5,"This is one of the most detailed real-world Claude Code hooks configurations shared publicly — five hooks wired to a semantic search index, a message classifier, a frontmatter validator, and session archiving. The CLAUDE.md structure and dual-memory-system pattern (Claude's ~/.claude/ for session prefs, the vault's brain/ folder for durable knowledge) are directly portable to any project. The key insight — that vault structure matters more than prompts — is validated by a month of daily use and is immediately actionable for anyone running Claude Code on a documentation-heavy project.",{"rank":22,"title":23,"source":10,"url":24,"category":25,"tldr":26,"score":27,"scores":28,"why":32},2,"I got Claude Code to stop burning 40K tokens by just figuring out my codebase","https://www.reddit.com/r/ClaudeAI/comments/1scq9vk/i_got_claude_code_to_stop_burning_40k_tokens_by/","Tutorial","- 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\n- 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\n- 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)",63,{"direct_claude_relevance":29,"practical_utility":30,"novelty":31,"source_credibility":19},22,24,12,"The token savings are real and benchmarked on actual codebases — 66K down to 5K tokens for a 92-file project, 46K down to 4K for a 53-file project. The blast-radius analysis (\"if I change this file, what breaks?\") is a particularly useful addition beyond basic file summaries. The tool ships an MCP server and Claude Code profile so the `.codesight` folder is treated as high-priority context automatically, and it works on TypeScript, Python, and Go stacks.",{"rank":34,"title":35,"source":36,"url":37,"category":12,"tldr":38,"score":39,"scores":40,"why":43},3,"Senior engineer best practice for scaling yourself with Claude Code","Reddit r/ClaudeCode","https://www.reddit.com/r/ClaudeCode/comments/1sciznh/senior_engineer_best_practice_for_scaling/","- 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\n- 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",60,{"direct_claude_relevance":41,"practical_utility":17,"novelty":42,"source_credibility":19},25,10,"The combination of git worktrees + a documented multi-agent planning process is the clearest articulation of the emerging \"parallel Claude Code\" workflow that senior engineers are converging on. The compound-engineering-plugin (github.com/EveryInc/compound-engineering-plugin) is a concrete starting point most developers haven't seen. The post's honest caveat — that worktrees without planning just produce parallel chaos — is more useful than the typical boosterism around multi-agent setups.",50,15,1776575098421]