A Reddit post by a developer describes testing a 450-line static CLAUDE.md against a minimal 25-line root file with dynamic skill loading across 40 multi-file refactoring tasks on their backend repo. The dynamic setup cut regression errors 38.4%, dropped per-turn input tokens from ~18,500 to under 3,200, and reduced session token spend over 45%. The team open-sourced the tool as autoharness.
autoharness is an MIT-licensed Claude Code plugin that automatically learns skills from the sessions you already run, instead of requiring hand-written, stale skill files. It targets developers using Claude Code on ongoing projects who repeatedly re-solve the same problems because nothing persists between sessions.
autoharness is an MIT-licensed Claude Code plugin that automatically learns skills from the sessions you already run, instead of requiring hand-written, stale skill files. It targets developers using Claude Code on ongoing projects who repeatedly re-solve the same problems because nothing persists between sessions.
A Reddit post argues that common Claude Code guidance — piling coding standards, architecture rules, test commands, and lint preferences into CLAUDE.md — degrades agent performance over weeks of use. The author proposes modular skill distillation as an automated alternative to maintaining one large static prompt.
A Reddit post argues that common Claude Code guidance — piling coding standards, architecture rules, test commands, and lint preferences into CLAUDE.md — degrades agent performance over weeks of use. The author proposes modular skill distillation as an automated alternative to maintaining one large static prompt.
A developer with eight years of experience says their team uses Claude Code daily, but the agent repeatedly reverts code to patterns the team deliberately moved away from, because the reasoning sits in old PRs the agent never sees. The team tried encoding rules in CLAUDE.md, which works briefly, but the file grows unmanageable and many rules' origins are forgotten. The post asks how other teams handle institutional knowledge that Claude Code lacks.
A developer with eight years of experience says their team uses Claude Code daily, but the agent repeatedly reverts code to patterns the team deliberately moved away from, because the reasoning sits in old PRs the agent never sees. The team tried encoding rules in CLAUDE.md, which works briefly, but the file grows unmanageable and many rules' origins are forgotten. The post asks how other teams handle institutional knowledge that Claude Code lacks.
A developer preparing to use Claude Code for the first time on a large professional backend-and-frontend project asks the community for production-grade workflow advice. The post seeks practices for staying in control — spec-to-test processes, documentation upkeep, and guarding against regressions — rather than fully autonomous setups, reflecting growing use of AI coding agents in serious business applications.
A developer preparing to use Claude Code for the first time on a large professional backend-and-frontend project asks the community for production-grade workflow advice. The post seeks practices for staying in control — spec-to-test processes, documentation upkeep, and guarding against regressions — rather than fully autonomous setups, reflecting growing use of AI coding agents in serious business applications.
A solo developer analyzed 61 days of Claude Code transcripts (190 sessions, 918 subagent files) to measure what actually reaches the context window, then released the resulting open-source memory orchestration setup, Hipocampo. Built entirely on native features (hooks, MEMORY.md, CLAUDE.md, skills, subagents, compaction) with no MCP, it organizes memory into resident, paged, and interrupt regimes. The measurements expose gaps: zero injected recalls in 190 conversations, hook outputs silently truncated to ~2 KB previews, and aggressive compaction removing up to 96.6% of context.
A solo developer analyzed 61 days of Claude Code transcripts (190 sessions, 918 subagent files) to measure what actually reaches the context window, then released the resulting open-source memory orchestration setup, Hipocampo. Built entirely on native features (hooks, MEMORY.md, CLAUDE.md, skills, subagents, compaction) with no MCP, it organizes memory into resident, paged, and interrupt regimes. The measurements expose gaps: zero injected recalls in 190 conversations, hook outputs silently truncated to ~2 KB previews, and aggressive compaction removing up to 96.6% of context.