v0.6.0 – System Explore

Explore a project design system before adopting it

System Explore compares new or explicitly requested replacement project identities on representative content. Start with broad visual directions or a focused palette or typography question, without needing an existing layout.

• Preserve settled choices while comparing the next question, such as quieter secondary accents or a different type hierarchy.
• Review candidates in one HTML document at wide and phone widths, in light and dark modes.
• Keep artifact themes separate from project identity. Existing identities can be documented with teach; one-artifact comparisons still use Artifact Explore.
• Approve a complete system before reviewing the full DESIGN.md, PRODUCT.md, and tokens.css drafts. File writes require separate confirmation. Replacement preserves private backups and stops for manual repair after a partial failure.

Try: “Explore a design system for this project. Start with four directions; I don't have a layout yet.”

See the System Explore procedure and skill README.

Verification and scope

Fresh Codex agents exercised broad and focused comparisons, incumbent routing, artifact preservation, and confirmed adoption, including concurrent edits, backup collisions, and repair after an injected write failure. Local browser checks covered responsive rendering, theme precedence, contrast, and content preservation.

Acceptance used Codex and Chromium. Local font rendering depends on the host; remote font loading and other browsers were not qualified. The palette helper does not validate hex input, so those fixtures used rendered browser contrast checks. Strict Stitch validation was unavailable.

This release publishes the skill only. The website remains work in progress and is not deployed by this release.