Skip to lesson
Exit
Values & Why Cursor1 / 2

1 min lesson

Have an opinion on the core surfaces

Use "Have an opinion on the core surfaces" to explain each part and the role it plays.

Step 1 of 2

Have an opinion on the core surfacesWhat a daily driver notices about each

The surfaces to form a view on
Tab
Inline autocomplete. Where does it carry repetitive edits and where does it lose the thread on a cross-file change?
Composer / Agent
Multi-step, multi-file work. When does an early wrong step compound and how much do you review before accepting?
Chat
Ask-about-the-code and scoped edits. When do you reach for it instead of Agent and where does context get thin?
Rules
Project conventions you encode so the model stops repeating a mistake. What rule did you write because you got tired of reverting something?

A specific friction on one surface beats a polished tour of all four.

Learn more

Advanced table

Generic enthusiasm versus a real user

Generic enthusiasm versus a real user

Sounds like prep
“Cursor makes me so much faster.”
Sounds like a daily driver
“Tab carries my repetitive edits, but on a cross-file rename it loses the thread, so I drop to Agent and read the diff before I accept.”
Sounds like prep
“The Agent is really powerful.”
Sounds like a daily driver
“Agent nailed a four-file change last week, then confidently broke an import path. I caught it on review and added a rule so it stops.”
Sounds like prep
“I'd want to research what users love.”
Sounds like a daily driver
“I'd research the trust moment: the first time the AI edits code a user can't fully see, half of them freeze. That hesitation is where adoption lives or dies.”

The right column cannot be written without real usage and a researcher's eye.

Learn more

Optional practice

Practice: Have an opinion on the core surfaces

QWhy does the authenticity read carry so much weight for a User Researcher specifically and what does a passing answer sound like?