progressive-loading

## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Basic Hub Pattern](#basic-hub-pattern) - [Progressive Loading](#progressive-loading) - [Context-Based Selection](#context-based-selection) - [Hub-and-Spoke Architecture](#hub-and-spoke-architecture) - [Hub Responsibilities](#hub-responsibilities) - [Spoke Characteristics](#spoke-characteristics) - [Selection Strategies](#selection-strategies) - [Loading Patterns](#loading-patterns) - [Common Use Cases](#common-use-cases) - [Best Practices](#best-practices) - [Module References](#module-references) - [Integration with Other Skills](#integration-with-other-skills) - [Exit Criteria](#exit-criteria) # Progressive Loading Patterns ## Overview Progressive loading provides standardized patterns for building skills that load modules dynamically based on context, user intent, and available token budget. This prevents loading unnecessary content while ensuring required functionality is available when needed. The core principle: **Start minimal, expand intelligently, monitor continuously.** ## When To Use Use progressive loading when building skills that: - Cover multiple distinct workflows or domains - Need to manage context window efficiently - Have modules that are mutually exclusive based on context - Require MECW compliance for long-running sessions - Want to optimize for common paths while supporting edge cases ## When NOT To Use - Project doesn't use the leyline i...