​

Writing better prompts

​

Lead with outcome and audience

Say who uses the app and what success looks like. “Trainers need a session roster and clients need homework forms” beats “make some pages.”

​

Name roles early

If different people should see different screens or tools, say so. GenieForge enforces roles; naming them early avoids rebuilding access later.

​

Prefer product nouns

Ask for forms, pages, automations, notifications, and portals by outcome. The AI maps those to GenieForge primitives.

​

Call out hard constraints

Examples: “clients must never see other clients’ data”, “no public unauthenticated API”, “emails only to verified addresses”, “this may involve health data so stop and we will talk to support first.”

​

Iterate with Preview

After a change, use Preview as the role you care about. If something fails, paste the error and ask for a fix in Build mode.

​

Related

• Build your first app
• Roles and access control