Fix: Cursor Ignores Your Code and Gives Generic Answers
Quick Answer
Use @file to explicitly include files in your prompt. Example: "@src/lib/db.ts create a new function that queries the users table". Cursor only reads files you mention or have open in the editor.
Quick Fix Summary
| Issue | Not reading my files |
| Fastest fix | Use @file for specific files |
| Use this page if | Cursor gives generic answers that don't match your codebase |
Symptoms
- !Cursor gives generic answers that don't match your codebase
- !AI suggests code that conflicts with your existing patterns
- !Cursor says 'I don't have access to that file'
- !Generated code uses wrong import paths or function names
Step-by-Step Fix
Use @file for specific files
Type @ in the chat and select the file you want Cursor to read. This is the most reliable way to give context. Example: @src/app/page.tsx @src/lib/db.ts 'add a loading state to the homepage'
Use @codebase for full context
Type @codebase to let Cursor scan your entire project. This is slower but gives the AI a complete picture. Best for architectural questions.
Create .cursorrules
Create a .cursorrules file in your project root with instructions like: 'This is a Next.js 14 app using TypeScript, Tailwind CSS, and Supabase. Always use server components unless client interactivity is needed.'
Keep relevant files open
Cursor reads files that are open in your editor tabs. Open the 3-5 most relevant files before asking a question.
Frequently Asked Questions
Reading every file in a large project would exceed the context window instantly. Cursor is selective — you need to tell it which files matter for your current task.
Your tech stack, coding conventions, file structure patterns, and any project-specific rules. Think of it as onboarding instructions for a new developer.
Related
Weekly Signals
Get the next fix, switch, or warning before it hits your build.
Join builders getting the community signals, fix patterns, and tool shifts that matter before they show up everywhere else.
Follow the signals →