.cursorrules File (Project Rules for AI)

1. Concept Overview & Systemic Problem

When collaborating with artificial intelligence on a project, you will quickly notice its undesirable habits:

• It suddenly decides to install an outdated version of a library that has not been supported for three years.
• It writes code in JavaScript instead of strict TypeScript.
• It invents its own folder structure, breaking your site's architecture.

The .cursorrules file is the law of your project. It is a concise set of rules in plain text or Markdown format that you place once at the root of the project. Every time the AI attempts to write or modify any line of code, it is required to consult this file.

Key engineering principle: the simplest way to keep code clean and organized without daily tedious admonitions to the model.

2. Architectural Taxonomy & Mental Model

Here is a ready-to-use template that you can copy into your project right now:

# Technology Stack and Project Standards
- Language: TypeScript (strict mode strict: true)
- Framework: Next.js (App Router)
- Styles: Tailwind CSS (no inline styles or regular CSS)
- Database: Drizzle ORM + PostgreSQL / SQLite

# Rules for the Agent:
1. Always write complete file implementations. Never leave lazy comments like "// ... remaining code here".
2. All user texts and buttons must be in Ukrainian.
3. Before creating a new npm package, check if a similar one is already installed in package.json.
4. If you see an architectural error — first explain the risk, then suggest changes.

3. Four Things That Must Be Prohibited

1. Prohibition of Lazy Comments: The worst scenario is when the model erases the middle of your working code and writes // ... keep existing code. Explicitly prohibit this behavior.
2. Library Version Pinning: Specify, for example: "Use only Lucide-React for icons," to prevent the model from importing both FontAwesome and HeroIcons simultaneously.
3. Component Naming Rules: State: "Component names are written in PascalCase, utility names in camelCase."
4. Type Requirements: Prohibit the use of the any type in TypeScript.

4. Production Engineering Scenarios

01. Streamlined Code Generation

With .cursorrules, the model feels like an experienced developer on your team from the very first second, perfectly aware of corporate standards. You receive code that compiles on the first attempt without syntax conflicts!

02. Consistent Code Quality

By enforcing rules through the .cursorrules file, you ensure that all generated code adheres to the specified standards, reducing the need for extensive code reviews and corrections.

03. Enhanced Team Collaboration

The .cursorrules file acts as a shared reference point for all team members, ensuring that everyone is aligned on coding practices and project requirements, leading to smoother collaboration.

5. Pitfalls, Common Mistakes & Security

Be cautious of the following common pitfalls when implementing .cursorrules:

• Neglecting Updates: Regularly review and update the rules to reflect changes in project requirements or technology stacks.
• Overly Restrictive Rules: Avoid making rules too stringent, which may hinder the AI's ability to generate creative solutions.
• Ignoring Feedback Loops: Establish mechanisms for collecting feedback on the effectiveness of the rules and adjust them based on team input and AI performance.