Last Update: September 6th, 2026

<aside> 💡

In short: Tell Shipper what users need to accomplish, how the experience should work, and what must stay unchanged. Give it real examples, then build and test one meaningful piece at a time.

</aside>

This is a practical guide to turning a rough idea into a working app with clearer prompts, fewer retries, and less accidental rework.

There is no secret syntax to learn. You can write naturally. The difference between an average result and a strong one usually comes down to context, specificity, and how you split the work.

Prompting is a build loop

You do not need one enormous, perfect prompt. Treat every result as the next version of the product. Give Shipper a clear direction, review what it built, and refine it in focused rounds.

  1. Describe: Explain the outcome and relevant context.
  2. Build: Let Shipper create one coherent piece.
  3. Review: Try the flow and inspect every state.
  4. Refine: Ask for a precise change, then repeat.

💡 Your first result is a foundation

Start with the core product and the most important user journey. Add secondary features after that path works. This makes each change easier to review, debug, and undo.

Before you build anything

Spend a minute defining the direction. You do not need a long specification. You should be able to answer these six questions: