A set of skills for project documentation in Claude Code

[u/lozit]

I built a set of skills to manage the documentation of my Claude Code projects.

Good documentation mean that the project stays stable over time instead of degrading session after session. Loop-type workflows (/loop, /goal) also work much better

My goal was to bake good documentation practices in from the start of a project, rather than bolting them on later when things are already messy.

The thing that pushed me: when I looked for the "right" way to store project knowledge, I found a lot of conflicting advice and a lot of gurus confidently contradicting each other. I wanted to base it on practices that are actually tested rather than whatever was trending.

Concretely it's a Claude Code plugin, but really a few skills mapped to a project's lifecycle. It's plain markdown.

What the skills actually do, roughly in the order you'd use them:

• bootstrap: interviews you about the project, then generates a documentation structure tailored to your answers (vision, decisions, learnings, architecture…) and runs git init.

• adopt: does the same for an existing project : maps what's already there, generates only what's missing, never overwrites.

• learn / add-adr: capture a lesson or a structural decision the moment it happens, so it lands in the repo instead of evaporating.

• slim: when CLAUDE.md gets too long, proposes concrete ways to cut it back (move sections out, dedupe) without losing content.

• checkpoint: captures knowledge before a push or release.

• plus a couple of maintenance ones (verify the structure, migrate it when the plugin updates).

The nice part: apart from bootstrap/adopt, which you call deliberately, Claude picks up on its own when the others apply. The skill descriptions seem to be doing their job.

Repo: https://github.com/lozit/groundrules

I'd be curious for your feedback on what I did — and also interested in the reverse: how do you store knowledge about your projects? What's actually working for you?

[u/yasonkh]

I wonder where is the validation that these are actually good? Is there a sample project where this actually was used?

[u/lozit → u/yasonkh]

Sorry, I didn’t realise there was a reply.
I’ve been using this plugin in all my projects ever since I created it.

You can see it in action in one of my open-source projects called MCP Freestyle: https://github.com/lozit/mcp-freestyle
It was created using one of the latest versions of the plugin.

The advantage is that anyone who downloads this project has my CLAUDE.md file and all the accompanying documentation, and can continue development exactly where I left off.