Prompts that work

Describe shape, not words. Examples of good and bad prompts.

  • 4 min read
On this page
  1. Three principles
  2. Good vs bad
  3. Tagging files and components

Three principles #

  1. Describe the shape of the result, not the words it should contain.
  2. Name the table or field directly when it matters — “the customers table” beats “the data.”
  3. Iterate in small steps. One change per prompt makes it easy to undo.

Good vs bad #

Tagging files and components #

You can drop a file path into the prompt with @ — the agent will read that file before responding. Useful when you want to change something specific without describing it.

Text
In @src/pages/Dashboard.tsx, replace the bar chart with a line chart.

Skip the docs.Just describe it.

Tadabase AI builds it, hosts it and keeps it running. Real backend, real domain, real app.

Plain English. It asks follow-up questions like a real developer.

  • Free plan, no card
  • Unlimited app users
  • Live on your own domain