Scoped Iteration Prompt

The principle of limiting each iterative Bolt prompt to a single concern. Multiple changes in one prompt multiply failure risk and make it impossible to identify which change caused a regression. One concern per prompt, verify, then continue.

Syntax

bolt-new

// WRONG — multiple concerns bundled:
Fix the styling, add sorting, and handle the error when title is empty.

// RIGHT — one concern per prompt:
Prompt 1: Add sorting to the task list.
  Sort by due date ascending by default.
  Dropdown to switch: Due Date / Priority / Created.

Prompt 2: Add title validation to the project form.
  Title is required. Show "Project title is required"
  below the field on empty submit.

Prompt 3: [Next concern after verifying #1 and #2]

Example

bolt-new

// After verifying the task list renders correctly:
Add sorting controls to the TaskList component.
Place a sort dropdown in the top-right of the list header.
Options: "Due Date (asc)", "Due Date (desc)", "Priority", "Created".
Default: Due Date ascending.
Sort is client-side — do not change the Supabase query.

// After verifying sort works:
Add an empty state to the TaskList.
If there are 0 tasks matching the current filters,
show: icon (CheckSquare from Lucide), heading "No tasks yet",
subtitle "Add a task to get started", and a primary button "Add Task".