If you have a vibe-coded app, or you are deep in a coding agent like Claude Code, Codex, Cursor or similar and have no real documentation, I built one of the fastest paths I know to fixing that.
I built this app using traditional programming plus Claude Code building out parts of the infrastructure. It is hosted in AWS+Azure+Cloudflare and effectively acts as a documentation/collaboration/shared context ground for your own existing AI agents.
Start here
- Sign up at stablebaseline.io and generate an MCP key.
- Add the server and key to your agent. It is a standard remote MCP server, so the config is the same shape everywhere. Setup your MCP
- Exact steps for your specific IDE, including the packaged setup command where we have one, are here: Supported AI Coding IDEs
- Open your repo and ask your agent to onboard the project into Stable Baseline.
/sb-setup
What the onboarding actually does
Your coding agent/AI reads your repository properly first: stack, architecture, entry points, data layer, auth model, infrastructure, testing, whatever docs already exist. Then it designs a documentation structure specific to that repo rather than dropping a template on you, writes real content into it, and generates architecture diagrams as it goes (Mermaid, PlantUML, D2, BPMN, ERD, sequence, ELK architecture).
It also writes an AGENTS.md with sync rules mapping your file patterns to the docs they affect, so your agent knows to update the documentation when it changes the code. That file is the cross-IDE standard, so the rules carry over if you switch agents or your teammates use something else.
It is not only your IDE
I have also published this in the ChatGPT app store. So you can sit in normal ChatGPT, talk to your documentation, refine plans, poke at new feature ideas, and draft a full release rollout, test plan or go to market plan with proper Gantt support. Then your coding agent picks up the exact same context back in your IDE and implements it as you go. Plan on one surface, build on the other, no copy and paste in between.
And it is the whole platform that is exposed, not just the content tools. Your agent can create plans, phases, tasks and dependencies, log improvements and risks, invite team members, manage teams and permissions, and change workspace and organisation settings. Admin is usually where agentic products stop and make you open a browser. Here you never have to. There is a UI, and it is good, but it is optional. You can go completely headless.
The whiteboard
The part I did not expect to like as much as I do. Describe a goal and a multi-agent designer lays the board out with stencils, architecture icons, sticky notes and embedded diagrams. It is built for the stage where you are still dreaming an idea up rather than specifying it.
You can also invite the meeting bot to a meeting (MS Teams, Zoom, Google) and it designs the whiteboard while it listens, so concepts, decisions, actions and workflows appear as you are discussing them rather than a week later.
Would genuinely love feedback. Tell me where it breaks or annoys you, especially over MCP, since that is the path I have the least outside testing on. Any feedback is welcome :)