Cursor rule

1---
2description: Workflow memory operating loop — read root state before acting, write state back after meaningful change
3globs:
4alwaysApply: true
5---
6 
7# Workflow Memory
8 
9This repository keeps agent memory in root markdown files. Follow this loop every session.
10 
11## Session Start
12 
131. Read `workflow_state.md` — current phase, plan, blockers, log.
142. Read `project_config.md` — goals, stack, patterns, constraints.
153. Reconstruct the next action from those files before proposing or making changes.
16 
17## Loop
18 
19One phase at a time: `ANALYZE → PREPARE → IMPLEMENT → VALIDATE`.
20 
21- ANALYZE: inspect relevant files and current state before deciding.
22- PREPARE: short plan; identify the checks `project_config.md` requires.
23- IMPLEMENT: smallest coherent edits that satisfy the task.
24- VALIDATE: run the checks appropriate for the repo; report what could not run.
25- ROLLBACK: only when the approach must be abandoned and state preserved.
26 
27## State Writes
28 
29Update `workflow_state.md` only after meaningful change: a phase transition, a completed task, a blocker, or a validation result that changes the next action. No per-message summaries. Preserve headings, keep entries concise.
30 
31Update `project_config.md` only for durable changes: goals, stack, patterns, constraints, changelog. No live task notes there.
32 
33Never store secrets, tokens, or credentials in memory files. Record only where they load from (env vars, secret manager).
34 
35## Exit
36 
37When work is complete, report result, changed files, and validation status. No post-completion questions, no optional next-step prompts. Wait for the next user message.
38