Guides, tools, and blueprints for builders who build with AI
Understand what every app is made of — frontend, backend, database, and how they connect. No jargon.
Read guide → Free guideHow to describe your app idea so blueprint generation captures every integration, scheduler, and AI step.
Read tips → Free guidePlain-English picks for frontend, backend, database, auth, AI, and common vendors — when to choose what.
Read guide → Free guideStep-by-step: define the problem, map user flows, design architecture, choose your stack, and set checkpoints.
Read guide → Free guideA reusable visual template for mapping pages, APIs, databases, AI prompts, and checkpoints before you code.
Read guide → Free guideTurn your blueprint into a structured, build-ready prompt for Cursor Agent mode — then let it build the app.
Read guide →Concrete tips from real blueprint generation — name what you mean, and the AI will build the right nodes.
“Subscribe via Stripe” produces a real payment node with webhook verification. “Handle payments” or “monetization” is too vague and may get lost. Same rule for any third-party service — Gmail, SendGrid, Twilio — name it by name.
“Send a summary every morning” produces a scheduler node connected to what it triggers. “Keep users updated” does not — the blueprint has no way to know you need a daily cron job.
“Summarize unread emails into 3 bullet points” produces a real AI prompt node with substance. “Use AI to help” does not — mention the task, the input, and the output you expect.
Sign up → connect account → configure → use. Spelling out the steps helps the blueprint capture the right frontend screens and checkpoint nodes between them — not just a single generic app node.
You don't need technical terms. A plain description like “when someone leaves a bad review, have AI draft a polite reply for me to approve before it posts” is exactly the right level of detail — informal tone, concrete behavior.
What the architecture preference questions are actually asking — skimmable picks for vibe coders, not a textbook.
This is what users see and click — the website or app UI. Bluemoonkey asks because it affects how your project is structured from day one.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| Next.js | React with batteries included — routing, API routes, deployment helpers. | More opinionated; you follow its folder structure. | Good default if you're unsure. Handles more out of the box. |
| React + Vite | React UI with a fast, lightweight dev setup. | You wire up more pieces yourself (routing, backend connection). | Pick if you want a lighter frontend or already know React. |
| Vue 3 | Another popular UI framework with a different syntax. | Less common in AI-generated starter repos than React. | Only if you already know Vue or have a strong preference. |
| Let AI decide | Bluemoonkey picks a sensible default for your app. | You don't steer the stack upfront. | Fine for most first drafts — you can change it later. |
The server side — APIs, business logic, talking to the database and third-party services.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| Node.js + Express | JavaScript on the server — same language as most React frontends. | You manage more structure yourself than a full framework. | Classic default; great if your frontend is already JavaScript. |
| Next.js API routes | Backend endpoints live inside the same Next.js project. | Best for small-to-medium apps; can get crowded on huge backends. | Pick when you chose Next.js and want one repo, not two. |
| Python + FastAPI | Python API server — popular for AI-heavy apps. | Two languages in the stack (Python + JS frontend). | When your app leans hard on AI, data, or Python libraries. |
| Let AI decide | Matches backend to your app description automatically. | Less control over language choice. | Default for most vibe coders — totally reasonable. |
Where your app stores data — users, posts, orders, settings, etc.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| PostgreSQL (Supabase) | Reliable relational database, often paired with Supabase auth & APIs. | You think in tables and relationships — great for structured data. | Best default for most apps with users, accounts, or payments. |
| PostgreSQL (plain) | Same database, without Supabase's extra platform features. | You set up hosting and auth wiring yourself. | When you already have a Postgres host or want full control. |
| SQLite | A single-file database on the server — dead simple. | Not ideal for many simultaneous users or multiple servers. | Personal tools, prototypes, or single-user apps. |
| Let AI decide | Picks based on whether you need accounts, scale, etc. | You don't specify storage upfront. | Fine unless you already pay for a specific database. |
Only relevant if your app uses AI — summarizing, drafting, classifying, chatting, etc.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| Anthropic (Claude) | Claude models via API — strong at writing and reasoning. | Separate billing from OpenAI; you need an Anthropic key. | When your app's AI features are text-heavy or agent-like. |
| OpenAI (GPT) | GPT models via API — huge ecosystem and examples online. | Model names and pricing change more often than you'd like. | When you already have OpenAI credits or examples you're copying. |
| Let AI decide | Blueprint picks a mainstream provider with a sensible default model. | You're not committing to a vendor yet. | Good for v1 — swap the API key later without redoing the whole blueprint. |
How users sign up, log in, and prove they are who they say they are. Skip this category if your app has no accounts.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| Supabase Auth | Email/password + social logins bundled with Supabase. | Tied to Supabase — great combo if you already use it for data. | Default for most new apps with user accounts. |
| Clerk | Drop-in auth UI and user management. | Another paid service to manage; very polished out of the box. | When you want login screens fast and hate building auth forms. |
| Auth0 | Enterprise-style identity platform. | Can feel heavy for a small side project. | Bigger apps, teams, or strict compliance needs. |
| Let AI decide | Chooses auth only if your description implies user accounts. | You don't pick the login experience upfront. | Fine if you just said “users can sign up” without a vendor preference. |
How your app sends transactional email — welcome messages, password resets, digests, alerts.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| Resend | Developer-friendly email API with simple templates. | Another API key to store — but setup is quick. | Modern apps, especially if you're already in the React/Node world. |
| SendGrid | Long-running email delivery service. | Dashboard can feel corporate; free tier has limits. | When you need volume or already have a SendGrid account. |
| Let AI decide | Adds an email node only if your idea mentions notifications or digests. | You don't name the vendor yet. | Good unless you specifically want Gmail API or something else. |
How you charge money — subscriptions, one-off purchases, checkout flows.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| Stripe | The default for online payments and subscriptions. | Webhook setup and test mode take a little learning. | Almost always the right answer for SaaS or paid plans. |
| Lemon Squeezy | Merchant of record — they handle tax in more places for you. | Less flexible than Stripe for weird billing models. | Digital products, solo founders who hate tax paperwork. |
| Let AI decide | Only adds payments if your description mentions charging users. | You don't commit to a provider in the questionnaire. | Fine if you just said “paid plan” without naming Stripe. |
For apps that post to Instagram, X, LinkedIn, etc. — or schedule content in advance.
| Option | What it is | Tradeoff in plain English | When to pick it |
|---|---|---|---|
| Official platform APIs | Connect directly to Meta, X, LinkedIn developer APIs. | Approval processes and rate limits — not instant. | When you need deep control and are okay with app review. |
| Buffer / Hootsuite-style API | Third-party tool that already connected to social networks. | Monthly cost; you depend on their supported platforms. | Faster MVP for “post to my accounts” without fighting OAuth yourself. |
| Let AI decide | Blueprint adds a scheduler + publishing node from your description. | Vendor stays generic until you build. | When you described the behavior (“post every morning”) but not the tool. |
Open your project in Cursor
Open Cursor and create or open your project folder. Starting fresh? Create an empty folder first.
Open Agent chat
Press Ctrl+L (Cmd+L on Mac). Make sure it says Agent not Chat at the top — Agent mode can create and edit files.
Paste your blueprint
Paste the exported prompt. Add at the end:
Build this app exactly as described. Start with database schema and auth, then APIs, then frontend pages.
Let Cursor run
Let it finish completely before asking questions. It may create 10-20 files — that's normal and expected.
Iterate with your blueprint
If something isn't right, go back to Bluemoonkey, click the specific node, copy its description, paste into Cursor: “Fix [component] to match this spec: [paste]”
💡 Pro tip: Save your blueprint JSON — it's your source of truth if Cursor goes off track.
A growing directory of AI tools, APIs and services explained in plain English. Find the right tool for your app — verified pricing, real use cases.
Growing with every blueprint generated
Real app architectures you can fork and build from
For creators who want to post consistently without being glued to their phone
View blueprint →For dropshippers who waste hours checking prices manually across platforms
Coming soonFor local businesses drowning in Google reviews with no time to reply
Coming soonFor founders who want a weekly newsletter but never have time to write it
Coming soonYes — the canvas, exports, imports, version history, README attachments, reference images, and shared blueprints are all completely free forever. We only charge tokens for AI-powered features: the AI Advisor, blueprint generation, and reverse engineering. You get 10 free tokens when you sign up to try everything out.
Tokens are how we charge for AI usage — the only part that costs us real money to run. 1 token = 1 AI Advisor message or 1 blueprint generation. 5 tokens = 1 codebase analysis. Token packs start from €5 for 60 tokens. Everything else on the platform uses zero tokens.
No. Your blueprints are private by default and stored securely in your account. We cannot see what you're building and we don't share your data with anyone. The only exception is if YOU choose to share a blueprint publicly using the Share feature — that's always your choice, never ours.
You do. 100%. Everything you create on Bluemoonkey belongs to you. We don't claim any rights to your ideas, your architecture, or anything you export. Download your blueprint as JSON anytime and take it with you — no lock-in.
If you can describe your app idea in plain English, you can use Bluemoonkey. Most people have their first blueprint in under 5 minutes. The AI does the heavy lifting — you just describe what you want to build and review what it creates. No technical knowledge required.
Not at all. Bluemoonkey is built for people who build with AI tools like Cursor and Claude Code. You plan the architecture here, export it as a ready-to-use prompt, and your AI coding tool does the building. Think of it as the planning layer before the building layer.
The free tools (canvas, export, import, sharing) keep working normally — tokens only gate the AI features. You can top up anytime with a token pack, or keep using the free features indefinitely.
Yes — export as JSON to save and reimport later, or export as an AI Prompt to paste directly into Cursor, Claude Code, or any AI coding tool. The export is yours to use however you want.
We use Stripe for all payments — one of the most trusted payment processors in the world. We never see or store your card details. Stripe handles everything securely.
Your data is stored in Supabase on EU servers, in compliance with GDPR. We are based in Cork, Ireland and operate under EU data protection law. You can request deletion of your account and all data at any time.