Project Context & Persistent Memory — Guided Starter Kit
Model: ANY Task: SETUP
~1788 tokens
Summary
Supply LLMs with a stable, concise, and up-to-date representation of your project so prompts can build on a persistent context (dependencies, file layout, rules, goals).
Refined Core
Build and maintain small, versioned project artifacts that the model reads as persistent context — prompts then become lightweight commands because the model already knows your constraints, style, and history.
Advice Highlights
- Store decision rationale, architecture notes, and pattern files as separate versioned documents so the model can reference why prior choices were made.
- Keep a short set of persistent files per project (WHO_I_AM.md, WHAT_IM_DOING.md, CONTEXT.md, STYLE_GUIDE.md, NEXT_SESSION.md) and have the model read them before any coding request.
- When editing code, include explicit file-path context and small related file groups rather than entire repo dumps.
- Keep a change/error history (memlog) that the model must check or update before making edits; require the agent to verify and update this memlog before proceeding.
Fill Variables
Template Preview
project-memorycontext-filesllm-workflowguided-template