Ctx Tree

Effect

As a project grows, a single resume file becomes bloated and hard to navigate. Split it into a parent ctx + sub-contexts tree structure, balancing high-level overview with theme-specific depth.

When to Use

• Your project resume exceeds 200 lines
• A single project has 3+ independent themes (UI, infra, AI, etc.)
• Multiple people or Agents work on different themes in parallel

How It Works

1. Add a Sub Contexts table to the parent ctx

## Sub Contexts

| Theme | File |
|-------|------|
| Cards system | project/cards.md |
| LLM readability | project/llm-readability.md |
| i18n | project/i18n.md |

2. Sub-context structure

Each sub-ctx is a standalone resume file with a reference back to the parent.

# Cards System — Sub ctx

**Parent ctx**: project_resume.md
**Last updated**: 2026-03-30

## Overview (purpose of this theme)
## Done
## TODO
## Notes

3. When to use which

Action	Target
Get the big picture	Parent ctx
Dive into a theme	Sub-ctx
Session start	Parent ctx → relevant sub-ctx
Task completion	Update sub-ctx → add 1 line to parent Timeline

Combinations

Card	Synergy
Ctx	Foundation. Tree extends Ctx
Ctx Branch	Links sub-contexts to Git branches
Ship	Records sub-ctx completion during shipping

---

“An eye for the whole, and an eye for the detail. Without both, you can’t build anything large.” — Eris

Want to use this card permanently? Convert it directly into a SKILL.md — Effect → Overview, When to Use → Trigger, How It Works → Steps.