​

Starting from your first prompt

​

Plain-language prompt

Describe who the app is for, the main jobs, and any must-have constraints (roles, compliance boundaries, integrations). Example shape:

Build an intake app for a coaching practice. Coaches invite clients. Clients fill a weekly check-in form. Coaches see a dashboard of open items. Send me an email digest every Monday.

​

Plan first

For non-trivial apps, let the AI propose a plan before it builds. Approve when the data model and surfaces look right. That keeps major structure intentional instead of accidental.

​

Constraints that stick

Put durable preferences in Build Rules (naming, UX tone, domain rules). Put secrets in Environment Variables, not in the prompt. Put role boundaries in Roles and confirm with Preview as.

​

What not to paste

Do not paste production database URLs, API keys, or passwords into chat. Use the secure prompts GenieForge shows, or App Settings → Environment Variables.

​

Related

• Writing better prompts
• How building works
• Secrets and safe execution