| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 11 | 7 | 0% |
| Commands | 0 | 0 | 2 | 0% |
| Section tags | 1 | 3 | 3 | 14% |
What each file covers
Sections
0 shared · 11 only in A · 7 only in B- − AI Memory Rule
- − Purpose
- − Storage
- − Updating Memory
- − Using Memory
- − Example Scenario
- − Memory File (`.cursor/rules/learned-memories.mdc`)
- − Project Memory
- − User Preferences
- − Technical Decisions
- − Project Conventions
- + Strapi Backend Conventions
- + Project Structure
- + File Naming Conventions
- + Content Type Structure
- + Plugin Development
- + Configuration
- + Database
Commands
0 shared · 0 only in A · 2 only in B- + yarn seed
- + yarn export
Section tags
1 shared · 3 only in A · 3 only in B- − performance
- − do-not
- − agent-behaviour
- + architecture
- + types
- + database
- code-style
Line diff
magdazelena/primer · .cursor/rules/memory.mdc
@@ −1 @@
1---
2alwaysApply: true
3---
4# AI Memory Rule
5
6This rule defines how the AI should manage and utilize its "memory" regarding this specific project, including user preferences, learned facts, and project-specific conventions.
7
8## Purpose
9
10The AI's memory helps maintain consistency and adapt to specific project needs or user preferences discovered during interactions. It prevents the AI from repeatedly asking for the same information or making suggestions contrary to established patterns.
11
12## Storage
13
14All learned project-specific knowledge and preferences should be stored and referenced in the `learned-memories.mdc` file located in `.cursor/rules`.
15
16## Updating Memory
17
18When new information relevant to the project's conventions, user preferences, or specific technical details is learned (either explicitly told by the user or inferred through conversation), the AI should:
19
201. **Identify Key Information:** Determine the core piece of knowledge to be stored.
212. **Check Existing Memory:** Review `learned-memories.mdc` to see if this information contradicts or updates existing entries.
223. **Propose Update:** Suggest an edit to `learned-memories.mdc` to add or modify the relevant information. Keep entries concise and clear.
23
24## Using Memory
25
26Before proposing solutions, code changes, or answering questions, the AI should consult `learned-memories.mdc` to ensure its response aligns with the recorded knowledge and preferences.
27
28## Example Scenario
29
30**User:** "We've decided to use Tailwind v4 for this project, not v3."
31
32**AI Action:**
33
341. Recognize this as a project-specific technical decision.
352. Check `learned-memories.mdc` for existing Tailwind version information.
363. Propose adding or updating an entry in `learned-memories.mdc`:
37 ```markdown
38 ## Technical Decisions
39
40 * **CSS Framework:** Tailwind v4 is used. Ensure usage aligns with v4 documentation and practices, noting differences from v3.
41 ```
424. In subsequent interactions involving Tailwind, the AI will refer to this entry and consult v4 documentation if necessary.
43
44## Memory File (`.cursor/rules/learned-memories.mdc`)
45
46The basic structure:
47
48```markdown
49# Project Memory
50
51This file stores project-specific knowledge, conventions, and user preferences learned by the AI assistant.
52
53## User Preferences
54
55- [Preference 1]
56- [Preference 2]
57
58## Technical Decisions
59
60- [Decision 1]
61- [Decision 2]
62
63## Project Conventions
64
65- [Convention 1]
66- [Convention 2]
67```
68---
69alwaysApply: true
70---
71
magdazelena/primer · .cursor/rules/strapi-backend.mdc
@@ +1 @@
1---
2globs: apps/backend/**/*.ts,packages/strapi-plugin-*/**/*.ts
3---
4
5# Strapi Backend Conventions
6
7## Project Structure
8
9Follow Strapi's recommended structure in [apps/backend/src/](mdc:apps/backend/src/):
10
11- **API**: [apps/backend/src/api/](mdc:apps/backend/src/api/) - Content types and controllers
12- **Components**: [apps/backend/src/components/](mdc:apps/backend/src/components/) - Reusable components
13- **Extensions**: [apps/backend/src/extensions/](mdc:apps/backend/src/extensions/) - Strapi extensions
14- **Admin**: [apps/backend/src/admin/](mdc:apps/backend/src/admin/) - Admin panel customizations
15
16## File Naming Conventions
17
18- **Controllers**: `*.controller.ts`
19- **Services**: `*.service.ts`
20- **Content Types**: `*.json` (schema files)
21- **Policies**: `*.policy.ts`
22- **Middlewares**: `*.middleware.ts`
23
24## Content Type Structure
25
26Each content type should have:
27- `content-types/[name]/schema.json` - Schema definition
28- `content-types/[name]/lifecycles.ts` - Lifecycle hooks
29- `api/[name]/controllers/[name].controller.ts` - Controller
30- `api/[name]/services/[name].service.ts` - Service
31
32## Plugin Development
33
34For custom plugins in [packages/strapi-plugin-*/](mdc:packages/strapi-plugin-status-manager/):
35
36- **Server**: `server/src/` - Backend logic
37- **Admin**: `admin/src/` - Frontend components
38- **Package**: Follow `@primer/strapi-plugin-*` naming
39- **Exports**: Use proper package.json exports for Strapi 5
40
41## Configuration
42
43- Use TypeScript configs in [apps/backend/config/](mdc:apps/backend/config/)
44- Environment-specific configs in `config/env/`
45- Plugin configuration in [apps/backend/config/plugins.ts](mdc:apps/backend/config/plugins.ts)
46
47## Database
48
49- Use SQLite for development (better-sqlite3)
50- Migrations in [apps/backend/database/migrations/](mdc:apps/backend/database/migrations/)
51- Seed data management with `yarn seed` and `yarn export`
@@ −1 +1 @@
11 ---
2−alwaysApply: true
2+globs: apps/backend/**/*.ts,packages/strapi-plugin-*/**/*.ts
33 ---
4−# AI Memory Rule
54
6−This rule defines how the AI should manage and utilize its "memory" regarding this specific project, including user preferences, learned facts, and project-specific conventions.
5+# Strapi Backend Conventions
76
8−## Purpose
7+## Project Structure
98
10−The AI's memory helps maintain consistency and adapt to specific project needs or user preferences discovered during interactions. It prevents the AI from repeatedly asking for the same information or making suggestions contrary to established patterns.
9+Follow Strapi's recommended structure in [apps/backend/src/](mdc:apps/backend/src/):
1110
12−## Storage
11+- **API**: [apps/backend/src/api/](mdc:apps/backend/src/api/) - Content types and controllers
12+- **Components**: [apps/backend/src/components/](mdc:apps/backend/src/components/) - Reusable components
13+- **Extensions**: [apps/backend/src/extensions/](mdc:apps/backend/src/extensions/) - Strapi extensions
14+- **Admin**: [apps/backend/src/admin/](mdc:apps/backend/src/admin/) - Admin panel customizations
1315
14−All learned project-specific knowledge and preferences should be stored and referenced in the `learned-memories.mdc` file located in `.cursor/rules`.
16+## File Naming Conventions
1517
16−## Updating Memory
18+- **Controllers**: `*.controller.ts`
19+- **Services**: `*.service.ts`
20+- **Content Types**: `*.json` (schema files)
21+- **Policies**: `*.policy.ts`
22+- **Middlewares**: `*.middleware.ts`
1723
18−When new information relevant to the project's conventions, user preferences, or specific technical details is learned (either explicitly told by the user or inferred through conversation), the AI should:
24+## Content Type Structure
1925
20−1. **Identify Key Information:** Determine the core piece of knowledge to be stored.
21−2. **Check Existing Memory:** Review `learned-memories.mdc` to see if this information contradicts or updates existing entries.
22−3. **Propose Update:** Suggest an edit to `learned-memories.mdc` to add or modify the relevant information. Keep entries concise and clear.
26+Each content type should have:
27+- `content-types/[name]/schema.json` - Schema definition
28+- `content-types/[name]/lifecycles.ts` - Lifecycle hooks
29+- `api/[name]/controllers/[name].controller.ts` - Controller
30+- `api/[name]/services/[name].service.ts` - Service
2331
24−## Using Memory
32+## Plugin Development
2533
26−Before proposing solutions, code changes, or answering questions, the AI should consult `learned-memories.mdc` to ensure its response aligns with the recorded knowledge and preferences.
34+For custom plugins in [packages/strapi-plugin-*/](mdc:packages/strapi-plugin-status-manager/):
2735
28−## Example Scenario
36+- **Server**: `server/src/` - Backend logic
37+- **Admin**: `admin/src/` - Frontend components
38+- **Package**: Follow `@primer/strapi-plugin-*` naming
39+- **Exports**: Use proper package.json exports for Strapi 5
2940
30−**User:** "We've decided to use Tailwind v4 for this project, not v3."
41+## Configuration
3142
32−**AI Action:**
43+- Use TypeScript configs in [apps/backend/config/](mdc:apps/backend/config/)
44+- Environment-specific configs in `config/env/`
45+- Plugin configuration in [apps/backend/config/plugins.ts](mdc:apps/backend/config/plugins.ts)
3346
34−1. Recognize this as a project-specific technical decision.
35−2. Check `learned-memories.mdc` for existing Tailwind version information.
36−3. Propose adding or updating an entry in `learned-memories.mdc`:
37− ```markdown
38− ## Technical Decisions
47+## Database
3948
40− * **CSS Framework:** Tailwind v4 is used. Ensure usage aligns with v4 documentation and practices, noting differences from v3.
41− ```
42−4. In subsequent interactions involving Tailwind, the AI will refer to this entry and consult v4 documentation if necessary.
43−
44−## Memory File (`.cursor/rules/learned-memories.mdc`)
45−
46−The basic structure:
47−
48−```markdown
49−# Project Memory
50−
51−This file stores project-specific knowledge, conventions, and user preferences learned by the AI assistant.
52−
53−## User Preferences
54−
55−- [Preference 1]
56−- [Preference 2]
57−
58−## Technical Decisions
59−
60−- [Decision 1]
61−- [Decision 2]
62−
63−## Project Conventions
64−
65−- [Convention 1]
66−- [Convention 2]
67−```
68−---
69−alwaysApply: true
70−---
71−
49+- Use SQLite for development (better-sqlite3)
50+- Migrations in [apps/backend/database/migrations/](mdc:apps/backend/database/migrations/)
51+- Seed data management with `yarn seed` and `yarn export`
