MCPInstall

version-migration

Migrate applications between IDS (Iress Design System) major versions — including v4→v5, v5→v6, and OUI→v6. Covers component renaming, prop changes, form architecture migration (Formik→React Hook Form), testing updates, and common gotchas. Use when the user asks about upgrading, migrating, or updating IDS versions, or mentions OUI, v4, v5, or v6 migration.

Installs
43
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/iress/design-system --skill version-migration
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads version-migration automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Skill: IDS Version Migration

When to Use

  • Migrating from IDS v5 (or v4) to IDS v6
  • Migrating from OUI (@iress/oui) to IDS v6
  • Updating imports from @iress/components-react to @iress-oss/ids-components
  • Converting Formik forms to React Hook Form via IressForm/IressFormField
  • Updating test files that use IDS v4 test utilities
  • Reviewing migration PRs for correctness

Decision Table: Which Migration Path?

Current stackMigration pathComplexityReference
OUI onlyOUI→v6 guideHigh (form architecture change)prop-renames.md
IDS v4 onlyv4→v6 guideMedium (form architecture change)prop-renames.md
IDS v5 onlyv5→v6 guideLow–Mediumv5-to-v6-migration.md
OUI + IDS v4Both OUI→v6 and v4→v6 guidesHigh (form architecture change)prop-renames.md
OUI + IDS v5OUI→v6 guide + v5→v6 for IDS changesHigh (form architecture change)v5-to-v6-migration.md

Full interactive guides with diff viewers are available in Storybook:


Pre-Migration Assessment

Before starting migration, run these scripts (or perform checks manually):

  1. Identify current version: scripts/detect-version.sh — detects IDS/OUI version and recommends migration path
  2. Audit component usage: scripts/audit-components.sh — generates component usage report
  3. Check for deprecated props: scripts/find-deprecated-props.sh — finds props that will break
  4. Check form architecture: scripts/find-formik.sh — identifies Formik forms needing migration
  5. Check test patterns: scripts/find-test-utils.sh — finds old test utilities
  6. Review custom CSS: Search for .oui-, .ids-, or iress- class selectors that may break
  7. Setup VRT (recommended): scripts/setup-playwright-vrt.sh — generates Playwright visual regression tests
  8. Capture baseline screenshots: Run VRT suite before migration to capture current state
  9. Create migration branch: Ensure you can rollback if needed

Quick Reference: Package Changes

Import path

// ❌ Old (IDS v4)
import { IressButton } from '@iress/components-react';

// ❌ Old (OUI)
import { Button, Input } from '@iress/oui';

// ✅ IDS v6 (install with @beta tag: npm install @iress-oss/ids-components@beta)
import { IressButton, IressInput } from '@iress-oss/ids-components';

Important: IDS v6 is currently in beta. Install with the @beta tag:

npm install @iress-oss/ids-components@beta
npm install @iress-oss/ids-tokens@beta  # if using tokens directly

CSS entry point

// ✅ Required in your app entry point
import '@iress-oss/ids-components/dist/style.css';

Token package

// ✅ Required for design tokens
import '@iress-oss/ids-tokens/build/css-vars.css';
import { cssVars } from '@iress-oss/ids-tokens';

Key Migration Areas

v5 → v6 Migration

For migrations specifically from IDS v5 to v6, see references/v5-to-v6-migration.md for:

  • Package and CSS import changes
  • Component renames (IressBadge → IressPill, IressFilter → IressDropdownMenu, etc.)
  • Prop changes by component (Button, Alert, Toggle, Field, Modal, Select)
  • Icon migration (FontAwesome → Material Symbols)
  • Form migration patterns

Component renames

Components that changed names between versions (IDS and OUI → v6), plus removed and new components. See references/component-renames.md for the full map.

Key renames: IressBadge → IressPill, IressRichSelect → IressSelect, IressField → IressFormField, IressFilter → IressDropdownMenu.

Prop renames (CRITICAL — verified against source code)

Using old prop names will silently fail. See references/prop-renames.md for the complete table.

Most common renames:

ComponentOld prop (OUI)New prop (v6)
Alertcontextstatus
ModalonHideonShowChange
Fieldset/RadioGrouplegendlabel
Labeloptionalrequired
Component (IDS v4/v5)Old propNew prop (v6)
IressButtonvariantmode
IressAlertvariantstatus
IressModalisOpenshow
IressModalonCloseonShowChange
IressModaltitleheading
IressPanelbackgroundbg
IressStack/IressInlineguttergap

Form migration (Formik → React Hook Form)

The most significant architectural change. Forms use IressForm + IressFormField with render prop, replacing Formik's <Field as={...}> pattern. Yup schemas become per-field rules props.

See references/form-migration.md for validation mapping, before/after examples, and common patterns.

Quick example:

