Exploring AI-Assisted Development with Cursor
An outline for working notes on using Cursor as an AI-assisted editor in day-to-day development.
2 min read
- cursor
- ai-assisted-development
- workflow
- developer-tools
Starter draft. This note is an outline. Sections marked Needs input are waiting for real experience and have not been written yet.
This is a starter draft. It sets out the questions I want to answer about working with an AI-assisted editor, and leaves each answer blank until I have real experience to write down.
Why this note exists
A short, honest framing of why I'm looking at AI-assisted development at all: what I hope it helps with, and what I'm wary of.
How I want to work with it
Before writing about results, it helps to be clear about the working agreement. A reusable shape for a request might look like this:
Context: [what the project is and what already exists]
Task: [one small, reviewable change]
Constraints: [tests that must pass, files that must not change]
This is a template, not a record of how I actually work. It is here to show how code blocks look in notes.
What worked
What didn't
Open questions
- How do I keep a clear line between code I understand and code I merely accepted?
- What belongs in a review checklist for AI-assisted changes?
- Where does it fit alongside tests, types and code review?