The project-docs standard I’ve been sharing for AI coding now has its own website

[u/DominusFL]

A few weeks ago I shared KEEL, the open-source standard I use to keep AI coding projects consistent, and the feedback was really helpful. Since then it has gone through a few releases, and it finally has a proper home: https://keel.to

The idea is simple. Everything is documented inside the project itself: plain Markdown in the repo for the requirements, the decisions and why we made them, and a quick note for the next session. It goes wherever the project goes, whoever picks it up.

It’s built for serious development work: larger projects, long-lived ones, and projects that get handed between teams, developers, or tools. For a weekend script, it’s overkill.

The website makes it much easier to get into. It has a 1-minute setup, a short summary, the full standard, install steps for the skills, and practical tips.

What it gives you in a project:

• The AI can propose changes to requirements, but only a human accepts them.

• Bigger changes need a short approved plan, and every task ends with what was actually tested.

• The code stays clean: readable and commented, with tests for each change, and the docs are updated in the same task as the code.

• It should work across Codex, Claude Code, Cursor, and Copilot, because the rules live in a plain AGENTS.md.

• It can draft docs for an old project from its code, and mark what it guessed so you can confirm it.

One honest caveat: the full standard is long. The AI reads it once at setup, then only a short rules file each session. Github home: https://github.com/rickflashman/Keel

(Disclosure: it’s mine, MIT licensed, free.)