What problem does it solve?
During component migrations, code drifts from style guides, migration plans go stale, and shared-resource documentation silently falls out of sync. This Skill runs a structured three-part self-audit so these inconsistencies are caught before a migration phase is declared complete.
Core Features & Use Cases
- Code Conformance Check: Runs linters (yarn lint, yarn lint:css, prettier) and applies the code-conformance checklist to changed files.
- Plan Validity Check: Verifies the implementation matches the migration plan, updates phase checklists, moves settled questions to the Decision log, and scans for cascading inconsistencies across plan sections.
- Shared Resources Check: Ensures new or newly consumed controllers, mixins, and utilities in @adobe/spectrum-wc-core or sibling shared-utils locations are recorded in the shared-resources doc.
- Use Case: After finishing the styling phase of a component migration, run the pass to confirm CSS follows conventions, the plan's Phase 5 checklist is updated, and any new shared mixin is documented.
Quick Start
Ask the assistant to run a consistency and validity pass on the files changed in this migration phase before marking it complete.