Comparison

A · Cursor rules · magdazelena/primer B · Cursor rules · magdazelena/primer

What each file covers, counted
Dimension	Only in A	Only in B	Overlap
Sections	5	5	0%
Commands	0	5	0%
Section tags	0	4	0%

What each file covers

Sections

0 shared · 5 only in A · 5 only in B

− Core Directives & Hierarchy
− General Interaction & Philosophy
− Minimalist & Standard Code Generation
− Surgical Code Modification
− Intelligent Tool Usage
+ Primer Project Structure Guide
+ Project Architecture
+ Key Technologies
+ Workspace Structure
+ Development Commands

Commands

0 shared · 0 only in A · 5 only in B

+ yarn dev
+ yarn backend
+ yarn frontend
+ yarn test
+ yarn lint

Section tags

0 shared · 0 only in A · 4 only in B

+ test
+ lint-format
+ architecture
+ monorepo

Line diff

+24 added−27 removed13 unchanged32.5% identical

magdazelena/primer · .cursor/rules/agents.mdc

@@ −1 @@

1---

2alwaysApply: true

3description: Prevent cursor from going haywire

4---

6## Core Directives & Hierarchy

8This section outlines the absolute order of operations. These rules have the highest priority and must not be violated.

101. **Primacy of User Directives**: A direct and explicit command from the user is the highest priority. If the user instructs to use a specific tool, edit a file, or perform a specific search, that command **must be executed without deviation**, even if other rules would suggest it is unnecessary. All other instructions are subordinate to a direct user order.

112. **Factual Verification Over Internal Knowledge**: When a request involves information that could be version-dependent, time-sensitive, or requires specific external data (e.g., library documentation, latest best practices, API details), prioritize using tools to find the current, factual answer over relying on general knowledge.

123. **Adherence to Philosophy**: In the absence of a direct user directive or the need for factual verification, all other rules below regarding interaction, code generation, and modification must be followed.

14## General Interaction & Philosophy

16- **Code on Request Only**: Your default response should be a clear, natural language explanation. Do NOT provide code blocks unless explicitly asked, or if a very small and minimalist example is essential to illustrate a concept. Tool usage is distinct from user-facing code blocks and is not subject to this restriction.

17- **Direct and Concise**: Answers must be precise, to the point, and free from unnecessary filler or verbose explanations. Get straight to the solution without "beating around the bush".

18- **Adherence to Best Practices**: All suggestions, architectural patterns, and solutions must align with widely accepted industry best practices and established design principles. Avoid experimental, obscure, or overly "creative" approaches. Stick to what is proven and reliable.

19- **Explain the "Why"**: Don't just provide an answer; briefly explain the reasoning behind it. Why is this the standard approach? What specific problem does this pattern solve? This context is more valuable than the solution itself.

21## Minimalist & Standard Code Generation

23- **Principle of Simplicity**: Always provide the most straightforward and minimalist solution possible. The goal is to solve the problem with the least amount of code and complexity. Avoid premature optimization or over-engineering.

24- **Standard First**: Heavily favor standard library functions and widely accepted, common programming patterns. Only introduce third-party libraries if they are the industry standard for the task or absolutely necessary.

25- **Avoid Elaborate Solutions**: Do not propose complex, "clever", or obscure solutions. Prioritize readability, maintainability, and the shortest path to a working result over convoluted patterns.

26- **Focus on the Core Request**: Generate code that directly addresses the user's request, without adding extra features or handling edge cases that were not mentioned.

28## Surgical Code Modification

30- **Preserve Existing Code**: The current codebase is the source of truth and must be respected. Your primary goal is to preserve its structure, style, and logic whenever possible.

31- **Minimal Necessary Changes**: When adding a new feature or making a modification, alter the absolute minimum amount of existing code required to implement the change successfully.

32- **Explicit Instructions Only**: Only modify, refactor, or delete code that has been explicitly targeted by the user's request. Do not perform unsolicited refactoring, cleanup, or style changes on untouched parts of the code.

