# EP07 Website Draft

## Goal

Make progressive disclosure visible instead of abstract.

## Hero

**A skill should reveal just enough to finish the task.**

## Page Structure

1. skill loading model
2. frontmatter / body / references comparison
3. progressive disclosure experiment
4. anti-patterns
5. minimal skill template
6. official links

## Interactive Blocks

### 1. Skill Load Ladder

Show the reader three stages:

- always loaded frontmatter
- task-relevant body
- on-demand references

### 2. Disclosure Comparison

Compare:

- frontmatter
- skill body
- references

Each row should answer:

- when it loads
- what it should contain
- what it should not contain
- what goes wrong if it is too large

### 3. Skill Size Experiment

Let the reader compare a concise skill to an overgrown one and see which version is easier to reuse.

## Minimum Viable UX

- editorial, card-based layout
- clear hierarchy
- small but meaningful motion
- readable on mobile

## Teaching Rules

- Keep the skill centered on one recurring task class.
- Every disclosure step must have a reason.
- Every example must be reusable, not decorative.

## Official Links

- skills and plugins
- memory
- context window and compaction

## Exit Outcome

The reader should know how to design a skill that stays short, usable, and safe to load.