ai-context

name: ai-context description: | Project knowledge base for coding agents. Activate when: (1) starting a new session in this project, (2) encountering unfamiliar code patterns or architecture decisions, (3) user asks about project design or rationale, (4) before making significant structural changes. Contains tiered knowledge from stable design principles to dynamic issues.

AI Context — Cowork Forge

This skill provides pre-generated project knowledge to help you understand the project faster and work more effectively.

🎯 When to Activate This Skill

Activate immediately when:

• Starting a new coding session in this project
• You need to understand "why something is designed this way"
• User asks about project architecture, design decisions, or constraints

Refer to specific sections when:

• Encountering unexpected behavior or errors → DYNAMICS.md
• Planning structural changes → references/DECISIONS.md
• Need high-level overview → references/PROJECT-ESSENCE.md
• Need component relationships → references/ARCHITECTURE.md

Do NOT activate when:

• Simple code edits with clear context
• User requests are purely mechanical (rename, format, etc.)
• You already have sufficient context from recent conversation

📁 Knowledge Tiers

Reading Order (Recommended)

1. PROJECT-ESSENCE.md  ← Start here (1-2 min read)
2. ARCHITECTURE.md     ← If working across components
3. DECISIONS.md        ← If changing established patterns
4. DYNAMICS.md         ← If something feels wrong

🔧 How to Use This Knowledge

1. Session Start Protocol

□ Read PROJECT-ESSENCE.md (always)
□ Scan DYNAMICS.md for active issues
□ Read ARCHITECTURE.md if working across subprojects
□ Proceed with dynamic code exploration

2. Dynamic Code Exploration

• Use grep and file search to locate actual implementations
• Verify knowledge against current code state
• Update knowledge if you find drift

3. Decision Validation

Before changing established patterns:

□ Check DECISIONS.md for existing decisions
□ If decision exists: follow it or explicitly propose change
□ If new decision needed: document after implementation

🔄 When to Update

Update PROJECT-ESSENCE.md when:

• Project purpose or scope fundamentally changes
• New major capability is added

Update ARCHITECTURE.md when:

• New component/subproject added
• Component responsibilities shift
• Data flow changes significantly

Update DECISIONS.md when:

• A new design decision is made
• An existing decision is revisited/changed

Update DYNAMICS.md when:

• New issue discovered
• Issue resolved
• Workaround found

📚 File Reference

• Project Essence
• Architecture
• Decisions
• Dynamics
• Maintenance Guide

Generated by ai-context-generator on 2026-04-17