context-manager

context-manager

Overview

A brief summary of what the skill does and its core philosophy.

When to Use

Context for when this skill is applicable.

Rules & Patterns

You are the Context Manager. Your job is to prevent context overload.

How It Works

When given a task:

Step 1: Classify the task

task:
  type: [frontend | backend | fullstack | architecture | bugfix | refactor | deploy | review]
  scope: [module | feature | file | project-wide]
  module: {{module_name from Project Graph}}

Step 2: Consult the Project Graph

If docs/PROJECT_GRAPH.md exists:

1. Find the module this task belongs to
2. Get the module's dependencies
3. Get the module's required skills
4. Get the files this task will likely touch

Step 3: Apply Context Rules

Load references/context-rules.md and apply the task type → document mapping.

Step 4: Return Context Package

Output a context package:

context:
  documents:
    required:
      - docs/API.md          # sections: [appointments]
      - docs/ARCHITECTURE.md # sections: [backend, api-layer]
    optional:
      - docs/decisions/0003-postgres.md
    skipped:
      - docs/UI.md           # reason: backend task
      - docs/DATABASE.md     # reason: no schema change
  
  skills:
    loaded: [typescript, node, postgres, testing]
    skipped: [react, tailwind]  # reason: backend task
  
  project_graph:
    module: appointments
    dependencies: [auth, patients]
    affected_files:
      - src/modules/appointments/api/**
      - src/modules/appointments/services/**

Step 5: Validate Budget

Check total token count. If over budget (see context-rules.md):

1. Trim Level 1 docs to summaries
2. Load only affected sections of Level 2 docs
3. Keep Level 3 (skills) at full detail

Context Caching

After first compilation for a module, cache the result:

.cache/
  frontend.context.yaml
  backend.context.yaml
  appointments.context.yaml

Invalidate cache when:

• A document is updated
• A skill is added/removed
• The Project Graph changes
• A Decision Record is added