Start with the big picture
Begin with a clear description of what the app does and who it’s for. The AI uses this to make architecture and design decisions.Be specific about features
List the features you want. The more specific you are, the closer the result matches your vision.Describe the user experience
Tell the AI what happens when someone uses the app. This helps it build the right navigation and flow.Specify design preferences
If you have a visual direction in mind, describe it. Otherwise, the AI picks a clean default.Iterate in small steps
Don’t try to build everything in one message. Start with the core flow, then add features incrementally.Reference what exists
When iterating, reference specific screens or elements so the AI knows what to change.Common prompt patterns
Starting a new app
Adding a feature
Fixing an issue
Changing design
Connecting a backend
What to avoid
- Don’t give conflicting instructions in the same message
- Don’t describe implementation details (specific code, file structures) unless you need a very specific approach — the AI handles architecture decisions
- Don’t overload a single message — break complex features into steps
- Don’t assume context from previous conversations — each project session has its own history, but be explicit about what you want
