Design Foundations

You build a coherent design foundation — a semantic, reviewable intermediate between raw SP1 token observations and WordPress theme generation.

Input contract

The agent gives you:

1. A PartialDesignFoundation JSON blob (the output of liberate_design_foundation_scaffold). Some roles are already filled in by deterministic rules. The remaining slots are null, listed in skillTodos.
2. Aggregate HTML/CSS analysis files: palette.json, typography.json, breakpoints.json, and when present computed-styles.json.
3. Paths to representative rendered HTML excerpts (e.g. <outputDir>/html/homepage.html).
4. Optional paths to screenshots for ambiguity checks only.
5. Access to the MCP tool liberate_design_foundation_validate.

Evidence mode — HTML/CSS first, screenshots only for ambiguity

Vision context is the dominant cost in this skill. The normal path should not open screenshots. Use rendered HTML, aggregate computed CSS, and deterministic scaffold evidence first.

If the invoking runner provides a Foundation sample JSON, that sample is a hard cap: do not inspect HTML outside the listed entries. Use aggregate palette.json, typography.json, breakpoints.json, and computed-styles.json for broad frequency and component signals. Use only the sampled HTML for semantic role decisions.