What problem does it solve?
After migrating a component from 1st-gen to 2nd-gen in the Spectrum Web Components monorepo, teams need a structured way to confirm the migrated files follow project style guides and pass all automated linters before documentation work begins. This Skill provides that conformance pass with a defined scope, sequence, and quality gate.
Core Features & Use Cases
- Automated lint orchestration: Runs ESLint, Stylelint, and Prettier scoped to the migrated component and requires all errors to be resolved before manual review.
- Domain-by-domain manual review: Delegates per-file-type criteria (TypeScript, CSS, tests, stories) to the authoritative code-conformance skill and its referenced style guides.
- Guideline gap reporting: Surfaces cases where correct code is not covered by existing guidelines as proposed PR comments, without blocking the conformance pass.
- Use Case: After Phase 6 testing of a migrated button component passes, ask for a conformance check to run linters, review each file against the style guides, and produce a checklist confirming the migration is style-compliant.
Quick Start
Ask the assistant to run conformance checks for the migrated component, for example by saying "Check code conformance for the button component migration."