2 min lesson
Navigating a frozen, unfamiliar codebase
Make the call in this situation: "You're given a frozen Cursor codebase you've never seen. What's the most impactful thing to find before building and why?" Explain what supports it.
Step 1 of 3
You'll be dropped into a frozen snapshot of Cursor's own codebase - large, real and entirely unfamiliar. The question the founders ask afterward is blunt: can they go end-to-end in the codebase?
This is where authentic daily use of Cursor pays off and prep-cramming shows. Someone who lives in the tool reaches for codebase search, symbol jumps and an agent to explain a module by reflex. Someone who skimmed docs the night before reads files top to bottom and stalls.
Learn more
Full explanation
Questions to answer in the spike
Questions to answer in the spike
- Entry point
- How does a user trigger work like mine today? (command palette, keybinding, panel)
- Data flow
- Where does the relevant state live and how does it get to the UI?
- AI plumbing
- If I need a model call, what's the existing path for prompt → response → applied edit?
- Reuse
- Which component or helper already does 80% of what I need?
- Render
- How does the editor surface a diff or suggestion I can borrow?