Skip to main content

​
Starting from your first prompt

This page is only about shaping the first Build message. For patterns and weak/adequate/strong examples, see Writing better prompts. For a full walkthrough, see Build your first app.

​
From fuzzy idea to brief

Write four lines before you hit send:
  1. Who uses it (roles in plain words)
  2. Main jobs each role does
  3. Must-have constraints (privacy, no public API, compliance stop-lines)
  4. Success check (“dispatcher can clear the queue in Preview”)
Example shape:
Build an intake app for a coaching practice. Coaches invite clients. Clients answer a short weekly check-in. Coaches see open items that need attention. Email me a Monday digest. Clients must never see each other’s answers.
GenieForge will choose the screens and automations. Judge the plan by whether those journeys and rules look right.

​
Plan first

For non-trivial apps, let the AI propose a plan before it builds. Approve when the roles and journeys look right.

​
What not to paste

Do not paste production database URLs, API keys, or passwords into chat. Use App Settings → Connections → Environment Variables. Put durable preferences in Build rules.