Be Specific About What You Want
Vague requests lead to generic results. Specific requests get you closer to what you actually need.| Instead of… | Try… |
|---|---|
| ”Make a tracker" | "Make a workout tracker where I log exercises with sets, reps, and weight" |
| "Build a dashboard" | "Build a sales dashboard showing monthly revenue, top products, and a trend chart" |
| "Create a form" | "Create a contact form with name, email, message, and a submit button that shows a confirmation” |
Attach Images and Files
You can attach images or files (txt, pdf) to your messages. This is useful for:- Demonstrating UI: Share a screenshot of a design you want to replicate
- Highlighting errors: Attach a screenshot showing what’s wrong with the current implementation
- Sharing documentation: Include specs, requirements, or reference material for specific features
Start Simple, Then Add Complexity
Don’t try to describe everything upfront. Start with the core functionality, get that working, then layer on features.- “Create a todo list with add and delete”
- “Add due dates to each item”
- “Add priority levels: high, medium, low”
- “Sort by priority, then by due date”
Ask for Changes Clearly
When something isn’t right, be specific about what needs to change:- Good: “The save button should be blue instead of gray”
- Good: “Move the total to the bottom of the list”
- Good: “When I click submit, show a loading spinner”
- Vague: “Make it look better”
- Vague: “It’s not working”
Provide Examples When Helpful
If you have a specific vision, reference it:- “Make it look like a Notion database”
- “I want the layout similar to Trello with columns”
- “Use a card-based design like this screenshot”