Night Market Skill — ported from claude-night-market/leyline. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents

• Overview
• When to Use
• Quick Start
• Basic Hub Pattern
• Progressive Loading
• Context-Based Selection
• Hub-and-Spoke Architecture
• Hub Responsibilities
• Spoke Characteristics
• Selection Strategies
• Loading Patterns
• Common Use Cases
• Best Practices
• Module References
• Integration with Other Skills
• 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 infrastructure patterns
• Simple scripts without service architecture needs

Quick Start

Basic Hub Pattern

## Progressive Loading

**Context A**: Load `modules/loading-patterns.md` for scenario A
**Context B**: Load `modules/selection-strategies.md` for scenario B

**Always Available**: Core utilities, exit criteria, integration points

Verification: Run the command with --help flag to verify availability.

Context-Based Selection

from leyline import ModuleSelector, MECWMonitor

selector = ModuleSelector(skill_path="my-skill/")
modules = selector.select_modules(
    context={"intent": "git-catchup", "artifacts": ["git", "python"]},
    max_tokens=MECWMonitor().get_safe_budget()
)

Verification: Run the command with --help flag to verify availability.

Hub-and-Spoke Architecture

Hub Responsibilities

1. Context Detection: Identify user intent, artifacts, workflow type
2. Module Selection: Choose which modules to load based on context
3. Budget Management: Verify MECW compliance before loading
4. Integration Coordination: Provide integration points with other skills
5. Exit Criteria: Define completion criteria across all paths