Built Aidea for makers who ship in Cursor/Claude Code — not for Lovable users
I kept running into the same problem.
Generate a project with an AI tool → open it in Cursor → spend 30 minutes
re-explaining the whole codebase to my AI assistant.
Which files exist. What patterns we use. What NOT to touch. Every. Single. Time.
That context lives in your head, not in your IDE.
So I built Aidea to fix the handoff.
It generates a production-ready React+Vite foundation AND the bridge docs
alongside it — automatically:
• .cursorrules (Cursor reads this on open)
• CLAUDE.md (full context for Claude Code)
• AGENTS.md (OpenAI Codex + Antigravity)
• .github/copilot-instructions.md (GitHub Copilot)
35 minutes from idea to a foundation you can actually continue building
in your own IDE.
Free to try right now. Launching at $19 — one-time, no subscription.
→ aideaapp.com
Would love feedback from other Cursor/Claude Code users — is the bridge
doc angle the thing that resonates, or is it something else?
The bridge-doc angle is definitely the part that resonates.
Most AI builder tools stop at generating the project. Your stronger insight is that the real slowdown starts after generation, when Cursor, Claude Code, Copilot, or Codex have to be re-taught the project context from scratch.
That makes Aidea less about “generate a React app” and more about continuity between idea, codebase, and AI assistant. That is a sharper category than another starter kit.
The name is close, but I’d be careful with it as this grows. Aidea sounds like idea generation, while the product is really solving AI development handoff and project memory. If you keep expanding around Cursor rules, Claude docs, agent instructions, repo conventions, and IDE-ready workflows, Xevoa .com would carry that direction better as a broader dev workflow brand.
The product’s real value is not the first 35 minutes. It is making the next 35 hours easier to continue without re-explaining everything.