1 min lesson
Keyboard-first and command surfaces
Use "Designing these patterns keeps a human in command of their own code" to say what you would do next.
Step 1 of 2
Keyboard-first and command surfacesthe primary interaction model for power users
Developers live on the keyboard. A command palette is often the main entry point to functionality, not a fallback. Design it as a primary surface: fast fuzzy matching, discoverable shortcuts shown inline and a flow that never forces a reach for the mouse.
Every AI-native pattern reduces to one question: does the user stay in control? Legible diffs, instant dismissal, visible tool calls, a real stop button. Designing these patterns keeps a human in command of their own code.
Asked how you'd improve an AI editing flow, anchor on trust and control rather than aesthetics: "My first move is making reject as fast and clean as accept, because the failure mode for AI features is users not trusting them enough to invite them in." That framing shows you understand what makes these products work.
Learn more
Optional practice
Test yourself on Keyboard-first and command surfaces
QYou're asked how you'd improve Cursor's inline-diff accept/reject flow. What principle should anchor your answer?