Systematically analyze and fix bugs by examining error messages, stack traces, and related code paths.
I'm encountering this error: [paste error/stack trace] Analyze this systematically: 1. Parse the error message and identify the exact error type 2. Trace the stack to find the originating file and line 3. Identify the root cause (not just the symptom) 4. Check for common causes of this error type 5. Look at recent changes to related files that might have introduced this 6. Propose a fix with explanation of WHY it works 7. Suggest a test that would catch this regression 8. Check if similar patterns exist elsewhere that might have the same bug Do NOT just suppress the error. Fix the underlying cause. If the error is in a dependency, explain the workaround and link to relevant issues.
Generate optimized .cursorrules files tailored to your project's tech stack, conventions, and team preferences. Covers TypeScript, Python, Rust, Go, and more.
Leverage Cursor's Agent mode to build complete features end-to-end. Handles file creation, terminal commands, dependency installation, and multi-file edits in one flow.
Generate complete React components with TypeScript types, props interface, stories, and unit tests in one prompt.
Generate robust Next.js API routes with Zod validation, error handling, rate limiting, and TypeScript types.
Design database tables with proper types, constraints, indexes, and migration files for PostgreSQL/Supabase.
Generate FastAPI endpoints with Pydantic request/response models, dependency injection, and async database operations.