The problem nobody talks about Everyone's excited about context engineering — CLAUDE.md files, structured docs/ folders, per-developer "current state" files. But as your project grows, you end up with something like this: docs/ ├── architecture.md (8,200 tokens) ├── decisions.md (12,400 tokens) ├── tech_debt.md (6,100 tokens) ├── api-patterns.md (4,300 tokens) ├── context/ │ ├── current_state_alice.md │ ├── current_state_bob.md │ └── feature_index.md └── history/ ├── 2026-04-auth-rewrite.md └── 2026-03-migration.md Enter fullscreen mode Exit fullscreen mode Now you have two problems: You can't see the forest for the trees — browsing .md files in a terminal or IDE one at a time doesn't give you a sense of the whole Token bloat is invisible — you don't know which files are eating your context budget until Claude starts truncating things What I built human-context — a single .html file that turns your docs folder into a browsable knowledge base. No server. No npm install. No build step.…