Resources
Thought Leaders
Aakash Gupta
Colin Matthews
Lenny Rachitsky
Paweł Huryn
Dan Olsen
Marty Cagan
Melissa Perri
Shreyas Doshi
Gibson Biddle
Interview Preparation
Bookmarks
AI Workflows
Stanislav Beliaev CTO of GetFluently.App
How to make Cursor 10x more useful with this one system 👇
At Fluently (AI English Coach → https://getfluently.app) we use Cursor to streamline our development process.
By following these proven practices, you can ship features in hours, not days.
→ Before using Cursor:
• Ask Claude (or ChatGPT) to create a clear, detailed plan in markdown • Have the AI ask clarifying questions, critique its own plan, and regenerate if needed • Save this plan as “instructions. md” for easy reference during development. • Use ChatGPT to add an extra planning layer before coding by another AI, reducing errors and complexity.
→ Workflow and incremental development:
Break work into small, manageable tasks or feature increments.
Use an Edit-Test loop: 1. Write a failing test case first (TDD approach). 2. Instruct AI to write code to pass the test. 3. Run the test. 4. If it fails, AI analyzes failure and fixes code. 5. Repeat until tests pass.
Review AI-generated changes after tests pass. Encourage AI to explain its chain of thought in prompts.
→ Debugging
• If stuck, ask Cursor to generate a detailed report of all files and their roles, including errors. • Use ChatGPT or Claude to analyze the report and suggest fixes. • Use tools like gitingest.com to collect all scripts, configs, and relevant files in a single page for easier AI ingestion. • Refer to the latest documentation via context7.com for up-to-date info.
→ Cursor-specific tips
• Use CursorRules to set broad project rules (always in AI context). Search Cursor Directory for examples. • Typical rule: Write tests → write code → run tests → update code until tests pass. • Use /Reference open editors to quickly add files to AI context. • Use cursorignore to exclude irrelevant files. • Keep context short by explicitly adding files via @. Longer context can confuse AI. • Start new chats when the context becomes too long. • Resync or reindex code frequently to keep AI up to date. • Notepads are useful for frequently used prompts.
→ Version control and file management
• Use Git often to commit changes regularly. • Avoid large sets of uncommitted changes. • Creating files and folders (e.g., touch, mkdir) is always acceptable. • Running tests (Vitest, PM test, NR test, build, tsc) is always allowed.
→ Optional settings and modes
Enable YOLO mode to have AI write tests automatically.
Use a system prompt in “Rules for AI” in Cursor settings: • Keep answers concise and direct. • Suggest alternative solutions. • Avoid unnecessary explanations. • Prioritize technical details over generic advice.
References
How To Get The Most Out Of Vibe Coding, Y Combinator Startup School
All about pivoting, Y Combinator Startup School