<IressForm defaultValues={{ email: '' }} onSubmit={handle}>
  <IressFormField
    name="email"
    label="Email"
    render={(props) => <IressInput {...props} type="email" />}
    rules={{ required: 'Required' }}
  />
  <IressButton type="submit" mode="primary">
    Submit
  </IressButton>
</IressForm>

Testing migration

IDS v6 uses standard React Testing Library — no special test utilities. Replace idsFireEvent with fireEvent/userEvent, remove mockLazyLoadedComponents, prefer getByRole/getByLabelText over getByTestId.

See references/testing-migration.md for import changes, pattern mapping, config updates, and form test examples.

Styling migration

OUI CSS classes and IDS v4 Stencil classes are removed. Use styling props (p, m, bg, gap, scrollable) or design tokens (var(--iress-*)). Declare @layer order if custom CSS is overridden.

See references/styling-migration.md for examples and AG Grid migration.


Post-Migration Validation

After completing migration, run scripts/validate-migration.sh or verify manually:

  1. Automated checks: Run validation script to check for common issues
  2. Visual regression: Run VRT suite and review all visual diffs (see references/visual-regression-testing.md)
  3. Visual check: All components render without console errors or warnings
  4. Form functionality: Submit forms and verify validation rules work correctly
  5. Test suite: All tests pass with new testing patterns (no idsFireEvent, etc.)
  6. Accessibility: Keyboard navigation and screen reader functionality intact
  7. Styling: No missing styles, check responsive breakpoints
  8. Interactive states: Hover, focus, disabled, loading states work as expected
  9. Build: Production build completes without errors, check bundle size

The validation script checks for:

  • Old imports (@iress/oui, @iress/components-react)
  • Old test utils (idsFireEvent, mockLazyLoadedComponents)
  • Deprecated props (variant=, isOpen=, gutter=, etc.)
  • Required CSS import
  • Remaining Formik usage

Common Gotchas

See references/common-gotchas.md for a comprehensive troubleshooting guide covering:

  • Critical breaking changes (missing CSS, validation, renamed props)
  • IDS v4 React → v6 React gotchas (test utils, slots, helpers, icons)
  • OUI-specific gotchas (prop renames, removed components)
  • Component API changes (form fields, styling, composition patterns)
  • Form architecture changes (Formik → React Hook Form)

Cross-References

Generated migration guides (read these for full details)

  • v4→v5 — node_modules/@iress-oss/ids-components/.ai/guides/migration-guides-v5.md
  • v5→v6 — node_modules/@iress-oss/ids-components/.ai/guides/migration-guides-v6.md
  • OUI→v6 — node_modules/@iress-oss/ids-components/.ai/guides/migration-guides-oui.md

Component and pattern docs

  • Component docs — node_modules/@iress-oss/ids-components/.ai/components/
  • Pattern docs — node_modules/@iress-oss/ids-components/.ai/patterns/
  • Index — node_modules/@iress-oss/ids-components/.ai/index.json

Related skills

  • token-usage — Design token usage patterns
  • ui-translation — Building new IDS v6 UIs from scratch
  • ui-doctor — Auditing IDS compliance

Reference

FAQ

What does the version-migration skill do?

Migrate applications between IDS (Iress Design System) major versions — including v4→v5, v5→v6, and OUI→v6. Covers component renaming, prop changes, form architecture migration (Formik→React Hook Form), testing updates, and common gotchas. Use when the user asks about upgrading, migrating, or updating IDS versions, or mentions OUI, v4, v5, or v6 migration.

How do I install version-migration?

Run npx skills add https://github.com/iress/design-system --skill version-migration in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/version-migration/ (personal) or .claude/skills/version-migration/ (project).

Which AI agents can use version-migration?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is version-migration safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains version-migration?

It is published by iress in iress/design-system. It has 43 recorded installs.

More from iress/design-system

View all →

ui-doctor

iress/design-system

Audit and review application UI for IDS compliance, accessibility, usability, and cognitive load. Covers component usage validation, WCAG accessibility checks, cognitive load assessment, and UX quality evaluation. Use when asked to review UI, check accessibility, assess usability, audit IDS compliance, or when the user says "review this page", "check a11y", or "is this accessible?"

Frontend & Design1.2K installs

token-usage

iress/design-system

Open the skill to read its SKILL.md instructions.

ui-translation

iress/design-system

Translate natural language UI descriptions into IDS (Iress Design System) component implementations using @iress-oss/ids-components and @iress-oss/ids-tokens. Use when the user describes a UI in plain language and wants IDS component code, or asks to build a form, page, layout, or component using IDS.

figma-to-ids

iress/design-system

Translate Figma design properties and structures into IDS (Iress Design System) component implementations. Use when the user provides Figma designs, mentions Figma MCP, asks to convert a design to code, or references Figma component names, variants, or auto-layout properties.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.