// Sub-task after Phase 6 of 1st-gen to 2nd-gen component migration. Use to verify all migrated files conform to the project style guides, run linters, and surface any guideline gaps as PR comment notes.
| name | migration-conformance |
| description | Sub-task after Phase 6 of 1st-gen to 2nd-gen component migration. Use to verify all migrated files conform to the project style guides, run linters, and surface any guideline gaps as PR comment notes. |
A code-style conformance pass that runs after Phase 6 (testing) and before Phase 7 (documentation). The goal is to verify that all migrated files conform to the project style guides, that all linters pass, and that any guideline gaps are documented for the team.
The per-domain review criteria live in the code-conformance rule (.ai/rules/code-conformance.md). Read and apply that rule as the authoritative checklist for each file type. This skill provides the migration-specific sequencing, scoping, and quality gate.
You are a style guide enforcer, not a feature reviewer. Automated linting catches formatting and rule violations; reading the style guide catches structural and convention issues that linters cannot see. Work through each domain in order and fix violations as you find them — do not batch them for the end.
When the code is correct and appropriate but the guideline does not cover it, surface it to the user rather than silently accepting it or changing the guideline yourself.
yarn lint directly insteadScope the Prettier check to the component under review. Use the standard lint commands from the code-conformance rule.
# ESLint
yarn lint
# Stylelint
yarn lint:css
# Prettier — scoped to the migrated component
yarn prettier --check "2nd-gen/packages/**/components/[component]/**"
yarn prettier --write "2nd-gen/packages/**/components/[component]/**"
Resolve every error before moving to the manual review.
Read .ai/rules/code-conformance.md now and apply it to the files below.
That rule is the authoritative source for what to check in each domain and which style guide documents to read. Do not skip directly to the checklist — read the referenced guide sections for each domain before reviewing the files.
Files in scope for this component:
| Domain | Files |
|---|---|
| TypeScript | 2nd-gen/packages/core/components/[component]/[Component].base.ts |
2nd-gen/packages/core/components/[component]/[Component].types.ts | |
2nd-gen/packages/swc/components/[component]/[Component].ts | |
| Any mixins, controllers, or directives added for this component | |
| CSS | 2nd-gen/packages/swc/components/[component]/[component].css |
| Tests | 2nd-gen/packages/swc/components/[component]/[component].test.ts |
2nd-gen/packages/swc/components/[component]/[component].a11y.spec.ts | |
| Play functions within the stories file | |
| Stories | 2nd-gen/packages/swc/components/[component]/stories/[component].stories.ts |
Follow the guideline-gap pattern in the code-conformance rule. Report findings to the user as a proposed PR comment; do not block the conformance pass on them.
Before marking conformance complete, confirm:
yarn lint passes with no errorsyarn lint:css passes with no errorsUse when creating a per-component migration guide for application developers upgrading from Spectrum 1 Web Components to Spectrum 2 components.
Phase 7 of 1st-gen to 2nd-gen component migration. Use to write JSDoc, Storybook stories, and usage docs so the component is usable and understandable by others.
Phase 5 of 1st-gen to 2nd-gen component migration. Use to migrate CSS to the 2nd-gen structure, apply Spectrum 2 tokens, and ensure stylelint passes.
Phase 2 of 1st-gen to 2nd-gen component migration. Use to create the 2nd-gen file and folder structure, wire up exports, and confirm the build passes before implementation begins.
Phase 4 of 1st-gen to 2nd-gen component migration. Use to implement WCAG-aligned semantics, ARIA, keyboard support, and focus management, and document accessibility behavior.
Phase 8 of 1st-gen to 2nd-gen component migration. Use to run final checks, verify lint/tests/build/Storybook, update the workstream status table, and open a PR.