Yggdrasil

Yggdrasil

**Say it once.**

Write a rule and it holds in every session after that, without you repeating yourself. Before the agent edits a file it gets only the rules that touch that file, not all two hundred. After the edit they are checked, and a violation comes back as an error the agent has to fix before it moves on. The same checks re-run in CI for free, with no API key.

[](https://github.com/krzysztofdudek/Yggdrasil/actions/workflows/ci.yml) [](https://www.npmjs.com/package/@chrisdudek/yg) [](https://opensource.org/licenses/MIT) [](https://codecov.io/gh/krzysztofdudek/Yggdrasil) [](https://github.com/krzysztofdudek/Yggdrasil/discussions)

---

You probably don't feel this problem, and that is the interesting part

If you have ever been the only thing standing between an agent and production, solo, after hours, shipping something fast to find out whether it was worth building, then you know the wall. Code arrives faster than you can keep quality up with it. From there it goes one of two ways. You slow to a crawl because you now have to watch everything yourself, or you lose the thread and end up with bugs you can no longer trace back to a decision.

If you work somewhere that pays for quality, you have probably never hit that wall. Review, QA and the rhythm of a sprint sit between you and it. Those same things mean you have never seen your own unconstrained speed either.

Nobody measures this in either direction. The best-known study measured experienced developers **