Writing good tasks
How to describe a change so the plan is right the first time.
Say what "done" looks like
Good: The login form shows "Please enter your email" under the field when it is empty, and the button stays disabled.
Too vague: Fix the login.
Name the place if you know it
In src/pages/Checkout.jsx, under the order total... helps CodeStilt read the right files and keeps the plan small.
Start small
One feature or fix per task. Small tasks are cheaper, easier to review and easier to undo.
Mention tests
Add a test for the empty email case. A task is only marked done when the tests pass.
Put repeated instructions in rules
If you keep saying use TypeScript, add it once to your rules instead.
Examples
| Instead of | Try |
|---|---|
| Make it faster | The products page loads all 2,000 products at once. Load 24 at a time with a Load more button. |
| Add dark mode | Add a dark mode toggle to the header. Save the choice in localStorage. Use the colours in theme.css. |
| Fix the bug | Orders over $1,000 show the wrong tax. The test in tax.test.js shows it. Make that test pass. |