Blueprint mode: draw the app's architecture, then hand it to an agent

[MrWeb]

Hi Nick 👋

This is already fully implemented and working. The whole feature is in the draft PR #1067, ready to try (npm run check passes). I'm opening this to ask whether you want it, not to propose something that still needs building.

First, an apology: I should have opened this before writing any code. CONTRIBUTING.md asks for an issue first for anything that adds a new surface, and for small focused PRs. I got carried away and built the whole thing in one go, end to end, and it's already up as a draft: #1067. I'm not expecting it to be merged as is. I'd rather hear what you think of the idea first, and I'm happy to split it into small PRs, change direction, or drop it.

The idea: a Blueprint mode

When I ask an agent to build or change a feature, it decides the structure on its own. After a few rounds I lose track of the overall shape of my project.

Blueprint is a second mode next to Development (a toggle in the title bar). It replaces the workspace with a canvas where you draw the app's architecture: typed boxes (Screen, Component, Service, DB, API, Queue, External, General) with a title and instructions, joined by labelled arrows. It's saved to .monocode/blueprint.json in the project, so it can be versioned.

From there:

• Implement (selection or all) opens a chat with the blueprint as a structured brief, not a screenshot. The rules: follow this structure, don't add or drop components, ask when something is unclear. The agent first replies with a TODO plan grouped by box and waits for approval before it writes any code.
• Draw it from the code: when a project has no blueprint, an agent can read the codebase and draw it.

A small Laravel project drawn with "Draw it from the code".

The PR has more screenshots and the details (multi-select, undo/redo, auto layout, and a couple of WebKit workarounds).

Questions

1. Does this fit where you want MonoCode to go?
2. If yes, how would you like it split up? My guess: (1) the canvas and file format, (2) the Implement flow, (3) the layout tools.
3. Anything you'd do differently, like where the toggle lives, the file location, or the dependencies (@xyflow/react, @dagrejs/dagre)?

Thanks for MonoCode, I use it every day.

[hardbeat920]

this looks quite interesting i just wonder if its something that should be inside Monocode?

ive been tinkering with the idea of add ons / extensions that people can add to monocode and extend its functionality

we are not there yet though.

@MrWeb what do you think?

[MrWeb]

I like the addon idea, for sure, and this may be something not everyone wants, the plugin idea would solve it for sure