Once the design phase is complete the element is ready for development and testing. This phase includes writing the mark-up, code, and Storybook stories for the element.
The work in this phase may be shared between designers and engineers. Detailed instructions for setting up and working in the repository are in the development guide.
At the end of this phase a pull request will be ready for review and release.
Designer: Gather design assets and prepare documentation
- A short name for the component
- Overview
- How (and when) to use
- Links to alternative components
- Anatomy
- Behaviours
- Variations
- Best practices
Developer: implement the component
All packages live in the design-system monorepo. Work done here includes building, testing, and updating Storybook stories.
@underwriters-labs/design-system— CSS/SCSS and design tokens@underwriters-labs/design-system-web-components— Stencil.js web components (framework-agnostic)@underwriters-labs/design-system-angular18— Angular 18 wrapper@underwriters-labs/design-system-angular19— Angular 19+ wrapper@underwriters-labs/design-system-react19— React wrapper
Run the relevant Storybook locally to verify the component visually, then run tests before opening a pull request:
# Run web component tests
pnpm test:wc
# Run a Storybook to review the component
pnpm storybook:wc # web components (port 6007)
pnpm storybook:angular19 # Angular 19 (port 6009)
pnpm storybook:react19 # React (port 6011)
Create Pull Request
- Design review
- Does the development element match the design and meet all requirements?
- Does the element meet accessibility requirements?
- Development review
- Run and pass all unit/UI tests
- Code and accessibility review
Once the work passes review the pull request will be accepted and the component merged into the main branch, making it available for the next release.