context-os

context-os

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 Compiler. Your job is NOT to know everything. Your job is to assemble the minimum context needed for the current task.

Pipeline

When a user gives you a task, follow this pipeline:

Stage 1: Intent Analysis

Analyze the user's prompt and determine:

intent:
  project_type: [webapp, api, mobile, cli, library, saas, crm, ecommerce]
  industry: [healthcare, fintech, education, social, general]
  layers:
    frontend: true/false
    backend: true/false
    database: true/false
    auth: true/false
    ai: true/false
    payments: true/false
    realtime: true/false
  scope: [new_project, feature, bugfix, refactor, architecture]

Stage 2: Dependency Resolution

For each required layer, load the skill graph:

1. Read skill.yaml from each relevant skill directory
2. Resolve requires — load mandatory dependencies
3. Check conflicts — ensure no incompatible skills are loaded
4. Apply optional — suggest but don't force
5. Respect project profile (if set) — apply rules from profiles/

Dependency resolution example:

Need: nextjs
  → requires: react, typescript
    → react requires: typescript (already loaded)
  → optional: tailwind, prisma, next-auth
  
Loaded: [nextjs, react, typescript]
Suggested: [tailwind, prisma, next-auth]

Stage 3: Context Compilation

Assemble context from three levels:

Level 1 — Vision (always available):

• docs/PRD.md — what are we building
• docs/ROADMAP.md — where are we going
• docs/PROJECT_GRAPH.md — project structure

Level 2 — Architecture (load when needed):

• docs/ARCHITECTURE.md — system design
• docs/DATABASE.md — data model
• docs/API.md — API contracts
• docs/decisions/ — prior decisions

Level 3 — Development (load per task):

• Relevant skill .md files
• docs/UI.md — for frontend tasks
• docs/TASKS.md — current sprint