component-mapper-design
Agent: UX/UI Designer
L2 UX/UI designer (Nx) responsible for user flow design, wireframing, prototyping, and component mapping.
Department ethos: ideal-design.md
Skill Description
Maps product requirements and design deliverables to existing design system components, identifying coverage gaps that require new components, variants, or token updates.
When to Use
- When a new feature design is underway and the designer needs to determine which existing components to reuse versus what must be created.
- When the design system is being audited for coverage against current product surfaces.
- When a wireframe or visual design introduces interaction patterns that may already exist in the component library under a different name.
- When engineering flags inconsistent component usage across screens and requests a canonical mapping.
Workflow
- Inventory requirements: Extract every UI element, pattern, and interaction from the design brief or wireframes. Classify each element by atomic level (atom, molecule, organism, template) using the atomic design framework. Deliverable: UI element inventory with atomic classification.
- Map to existing components: For each element, search the design system library for an existing match. Apply the semantic matching rules in the atomic design framework — verify role, interaction behaviour, and state availability, not just visual similarity. Record exact component name, variant, and coverage status. Deliverable: component mapping table.
- Identify gaps: Flag elements with no existing component match, partial matches requiring new variants, or missing token coverage. Use the severity classification in the atomic design framework to tag each gap as blocking or non-blocking. Deliverable: gap register with severity.
- Propose gap resolution: Apply the gap resolution decision tree in the atomic design framework to recommend the appropriate path for each gap. Estimate effort per resolution using the framework's effort table. Deliverable: gap resolution plan.
- Align with system owners: Review the gap resolution plan with the design system maintainer to confirm feasibility, naming conventions, and timeline. Deliverable: approved resolution plan with assignments.
Anti-Patterns
- Detaching and customizing: Detaching a Figma component instance to make local modifications instead of requesting a proper variant. Why: detached instances do not receive library updates, creating visual drift and multiplying maintenance effort across every file that copied the hack.
- Name-blind mapping: Mapping by visual similarity alone without verifying semantic meaning and interaction behavior. Why: two elements may look identical but serve different purposes (e.g., a card vs. a selectable list item), leading to incorrect ARIA roles and broken accessibility.
- Ignoring token coverage: Mapping components without checking that the required colour, spacing, and typography tokens exist for the target context (dark mode, compact density). Why: missing tokens force hard-coded values that break when themes or density settings change.
Output
On success: Produces a component mapping table linking every UI element to a design system component (or gap entry), a gap register with resolution recommendations, and an approved plan for new components or variants. Delivered to the designer, design system maintainer, and engineering lead.
On failure: Report which requirements could not be mapped (missing design system documentation, inaccessible Figma library, undefined interaction states), what partial mapping was achieved, and what access or documentation is needed.
Related Skills
wireframe-builder -- Wireframes are a primary input for component mapping; mapping should happen before visual design begins.
accessibility-checker-design -- Component mapping must verify that accessibility attributes (ARIA roles, focus behavior) are baked into system components.
design-implementer-review -- Implementation reviews verify that the mapped components were used correctly in code.
1---2name: component-mapper-design3description: This skill maps product requirements to design system components and identifies gaps requiring new components or variants. Use when asked to audit component coverage for a feature, identify design system gaps, or plan component work for a new surface. Also consider when a designer is building custom elements that may already exist in the system. Suggest when a wireframe introduces patterns not present in the component library.4---56# component-mapper-design78## Agent: UX/UI Designer910L2 UX/UI designer (Nx) responsible for user flow design, wireframing, prototyping, and component mapping.1112Department ethos: [ideal-design.md](../../../../departments/design/ideal-design.md)1314## Skill Description1516Maps product requirements and design deliverables to existing design system components, identifying coverage gaps that require new components, variants, or token updates.1718## When to Use1920- When a new feature design is underway and the designer needs to determine which existing components to reuse versus what must be created.21- When the design system is being audited for coverage against current product surfaces.22- When a wireframe or visual design introduces interaction patterns that may already exist in the component library under a different name.23- When engineering flags inconsistent component usage across screens and requests a canonical mapping.2425## Workflow26271. **Inventory requirements**: Extract every UI element, pattern, and interaction from the design brief or wireframes. Classify each element by atomic level (atom, molecule, organism, template) using the [atomic design framework](references/atomic-design-framework.md). Deliverable: UI element inventory with atomic classification.282. **Map to existing components**: For each element, search the design system library for an existing match. Apply the semantic matching rules in the [atomic design framework](references/atomic-design-framework.md) — verify role, interaction behaviour, and state availability, not just visual similarity. Record exact component name, variant, and coverage status. Deliverable: component mapping table.293. **Identify gaps**: Flag elements with no existing component match, partial matches requiring new variants, or missing token coverage. Use the severity classification in the [atomic design framework](references/atomic-design-framework.md) to tag each gap as blocking or non-blocking. Deliverable: gap register with severity.304. **Propose gap resolution**: Apply the gap resolution decision tree in the [atomic design framework](references/atomic-design-framework.md) to recommend the appropriate path for each gap. Estimate effort per resolution using the framework's effort table. Deliverable: gap resolution plan.315. **Align with system owners**: Review the gap resolution plan with the design system maintainer to confirm feasibility, naming conventions, and timeline. Deliverable: approved resolution plan with assignments.3233## Anti-Patterns3435- **Detaching and customizing**: Detaching a Figma component instance to make local modifications instead of requesting a proper variant. *Why*: detached instances do not receive library updates, creating visual drift and multiplying maintenance effort across every file that copied the hack.36- **Name-blind mapping**: Mapping by visual similarity alone without verifying semantic meaning and interaction behavior. *Why*: two elements may look identical but serve different purposes (e.g., a card vs. a selectable list item), leading to incorrect ARIA roles and broken accessibility.37- **Ignoring token coverage**: Mapping components without checking that the required colour, spacing, and typography tokens exist for the target context (dark mode, compact density). *Why*: missing tokens force hard-coded values that break when themes or density settings change.3839## Output4041**On success**: Produces a component mapping table linking every UI element to a design system component (or gap entry), a gap register with resolution recommendations, and an approved plan for new components or variants. Delivered to the designer, design system maintainer, and engineering lead.4243**On failure**: Report which requirements could not be mapped (missing design system documentation, inaccessible Figma library, undefined interaction states), what partial mapping was achieved, and what access or documentation is needed.4445## Related Skills4647- [`wireframe-builder`](../wireframe-builder/SKILL.md) -- Wireframes are a primary input for component mapping; mapping should happen before visual design begins.48- [`accessibility-checker-design`](../../../design/head-of-design/accessibility-checker-design/SKILL.md) -- Component mapping must verify that accessibility attributes (ARIA roles, focus behavior) are baked into system components.49- [`design-implementer-review`](../design-implementer-review/SKILL.md) -- Implementation reviews verify that the mapped components were used correctly in code.