lore-framework

# Lore Framework

Manage lore/ directory for tracking tasks, code history, and project state. Use this skill when working with `lore/` directory content.

## First-Time Installation

If `lore/` directory doesn't exist, see [INSTALL.md](INSTALL.md) for setup instructions.

Quick: Ask Claude to "bootstrap lore" after loading this skill.

**Language:** All documentation must be in English.

**Style:** Be concise. No ASCII art boxes. Use blockquotes (`>`) for status notes. Short sentences.

## Session Requirements

**Before any work:**
1. Check `lore/0-session/current-user.md` exists (who is working)
2. Check `lore/0-session/current-task.md` exists (active task)

| File | Purpose | Committed |
|------|---------|-----------|
| `0-session/current-user.md` | Local identity (auto-generated) | No |
| `0-session/current-task.md` | Symlink to active task | No |
| `0-session/next-tasks.md` | Actionable tasks (auto-generated) | No |
| `0-session/team.yaml` | Team data (source of truth) | Yes |

**Automatic setup:** Configure `LORE_SESSION_CURRENT_USER` in `.claude/settings.local.json`:
```json
{ "env": { "LORE_SESSION_CURRENT_USER": "your-id" } }
```

**Manual setup via MCP tools:**
- User: `lore-framework_set-user` tool with user_id parameter
- Task: `lore-framework_set-task` tool with task_id parameter
- Show: `lore-framework_show-session` tool
- List users: `lore-framework_list-users` tool

**Why:** Code is ephemeral; tasks + worklogs provide AI-readable history for future sessions.

See [reference/workflow.md](reference/workflow.md) for full rules.

## Which Note Type? (Decision Tree)

**Ask yourself what you're doing:**

| If you're thinking... | Create | Example |
|-----------------------|--------|---------|
| "How should we solve X?" | **Q-** (Question) | Q-how-should-tenant-isolation-work.md |
| "What if we did Y?" | **I-** (Idea) | I-use-crm-for-access-control.md |
| "I found that Z does..." | **R-** (Research) | R-postgres-rls-patterns.md |
| "We should do X because Y"