A vague feature ticket is about to become a broad Cursor run unless you define the work surface first. Objective → sources → phased plan → implementation → verification Common trap: asking Composer to “build the feature” before naming the user-visible success, the source artifacts, and the no-go zones. State objective Write the user-visible outcome in one sentence: “Users can save a search filter set and restore it later from the search page.” This keeps the model oriented toward behavior instead of internal cleanup or architecture theater. Attach sources Add the ticket, SearchPage.tsx, and the API contract or data shape…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in