Claude Md banner
orpheuscode orpheuscode

Claude Md

Development community

Description

Building on iamfakeguru's directives for Claude Code

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

CLAUDE.md — Merged Production-Grade Agent Directives

Production-grade agent directives for Claude Code, built by stress-testing and merging two independent approaches to the same problem: how do you override Claude Code's default behaviors to produce code that actually compiles, survives long sessions, and meets the standard a senior engineer would approve?

Origin

On March 31, 2026, [@iamfakeguru](https://x.com/iamfakeguru) published a thread reverse-engineering Claude Code's internal architecture from leaked source and billions of tokens of agent logs. The thread identified specific mechanical bottlenecks — silent file read truncation, context compaction destroying working memory mid-refactor, tool result clipping, and system prompt defaults that actively bias the agent toward minimal output over correct output — and proposed a CLAUDE.md file that overrides all of them.

**Original thread:** [x.com/iamfakeguru/status/2038965567269249484](https://x.com/iamfakeguru/status/2038965567269249484)

**Original repo:** [github.com/iamfakeguru/claude-md](https://github.com/iamfakeguru/claude-md)

This repo takes that work as a starting point and merges it with an independently developed set of directives focused on code quality standards, architecture principles, communication protocols, and explicit forbidden patterns — areas the original did not cover. The result is a single file that addresses both layers: how to drive the agent mechanically, and what good output looks like once it's running correctly.

What Problem This Solves

Claude Code has structural constraints that produce predictable failures. These are not bugs — they are architectural tradeoffs baked into how context windows, tool execution, and system prompts work. If you do not override them, you will encounter every one of these:

Failure Root Cause Directive
"Done!" with 40 type errors Tool reports success when bytes hit disk, not when code compiles §8.1 Forced Compilat