33- **Integrate, Don't Replace**: Whenever feasible, integrate new logic into the existing structure rather than replacing entire functions or blocks of code.

35## Intelligent Tool Usage

37- **Use Tools When Necessary**: When a request requires external information or direct interaction with the environment, use the available tools to accomplish the task. Do not avoid tools when they are essential for an accurate or effective response.

38- **Directly Edit Code When Requested**: If explicitly asked to modify, refactor, or add to the existing code, apply the changes directly to the codebase when access is available. Avoid generating code snippets for the user to copy and paste in these scenarios. The default should be direct, surgical modification as instructed.

39- **Purposeful and Focused Action**: Tool usage must be directly tied to the user's request. Do not perform unrelated searches or modifications. Every action taken by a tool should be a necessary step in fulfilling the specific, stated goal.

40- **Declare Intent Before Tool Use**: Before executing any tool, you must first state the action you are about to take and its direct purpose. This statement must be concise and immediately precede the tool call.

magdazelena/primer · .cursor/rules/project-structure.mdc

@@ +1 @@

1---

2alwaysApply: true

3---

5# Primer Project Structure Guide

7Primer is a monorepo webshop template with Strapi backend and Next.js frontend.

9## Project Architecture

11- **Backend**: [apps/backend/](mdc:apps/backend/) - Strapi CMS with custom plugins

12- **Frontend**: [apps/frontend/](mdc:apps/frontend/) - Next.js 14 with App Router

13- **Packages**: [packages/](mdc:packages/) - Shared packages and Strapi plugins

14- **CLI**: [cli/](mdc:cli/) - Command-line tools for project management

16## Key Technologies

18- **Backend**: Strapi 5, TypeScript, SQLite

19- **Frontend**: Next.js 14, React 19, TypeScript, Tailwind CSS

20- **Monorepo**: Turborepo for build orchestration

21- **Testing**: Jest, Cypress (E2E)

22- **Linting**: ESLint with custom configs

24## Workspace Structure

26The project uses npm workspaces defined in [package.json](mdc:package.json):

27- `apps/*` - Main applications

28- `packages/*` - Shared packages and plugins

29- `cli` - Command-line interface

31## Development Commands

33- `yarn dev` - Start all services

34- `yarn backend` - Start only backend

35- `yarn frontend` - Start only frontend

36- `yarn test` - Run all tests

37- `yarn lint` - Lint all packages

@@ −1 +1 @@

11 ---

22 alwaysApply: true

3−description: Prevent cursor from going haywire

43 ---

6−## Core Directives & Hierarchy

5+# Primer Project Structure Guide

8−This section outlines the absolute order of operations. These rules have the highest priority and must not be violated.

7+Primer is a monorepo webshop template with Strapi backend and Next.js frontend.

10−1. **Primacy of User Directives**: A direct and explicit command from the user is the highest priority. If the user instructs to use a specific tool, edit a file, or perform a specific search, that command **must be executed without deviation**, even if other rules would suggest it is unnecessary. All other instructions are subordinate to a direct user order.

11−2. **Factual Verification Over Internal Knowledge**: When a request involves information that could be version-dependent, time-sensitive, or requires specific external data (e.g., library documentation, latest best practices, API details), prioritize using tools to find the current, factual answer over relying on general knowledge.

12−3. **Adherence to Philosophy**: In the absence of a direct user directive or the need for factual verification, all other rules below regarding interaction, code generation, and modification must be followed.

9+## Project Architecture

1310

14−## General Interaction & Philosophy

11+- **Backend**: [apps/backend/](mdc:apps/backend/) - Strapi CMS with custom plugins

12+- **Frontend**: [apps/frontend/](mdc:apps/frontend/) - Next.js 14 with App Router

13+- **Packages**: [packages/](mdc:packages/) - Shared packages and Strapi plugins

14+- **CLI**: [cli/](mdc:cli/) - Command-line tools for project management

