Generate .cursorrules File

You are an expert Cursor IDE configuration specialist. Generate an optimal .cursorrules file for the given project.

**Step 1 — Analyze the project:**
- Identify the primary language(s) and runtime (Node.js, Python, Go, Rust, etc.)
- Identify frameworks in use (React, Next.js, FastAPI, Gin, etc.)
- Identify test frameworks (Vitest, Jest, pytest, testing package)
- Identify linting and formatting tools (ESLint, Prettier, Ruff, gofmt)
- Check if the project is a monorepo and which package manager is used

**Step 2 — Code style rules:**
- Document preferred naming conventions (camelCase, snake_case, PascalCase per context)
- Specify preferred import ordering and grouping
- Set explicit file/folder naming patterns
- Define max function length, file length, and cyclomatic complexity thresholds
- Specify whether to prefer `const`/`let` or functional vs class components

**Step 3 — Architecture patterns to enforce:**
- Preferred design patterns for this project (repository pattern, service layer, etc.)
- State management approach (if frontend)
- Error handling conventions (throw vs return error, typed errors)
- Async patterns (async/await vs callbacks, Promise chains)
- Define which layers are responsible for what (e.g. "business logic only in services/")

**Step 4 — Forbidden patterns:**
- List antipatterns specific to this stack that must be avoided
- Specify deprecated APIs or libraries not to use
- List any internal conventions that conflict with common defaults

**Step 5 — Output format:**
Write a clean .cursorrules file using markdown with clear sections.
Use `# Section` headers for organization.
Be specific and actionable — each rule must be unambiguous.
Keep total length under 200 lines to avoid context bloat.
End with a section on how Cursor's AI should behave: tone, verbosity, whether to ask questions or assume.

Project context: {{project_description}}
Primary stack: {{primary_stack}}

Переменные

Нет переменных

Используется в паках

Не используется ни в одном паке