What problem does it solve?
Designing reusable HTML components without a structured review process leads to weak primitive boundaries, bloated APIs, missing opt-outs, and unexpected bundle cost. This Skill provides a repeatable checklist for evaluating component design proposals before they ship.
Core Features & Use Cases
- Boundary and Ownership Review: Traces data flow across core logic, DOM behavior, and the element, checking lifecycle and cleanup.
- API and Anatomy Audit: Evaluates light-DOM anatomy, element and CSS APIs, and flags complex selectors like
:has() as signs of weak primitive boundaries.
- Opt-Out and Bundle Verification: Exercises omission, replacement, styling, behavior, and registration opt-outs while weighing API complexity against bundle cost and tree-shaking.
- Use Case: When reviewing a proposal for a new chapter-menu element in a media player UI, use this Skill to produce prioritized findings on boundaries, accessibility, lifecycle, and bundle impact.
Quick Start
Ask the assistant to review your HTML component design proposal using the review-html-component-design skill and report findings by severity.