[{"data":1,"prerenderedAt":44},["ShallowReactive",2],{"$f5aJMXLx1JbVIFzeQJDjc2E-xEMcADMYOdeqJULfyshY":3},{"date":4,"generated_at":5,"picks":6,"candidates_scanned":42,"candidates_scored":43},"2026-03-23","2026-03-23T05:30: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,"Orchestration -- the exact prompts I use to get 3-4 hour agentic runs","Reddit r/ClaudeAI","https://www.reddit.com/r/ClaudeAI/comments/1s0nktx/orchestration_the_exact_prompts_i_use_to_get_34/","Guide","- The entire system is a 25-line PLAN.md file that tells Claude *how* to plan AND *how* to implement — not a complex multi-agent framework, something anyone can write themselves\n- Planning phase (~30 min): Claude asks a few questions upfront, then generates a milestone-specific plan file that embeds its own implementation instructions\n- Execution phase (2-4 hours): a fresh Claude agent reads that plan file and runs fully autonomously — implementation, validation, and self-correction all baked into the file's instructions\n- Built-in code review: 4 separate second-opinion calls to a different agent (Claude/Codex) covering KISS, style, correctness, and goal fulfillment — Claude *must* address objections before it ships\n- Author links to the actual PLAN.md and a real PLAN-M3.md on GitHub so you can copy the format directly into your own projects",63,{"direct_claude_relevance":16,"practical_utility":17,"novelty":18,"source_credibility":19},22,26,10,5,"Most 'run Claude autonomously for hours' posts are vague hand-waving or require installing someone else's black box. This one shares a 25-line markdown file that anyone can read and adapt immediately. The built-in multi-agent review loop — four second-opinion calls that block completion until objections are addressed — is a concrete pattern for keeping long agentic runs on track without human intervention. Real GitHub links make it verifiable, not just aspirational.",{"rank":22,"title":23,"source":24,"url":25,"category":12,"tldr":26,"score":27,"scores":28,"why":32},2,"Hook-Based Context Injection for Coding Agents","Reddit r/ClaudeCode","https://www.reddit.com/r/ClaudeCode/comments/1s15sdl/hookbased_context_injection_for_coding_agents/","- Instead of dumping everything into CLAUDE.md at session start (where it gets buried 20 minutes later), inject only the *relevant* conventions the moment Claude touches a specific file — via PreToolUse hooks\n- A billing file gets billing-specific docs injected; a frontend component gets component conventions — all-match routing, general first, domain-specific last, landing at the recency end of the context window\n- PostToolUse runs grep-based architecture checks that block basic violations (wrong logger, fetch outside hooks, etc.) before Claude can move on\n- Tested on 15-file context decay runs with both Haiku and Sonnet: 108/108, zero degradation from file 1 to file 15",60,{"direct_claude_relevance":16,"practical_utility":29,"novelty":30,"source_credibility":31},20,12,6,"Context decay — Claude following your conventions perfectly at file 1 and ignoring them by file 10 — is one of the most frustrating problems for anyone using Claude Code on real codebases. This post offers a targeted fix using Claude Code's own PreToolUse/PostToolUse hooks to inject conventions at the moment of action rather than session start. The 108/108 test result across 15 files is a meaningful, reproducible claim backed by a linked blog post.",{"rank":34,"title":35,"source":24,"url":36,"category":12,"tldr":37,"score":38,"scores":39,"why":41},3,"PSA for heavy daily use Claude Code users: give yourself a gift and get 'claude-devtools'","https://www.reddit.com/r/ClaudeCode/comments/1s132j8/psa_for_heavy_daily_use_claude_code_users_give/","- claude-devtools reads the log files Claude Code already writes to ~/.claude/ and turns them into something readable — no wrapper, no changed behavior, just visibility\n- Token breakdown across 7 categories (CLAUDE.md files, tool inputs/outputs, thinking tokens, skill activations, user text, etc.) — finally see exactly what's eating your context window\n- Full subagent tree: when Claude spawns sub-agents, you see each one's prompts, tool calls, cost, and duration as a nested tree — including agents that spawn more agents",58,{"direct_claude_relevance":16,"practical_utility":29,"novelty":40,"source_credibility":19},11,"Claude Code's terminal output summarizes tool calls into near-useless lines like 'Read 3 files' and 'Edited 2 files' with no detail on which files or what changed. claude-devtools solves this by parsing the raw logs that already exist, giving you full diffs, exact token breakdowns by category, and a nested subagent execution tree — without changing how Claude Code works. The kind of tool you don't realize you need until you've wasted time wondering why Claude forgot something mid-session.",50,30,1776402243444]