Prompts to copy

These are the messages I send Claude at each step, in the order you'll need them. Copy one, fill in the parts in [square brackets], and send it.

Use them in the Code tab of the Claude desktop app, after you have connected NodeGX. Keep your own words short. NodeGX keeps the brief and the plan, so you don't have to repeat them.

Your first message

Use this to start a new app. Say as much about the idea as you like.

I want to build an app in NodeGX: [describe the whole idea in your own words].

About me:
- How much I know about building apps: [nothing / a little / I've built a few]
- Who the app is for: [the people who will use it]
- What I already have: [a spreadsheet, a paper form, an old app, nothing]

Don't build anything yet. Ask me questions first, one at a time,
and tell me what I've forgotten.

Plan it

Use this once you've talked the idea through. More on this in Plan before you build.

Let's plan this NodeGX app before you build anything.
Help me agree what it does, who uses it, what it stores, its pages,
and what it will not do. When we agree, create the project in NodeGX
and show me the plan. Don't build the pages yet.

Show me a mockup

Use this before a page is built, so you can change your mind cheaply. See See it before it's built.

Before you build the [page name] page in NodeGX, show me a mockup of it.
Keep it simple. I'll tell you what to change.

Build it

Use this for one page or one feature at a time, in its own conversation.

Build the [page name] page in NodeGX, following the plan.
When it's done, render it and check it looks right,
then tell me what you built and what you checked.

I changed things

Use this after you've changed anything in the NodeGX editor yourself. Claude remembers what it read earlier and may not look again unless you ask. See Changing things yourself.

I've changed some things in NodeGX myself. Please look at the project
again before you change anything else.

Something's wrong

Use this when the app doesn't do what you expected. Add a screenshot or paste the whole error message. See When something goes wrong.

In NodeGX, on the [page name] page, I [what you did].
I see [what happened].
I expected [what should have happened].
[paste a screenshot or the whole error message]

Explain before fixing

Use this when the same fix has failed twice.

Stop. This fix hasn't worked twice now.
Before you change anything else in NodeGX, explain what you think
is causing this, and how you would check that you're right.
Don't change anything yet.

Open my project again

Use this at the start of each new conversation. See One job per conversation.

Please open my NodeGX project "[project name]" and read its brief and plan.
Tell me what's built and what's left, then we'll pick today's job.

Check the app against its brief

Use this every few jobs, or before you show the app to anyone.

Read this NodeGX project's brief. Then go through the app page by page.
Tell me what the brief asks for that the app doesn't do yet,
and what the app does that the brief doesn't mention.
Don't change anything.

How do I put this online?

Use this when the app works on your computer and you want other people to use it. See Putting your app online.

I want to put my NodeGX app online. Look at the project and tell me
what it needs to go live. Recommend one way to do it, say what it will
cost, and walk me through it one step at a time.

Messages that don't work

• Too vague: "Fix it." "Make it better." Say what you see and what you expected.
• Skipping the plan: "Just do it." Claude will, and you'll find out afterwards what it thought you meant.
• Too many jobs at once: "Build the whole app." Ask for one page or one feature.

Quick reference

• Start with your idea and a few lines about you.
• Plan, then mockup, then build one page at a time.
• Tell Claude when you've changed things yourself.
• "I see this, I expected that", plus a screenshot.
• New conversation? Ask Claude to open your NodeGX project and read its brief and plan.