Skip to content
Skills Library
Programming · Writing

component-migration-analysis

/component-migration-analysis

Create rendering-and-styling migration analysis docs for gen2 component migration. Use when on the "analyze rendering and styling" step for one or more components.

Author
adobe ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Create rendering-and-styling migration analysis docs for gen2 component migration. Use when on the "analyze rendering and styling" step for one or more components.

Triggers from the description

analyze rendering and styling
Original author description

Create rendering-and-styling migration analysis docs for gen2 component migration. Use when on the "analyze rendering and styling" step for one or more components.

How it works

  1. Mindset
  2. When to use this skill
  3. How to invoke
  4. Quick reference
  5. Full instructions
Original SKILL.md headings · 48 lines, 366 words
SKILL.md preview
---
name: component-migration-analysis
description: Create rendering-and-styling migration analysis docs for gen2 component migration. Use when on the "analyze rendering and styling" step for one or more components.
---

# Component migration: analyze rendering and styling

Create comprehensive migration documentation for the **analyze rendering and styling** step of gen2 component migration. One markdown file per component, following a fixed structure (specs, comparison, summary, resources).

## Mindset

You are a code archaeologist. Read existing code without judgment — your job is to document what _is_ before imagining what _should be_. Curiosity about past decisions leads to better future ones.

## When to use this skill

- You are on the "analyze rendering and styling" step of the gen2 component migration workstream
- The user asks to create rendering-and-styling migration analysis for one or more components
- The user asks to analyze rendering and styling for a component (e.g. "analyze rendering and styling for button", "create migration analysis for dialog")

## How to invoke

- Say "create migration analysis for [component]", "analyze rendering and styling for [component]", or "rendering and styling migration for [component]"
- Or refer to the step "analyze rendering and styling" in the gen2 component migration workstream — the agent should use this skill and read the full prompt

## Quick reference

### Output

- **One markdown file per component** at:
  `CONTRIBUTOR-DOCS/03_project-planning/03_components/[component-name]/rendering-and-styling-migration-analysis.md`
- **Structure**: Component specifications (CSS from spectrum-css `spectrum-two` metadata.json; SWC from spectrum-web-components `main` render/slots) → Comparison (DOM structure changes: SWC + CSS main + CSS spectrum-two; CSS⇒SWC mapping table) → Summary of changes → Resources

### Sources and branches

- **CSS specs**: spectrum-css repo, `spectrum-two` branch → `components/[component-name]/metadata.json` (selectors, passthroughs, modifiers)
- **SWC specs**: spectrum-web-components repo, `main` branch → `packages/[component-name]/src/[component-name].ts` (render(), @property, slots)
- **DOM comparison**: SWC render() (main); spectrum-css `main` and `spectrum-two` → `components/[component-name]/stories/template.js` (line-by-line; verify branch after each checkout)

### Important

- Create all files on the **original spectrum-web-components branch** where the session started
- Verify git branch before analyzing any file; perform line-by-line comparisons (don’t assume templates are identical)
- Ask clarifying questions for uncertain mappings instead of guessing

## Full instructions

For the exact document structure, heading levels, collapsible sections, CSS⇒SWC mapping table format (columns, status values, ordering), DOM comparison format, and output format notes, read:

**.ai/skills/component-migration-analysis/references/migration-analysis-prompt.md**

That document is the single source of truth for file organization, component documentation structure, comparison format, summary sections, and resources placeholder.
Files in this package (2)
  • SKILL.md 3 KB
  • references/migration-analysis-prompt.md 15 KB

Versions

The database has no other skills named component-migration-analysis.

Database snapshot: 13.11.2026 · package version e936df469068 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100accessibility-migration-analysis
    Create accessibility migration analysis docs for gen2 component migration. Use when on the "analyze accessibility" step for one or more components.
  • 100migration-styling
    Phase 5 of 1st-gen to gen2 component migration. Use to migrate CSS to the gen2 structure, apply Spectrum 2 tokens, and ensure stylelint passes.
  • 100verify-v8-v9-migration-docs
    Generate, audit, and verify Fluent UI v8-to-v9 component migration guides. Use when asked to inventory v8 components, inspect their v8 and v9 source, produce missing per-component documentation, prove the guides are accurate or exhaustive with sealed migrations, classify…
  • 100react-component
    Use when writing or editing a React component. Covers preferred patterns for functional components, prop types, and styling.
  • 90project-analysis-react
    Use for deep React analysis: component tree, state flow, props flow, hooks usage, rendering behavior, and React-specific failure patterns.
  • 100react-patterns
    React + TypeScript component and hook standards. TRIGGER when: creating components, custom hooks, or reviewing React code. SKIP: visual styling and theme tokens (use mui-styling); global store design (use state-management).

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.