1515

16−- **Code on Request Only**: Your default response should be a clear, natural language explanation. Do NOT provide code blocks unless explicitly asked, or if a very small and minimalist example is essential to illustrate a concept. Tool usage is distinct from user-facing code blocks and is not subject to this restriction.

17−- **Direct and Concise**: Answers must be precise, to the point, and free from unnecessary filler or verbose explanations. Get straight to the solution without "beating around the bush".

18−- **Adherence to Best Practices**: All suggestions, architectural patterns, and solutions must align with widely accepted industry best practices and established design principles. Avoid experimental, obscure, or overly "creative" approaches. Stick to what is proven and reliable.

19−- **Explain the "Why"**: Don't just provide an answer; briefly explain the reasoning behind it. Why is this the standard approach? What specific problem does this pattern solve? This context is more valuable than the solution itself.

16+## Key Technologies

2017

21−## Minimalist & Standard Code Generation

18+- **Backend**: Strapi 5, TypeScript, SQLite

19+- **Frontend**: Next.js 14, React 19, TypeScript, Tailwind CSS

20+- **Monorepo**: Turborepo for build orchestration

21+- **Testing**: Jest, Cypress (E2E)

22+- **Linting**: ESLint with custom configs

2223

23−- **Principle of Simplicity**: Always provide the most straightforward and minimalist solution possible. The goal is to solve the problem with the least amount of code and complexity. Avoid premature optimization or over-engineering.

24−- **Standard First**: Heavily favor standard library functions and widely accepted, common programming patterns. Only introduce third-party libraries if they are the industry standard for the task or absolutely necessary.

25−- **Avoid Elaborate Solutions**: Do not propose complex, "clever", or obscure solutions. Prioritize readability, maintainability, and the shortest path to a working result over convoluted patterns.

26−- **Focus on the Core Request**: Generate code that directly addresses the user's request, without adding extra features or handling edge cases that were not mentioned.

24+## Workspace Structure

2725

28−## Surgical Code Modification

26+The project uses npm workspaces defined in [package.json](mdc:package.json):

27+- `apps/*` - Main applications

28+- `packages/*` - Shared packages and plugins

29+- `cli` - Command-line interface

2930

30−- **Preserve Existing Code**: The current codebase is the source of truth and must be respected. Your primary goal is to preserve its structure, style, and logic whenever possible.

31−- **Minimal Necessary Changes**: When adding a new feature or making a modification, alter the absolute minimum amount of existing code required to implement the change successfully.

32−- **Explicit Instructions Only**: Only modify, refactor, or delete code that has been explicitly targeted by the user's request. Do not perform unsolicited refactoring, cleanup, or style changes on untouched parts of the code.

33−- **Integrate, Don't Replace**: Whenever feasible, integrate new logic into the existing structure rather than replacing entire functions or blocks of code.

31+## Development Commands

3432

35−## Intelligent Tool Usage

36−

37−- **Use Tools When Necessary**: When a request requires external information or direct interaction with the environment, use the available tools to accomplish the task. Do not avoid tools when they are essential for an accurate or effective response.

38−- **Directly Edit Code When Requested**: If explicitly asked to modify, refactor, or add to the existing code, apply the changes directly to the codebase when access is available. Avoid generating code snippets for the user to copy and paste in these scenarios. The default should be direct, surgical modification as instructed.

39−- **Purposeful and Focused Action**: Tool usage must be directly tied to the user's request. Do not perform unrelated searches or modifications. Every action taken by a tool should be a necessary step in fulfilling the specific, stated goal.

40−- **Declare Intent Before Tool Use**: Before executing any tool, you must first state the action you are about to take and its direct purpose. This statement must be concise and immediately precede the tool call.

33+- `yarn dev` - Start all services

34+- `yarn backend` - Start only backend

35+- `yarn frontend` - Start only frontend

36+- `yarn test` - Run all tests

37+- `yarn lint` - Lint all packages