All notes

Prompts

5 min read

The prompt is the spec

A vague prompt gets a vague product. The work moved from writing code to writing what the code must do.

The quality of what an agent builds tracks the quality of what it is asked, almost exactly. A prompt that says make it nice gets something generic. A prompt that says what nice means for this user, on this screen, gets something you can ship.

What a good prompt holds

  • The goal, in one sentence a user would recognise

  • The constraints: the stack, the files to touch and the ones to leave

  • What done looks like, as a test someone could run

  • What to do when unsure: ask, never guess

prompt.md

Goal: a freelancer sees how much tax to set aside from each payment.
Touch: app/taxes/*, lib/tax.ts. Leave the billing code alone.
Done: the tests in tax.test.ts pass for PT, ES and DE.
If a rule is unclear, stop and ask.

None of this is new. It is what a good ticket always said. The difference is that now the ticket is executed in minutes, so a bad one costs minutes too, and you write a lot more of them.

Writing the spec used to be the boring part. Now it is the part that builds the product.

The quality of what an agent builds tracks the quality of what it is asked, almost exactly. A prompt that says make it nice gets something generic. A prompt that says what nice means for this user, on this screen, gets something you can ship.

What a good prompt holds

  • The goal, in one sentence a user would recognise

  • The constraints: the stack, the files to touch and the ones to leave

  • What done looks like, as a test someone could run

  • What to do when unsure: ask, never guess

prompt.md

Goal: a freelancer sees how much tax to set aside from each payment.
Touch: app/taxes/*, lib/tax.ts. Leave the billing code alone.
Done: the tests in tax.test.ts pass for PT, ES and DE.
If a rule is unclear, stop and ask.

None of this is new. It is what a good ticket always said. The difference is that now the ticket is executed in minutes, so a bad one costs minutes too, and you write a lot more of them.

Writing the spec used to be the boring part. Now it is the part that builds the product.

The quality of what an agent builds tracks the quality of what it is asked, almost exactly. A prompt that says make it nice gets something generic. A prompt that says what nice means for this user, on this screen, gets something you can ship.

What a good prompt holds

  • The goal, in one sentence a user would recognise

  • The constraints: the stack, the files to touch and the ones to leave

  • What done looks like, as a test someone could run

  • What to do when unsure: ask, never guess

prompt.md

Goal: a freelancer sees how much tax to set aside from each payment.
Touch: app/taxes/*, lib/tax.ts. Leave the billing code alone.
Done: the tests in tax.test.ts pass for PT, ES and DE.
If a rule is unclear, stop and ask.

None of this is new. It is what a good ticket always said. The difference is that now the ticket is executed in minutes, so a bad one costs minutes too, and you write a lot more of them.

Writing the spec used to be the boring part. Now it is the part that builds the product.

Written by Kai Moreno

Independent product engineer, Lisbon

Ready to ship?

Let’s build together.

From the first version to production, at a startup’s speed and with a senior engineer’s care. Tell me about your product.

2 builds open for December

Ready to ship?

Let’s build together.

From the first version to production, at a startup’s speed and with a senior engineer’s care. Tell me about your product.

2 builds open for December

Ready to ship?

Let’s build together.

From the first version to production, at a startup’s speed and with a senior engineer’s care. Tell me about your product.

2 builds open for December

Create a free website with Framer, the website builder loved by startups, designers and agencies.