Prompt for better results

Turn product intent into focused direction Superapp can build from.

Superapp makes stronger product decisions when it understands the person, the moment, and the outcome—not only a list of screens. A useful prompt sets direction while leaving room for the system to choose the right native implementation.

Start with a compact product brief

Describe the app in one short paragraph before listing details. Name the target user, their situation, the task they need to complete, and what a successful session looks like.

Build an iPhone app for independent bakers preparing weekly orders.

The main job is turning confirmed orders into a calm, prioritized prep plan.
It should be fast to scan with flour-covered hands and require very little typing.

Declare the priority and the boundaries

When speed, simplicity, visual character, and feature depth compete, tell Superapp which quality wins. Then remove tempting extras from the first build.

• Primary goal: “Optimize for a one-minute daily check-in.”
• Scope: “One main flow, three screens, no social features.”
• Platform: “Design for iPhone first and comfortable one-handed use.”
• Quality bar: “Prioritize clarity and finish over additional features.”

Describe behavior, including edge cases

Explain what happens after a tap, what changes on screen, and what persists after the app closes. Include empty, loading, offline, permission-denied, and failed states when they matter. This turns a feature request into a testable interaction.

Set a visual direction with useful references

Name two or three qualities such as quiet, energetic, editorial, dense, or playful. If you attach a reference, identify the specific lesson to take from it—navigation rhythm, typography, spacing, or motion—rather than asking for a copy.

“Make it look premium.”

Too vague

The desired hierarchy, tone, and interaction quality remain undefined.

“Quiet and precise.”

Actionable

Use generous spacing, restrained color, crisp type, and subtle feedback on taps.

Ask motion to explain something

Motion should confirm an action, show where content came from, or preserve context during navigation. Request quick, subtle transitions and responsive pressed states. Avoid animation that slows a repeated task or competes with the content.

Improve one outcome at a time

Test the current build, describe the observed behavior, and request one coherent change. A narrow follow-up is easier to verify and less likely to disrupt a working flow.

On the order detail screen, keep Mark as packed visible while scrolling.
After it is tapped, update the status immediately and keep it after relaunch.
Do not change the order list or navigation in this pass.