RAG Project Remember — Store to Project Knowledge Graph
Store project-specific knowledge — architecture decisions, conventions, dependencies, and requirements — into the project-level LightRAG graph.
Formatting rules
Format each entry as:
[TYPE] Title — YYYY-MM-DD
What: Brief description
Why: The reasoning or constraint behind it
Files: Relevant file paths (if applicable)
Entry types
| Type |
Use for |
ARCHITECTURE |
System design choices, component structure, data flow |
CONVENTION |
Coding standards, naming patterns, file organization rules |
DECISION |
Technology choices, library selections, approach decisions |
DEPENDENCY |
External services, APIs, packages, version constraints |
CONFIG |
Environment setup, build config, deployment settings |
REQUIREMENT |
Business rules, constraints, acceptance criteria |
INSIGHT |
Performance findings, gotchas, non-obvious behaviors |
How to store
node -e "
const BASE = 'http://YOUR_LIGHTRAG_HOST:YOUR_PROJECT_PORT';
const API_KEY = process.env.LIGHTRAG_API_KEY || 'YOUR_API_KEY';
(async () => {
const res = await fetch(BASE + '/documents/text', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-API-Key': API_KEY
},
body: JSON.stringify({
file_source: '[TYPE] Title — YYYY-MM-DD',
text: 'Full content here with What/Why/Files structure'
})
});
console.log('Status:', res.status);
})();
"
After inserting
- Confirm to the user: "Stored to project memory: [TYPE] Title"
- Do NOT dump the raw API response
When NOT to use this
Use /rag-remember (personal graph) instead for:
- User preferences — working style, tool preferences, communication style
- Cross-project knowledge — things that apply to all projects
- Personal context — roles, responsibilities, machine config
- People info — contacts, working relationships
This skill is for things specific to the current project that wouldn't be relevant elsewhere.
Infrastructure
- Server:
YOUR_LIGHTRAG_HOST:YOUR_PROJECT_PORT
- Auth: X-API-Key header (auth-enabled mode)
- Env var:
LIGHTRAG_API_KEY
1---2name: rag-project-remember3description: Store project-specific knowledge into the project-level LightRAG knowledge graph4---56# RAG Project Remember — Store to Project Knowledge Graph78Store project-specific knowledge — architecture decisions, conventions, dependencies, and requirements — into the project-level LightRAG graph.910## Formatting rules1112Format each entry as:1314```15[TYPE] Title — YYYY-MM-DD1617What: Brief description18Why: The reasoning or constraint behind it19Files: Relevant file paths (if applicable)20```2122### Entry types2324| Type | Use for |25|------|---------|26| `ARCHITECTURE` | System design choices, component structure, data flow |27| `CONVENTION` | Coding standards, naming patterns, file organization rules |28| `DECISION` | Technology choices, library selections, approach decisions |29| `DEPENDENCY` | External services, APIs, packages, version constraints |30| `CONFIG` | Environment setup, build config, deployment settings |31| `REQUIREMENT` | Business rules, constraints, acceptance criteria |32| `INSIGHT` | Performance findings, gotchas, non-obvious behaviors |3334## How to store3536```bash37node -e "38const BASE = 'http://YOUR_LIGHTRAG_HOST:YOUR_PROJECT_PORT';39const API_KEY = process.env.LIGHTRAG_API_KEY || 'YOUR_API_KEY';40(async () => {41 const res = await fetch(BASE + '/documents/text', {42 method: 'POST',43 headers: {44 'Content-Type': 'application/json',45 'X-API-Key': API_KEY46 },47 body: JSON.stringify({48 file_source: '[TYPE] Title — YYYY-MM-DD',49 text: 'Full content here with What/Why/Files structure'50 })51 });52 console.log('Status:', res.status);53})();54"55```5657## After inserting5859- Confirm to the user: "Stored to project memory: [TYPE] Title"60- Do NOT dump the raw API response6162## When NOT to use this6364Use `/rag-remember` (personal graph) instead for:65- **User preferences** — working style, tool preferences, communication style66- **Cross-project knowledge** — things that apply to all projects67- **Personal context** — roles, responsibilities, machine config68- **People info** — contacts, working relationships6970This skill is for things **specific to the current project** that wouldn't be relevant elsewhere.7172## Infrastructure7374- **Server**: `YOUR_LIGHTRAG_HOST:YOUR_PROJECT_PORT`75- **Auth**: X-API-Key header (auth-enabled mode)76- **Env var**: `LIGHTRAG_API_KEY`