RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Configs/Cursor rules/magdazelena/primer

Cursor rule

.cursor/rules/memory.mdc
Cursor rules

Quality

61/100

Scores the file, not the repository.

Length

336 words

11 headings · 2 code blocks

Repository

3

— · pushed 158 days ago

Last changed

3 days ago

First indexed 3 days ago.
magdazelena/primer/.cursor/rules/memory.mdcRawGitHub
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 

Sections

  • 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

What it covers

code-styleperformancedo-notagent-behaviour

Stack — with the evidence

node

(1.00)

nextjs

(1.00)

turborepo

(1.00)

react

(0.70)

tailwind

(0.70)

jest

(0.70)

cypress

(0.70)

eslint

(0.70)

typescript

(0.60)

javascript

(0.60)

monorepo

(0.60)

github-actions

(0.60)

Format

Cursor rules

The most expressive format here. Many small .mdc files, each with frontmatter declaring when it should load, so a rule about migrations only enters context when a migration is open. Costs the most to maintain and only one editor reads it.

What the corpus says about it

Repository

Owner
magdazelena
Language
—
License
—
Archived
no

All configs in this repo

Also in magdazelena/primer

Diff this repo’s formats

One repository carrying more than one format is the comparison this product exists for: does anyone actually write different content in each file, or is one a copy of the other?

The other instruction files in this repository
RepositoryFormatStackCoversScoreChanged
magdazelena/primer.cursor/rules/agents.mdc · 3Cursor rulesnodenextjs+10no sections48/1003 days ago
magdazelena/primer.cursor/rules/code-quality.mdc · 3Cursor rulesnodenextjs+10lint-formatstyletypesperformance+273/1003 days ago
magdazelena/primer.cursor/rules/monorepo-management.mdc · 3Cursor rulesnodenextjs+10buildtestlint-formatstyle+579/1003 days ago
magdazelena/primer.cursor/rules/nextjs-frontend.mdc · 3Cursor rulesnodenextjs+10teststylearchapi+172/1003 days ago
magdazelena/primer.cursor/rules/project-structure.mdc · 3Cursor rulesnodenextjs+10testlint-formatarchmonorepo71/1003 days ago
magdazelena/primer.cursor/rules/strapi-backend.mdc · 3Cursor rulesnodenextjs+10stylearchtypesdatabase68/1003 days ago
magdazelena/primer.cursor/rules/strapi-plugin-development.mdc · 3Cursor rulesnodenextjs+10buildtestarchagent-behaviour85/1003 days ago
magdazelena/primer.cursor/rules/testing-conventions.mdc · 3Cursor rulesnodenextjs+10teststyletesting-strategyapi+173/1003 days ago
magdazelena/primer.cursor/rules/typescript-conventions.mdc · 3Cursor rulesnodenextjs+10lint-formatstyletypesdo-not65/1003 days ago
Diff against .cursor/rules/agents.mdc Diff against .cursor/rules/code-quality.mdc Diff against .cursor/rules/monorepo-management.mdc Diff against .cursor/rules/nextjs-frontend.mdc Diff against .cursor/rules/project-structure.mdc Diff against .cursor/rules/strapi-backend.mdc Diff against .cursor/rules/strapi-plugin-development.mdc Diff against .cursor/rules/testing-conventions.mdc Diff against .cursor/rules/typescript-conventions.mdc

Similar configs

Same format, overlapping stack, ranked by quality.

Same format, overlapping stack, ranked by quality
RepositoryFormatStackCoversScoreChanged
TechSquidTV/Hermes.cursor/rules/10-hermes-api.mdc · 45Cursor rulestypescriptpytest+15testlint-formatstylearch+5100/1003 days ago
hiromaily/go-crypto-wallet.cursor/rules/typescript.mdc · 126Cursor rulesgobun+5setupbuildtestlint-format+6100/1003 days ago
markstev/mark-starter.cursor/rules/frontend.mdc · 0Cursor rulestypescriptturborepo+14setuptestlint-formatstyle+699/1003 days ago
deifos/clipmira-subtitles.cursor/rules/frontend.mdc · 1Cursor rulestypescriptnextjs+5setuptestlint-formatstyle+799/1003 days ago
dodgecfr/combatfilms-webapp.cursor/rules/frontend.mdc · 0Cursor rulestypescriptturborepo+15setuptestlint-formatstyle+799/1003 days ago
Allymahmoud/case-intake-platform.cursor/rules/frontend.mdc · 0Cursor rulestypescriptturborepo+13setuptestlint-formatstyle+799/1003 days ago
langflow-ai/langflow.cursor/rules/docs_development.mdc · 153kCursor rulespythonnode+16setupbuildtestlint-format+797/1003 days ago
TechSquidTV/Hermes.cursor/rules/20-hermes-api-tests.mdc · 45Cursor rulestypescriptpytest+15teststyletesting-strategysecurity+397/1003 days ago
RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack