​

Writing better prompts

GenieForge builds from what you say. Better prompts name who, what must happen, hard rules, and how you will know it worked. You do not need to specify which internal pieces GenieForge should create.

​

Same idea, three prompt qualities

Weak

Make some pages for requests.

Likely result: vague screens, unclear roles, weak access. Adequate

Staff should take requests from people on the team and work through an open queue.

Likely result: a usable desk, but soft privacy and fuzzy ownership. Strong

Build an internal request desk. Roles: requester and dispatcher. Requesters submit title, details, and priority, and see only their own requests. Dispatchers see everyone else’s open items, assign an owner, and mark done. Email the requester when done. No public unauthenticated API.

Likely result: two role experiences, clear ownership, a done notification, and access rules you can Preview. GenieForge chooses the screens, actions, and automations. Your job is the business contract above.

​

Patterns that work

​

Lead with outcome and audience

Say who uses the app and what success looks like in their words.

​

Name roles early

If different people should see different things or be allowed to do different actions, say so. GenieForge enforces roles. Naming them early avoids rebuilding access later.

​

State 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.”

​

Describe the journey, not the recipe

Talk about submit, assign, review, notify, import, digest. Avoid shopping lists like “add a tool, a form, and a hook.” If GenieForge proposes a plan, judge whether the roles and journeys look right, not whether every blueprint label matches a mental model.

​

Point when words are fuzzy

On a builder page, use Select UI to chip the exact control or region into chat. See Select UI on pages.

​

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
• Starting from your first prompt
• Roles and access control
• Build rules