In the past few months, I’ve been building and shipping things extremely fast. Some of the MVPs that I built for my friends were completely vibe-coded and shipped within a day to show a demo. While it was a great experience working with AI tools, I wanted to make sure some basics were followed, decisions of what and why written down, obvious things not skipped and that it could scale.

That’s why I built persist-os. It’s a CLI that runs locally. No network required. It records the architecture decisions and standards in plain files in the repo and 'persist doctor' checks them - it flags if anything contradicts or is missing, or if the task is done with no tests. Because the rules live in your repo files, it doesn't matter if you start a new session or the session is compacted - the standards and rules survive.

MIT licensed. Here’s how you can try it: npx persist-os@latest init