Tagged “best-practices”
1 post.
How to write a clear prompt for an AI coding tool
Write the goal first, then the stack it has to fit into, then the constraints it must respect, then how you will know it worked, and ask for one change small enough that you can check it. That order matters because the model has no view of your project beyond what you give it and what it can read: if you leave out the framework, the data shape or the expected error behaviour, it fills the gap with an assumption, and as Builder.io puts it, generic prompts produce generic code. Everything else in prompt writing is a refinement of those four parts: replacing vague adjectives with numbers, giving one worked example when the task is unusual, breaking a big ask into sequential steps, and moving the facts you repeat every time out of the prompt and into a rules or memory file where the tool reads them automatically.