memory

---

description: ALWAYS INCLUDE to HAVE Project Context. globs: alwaysApply: true

Memory Files Structure

This outlines the fundamental principles, required files, workflow structure, and essential procedures that govern documentation, and maintaining a memory using file system. The Memory Files consists of required core files and optional context files. Files build upon each other in a clear hierarchy:

flowchart TD
    PB[ [product_requirement_docs.md](mdc:docs/product_requirement_docs.md) ] --> PC[ [technical.md](mdc:docs/technical.md) ]
    PB --> SP[ [architecture.md](mdc:docs/architecture.md) ]

    SP --> TC[ [tasks_plan.md](mdc:tasks/tasks_plan.md) ]
    PC --> TC
    PB --> TC
    
    TC --> AC[ [active_context.md](mdc:tasks/active_context.md) ]

    AC --> ER[ [error-documentation.mdc](mdc:.cursor/rules/error-documentation.mdc)]
    AC --> LL[ [lessons-learned.mdc](mdc:.cursor/rules/lessons-learned.mdc) ]
    
    subgraph LIT[ @docs/literature ]
        L1[...]
        L2[...]
    end
    
    subgraph RFC[ @tasks/rfc/ ]
        R1[...]
        R2[...]
    end
    
    PC --o LIT
    TC --o RFC

Core Files (Required)

7 files:

1. product_requirement_docs.md (docs/product_requirement_docs.md): Product Requirement Document (PRD) for the project or an SOP.

• Why this project exists
• Problems it solves
• Defines core requirements and goals
• Foundation document that shapes all other files
• Source of truth for project scope
• Created at project start if it doesn't exist

1. architecture.md (docs/architecture.md): System architecture

• How it should work
• Component relationships
• Dependencies
• Work flow of the Solution
• Mermaid diagram of solution overview: each component and code flow

1. technical.md (docs/technical.md): Development environment and stack

• Technologies used
• Development setup
• Key technical decisions
• Design patterns in use
• Technical constraints