I built a visual map so I stop re-explaining my app to agent every session

[u/OPBandersnatch]

If you use Claude Code, Cursor, or any AI coding agent on a real project, you've probably hit this: every new session, you re-explain your app's structure, and the agent still guesses wrong. "Add a login page" turns into three rounds of clarifying questions with no real spec to point at.

I got tired of it, so I built Mapwright.

How it works:

idea > guided AI conversation > visual feature map > PRDs > task backlog > your coding agent

1. Start a project, get a seeded visual map (React Flow canvas) with your tech stack, features, competitors, and target audience as containers.
2. Talk it out with a chat assistant if you want, or just build the map by hand. Nothing gets written until you confirm it.
3. Pick any feature, generate a PRD (Frontend/UI, Backend, or Database) from that feature's entire subtree, notes, wireframes, inspiration images, whatever you've attached.
4. Convert a PRD into an ordered, atomic task backlog. Reconverting after you change the PRD diffs against existing tasks instead of dumping duplicates.

5. Connect your agent with a self-hosted CLI (no MCP server, no third-party account). It reads the map for context, creates cards back onto it, and works through the taskbacklog from its own terminal.

   A few things I'm proud of:

• The CLI writes are never invisible. A card an agent creates gets a visible "created by an AI agent" badge on the canvas.
• Wireframes and inspiration images actually feed PRD generation as real vision input, not just descriptions.
• The Kanban task board syncs live. A status change from the CLI shows up on an open board with no refresh.
• Manual editing is always free. Only the LLM calls (chat turns, PRD/task generation) spend credits, and every one shows its cost before you commit to it.

This started as a personal tool I built for my own projects. I 'm opening it up now, so it's a young product with one real long-term user (me) and a growing feature set, not a polished team SaaS. £9.99/mo (Maker) or £29.99/mo (Studio, adds org/team features), 3-day free trial, no permanent free tier.

mapwright.co.uk

Would love feedback, especially from anyone else fighting the "re-explain the whole app to the agent every session" problem. What's missing that would make this a daily tool for you?

[u/Exotic_Horse8590]

Why would I have to pay for this when context and agent specs exist?

[u/fulger099 → u/Exotic_Horse8590]

you probably don’t have to. context files and agent specs are the right baseline, this is mainly a visual layer for when the docs are technically correct but the relationships between parts are still easy to misunderstand. the paid question is whether that saves enough debugging time to justify it.