Apps: Building your app
Writing effective prompts
Practical techniques for getting the app you picture: be concrete, build in steps, describe the look, and fix things precisely.
Practical techniques for getting the app you picture: be concrete, build in steps, describe the look, and fix things precisely.
"A CRM" leaves everything to chance. "A CRM for a two-person agency: companies, contacts and deals; deals move through Lead → Proposal → Won/Lost on a board" gives the AI a structure.
Get the core flow right, then add features in separate messages: "add search to the deals board", then "add a weekly revenue chart".
Mood, colors, density and references work well: "dark, dense, like a developer tool", "playful, rounded corners, pastel colors".
Name the page and element: "on the deals board, make the Won column green" beats "change the colors".
When a change is risky, add "keep everything else the same".
If the preview shows an error, paste it or describe what you see: "clicking Save on the deal form does nothing". Draftship already repairs build errors automatically; runtime problems need your description.