Evolving Design System Components

This skill grounds Component Library work in two Bitwarden governance pages: Creating new design patterns and Modifying an existing Design System component. Read the canonical pages via get_confluence_page before driving a real proposal — they evolve faster than this skill, and they link to template Figma files and engineering processes referenced below. Figma conventions (property ordering, naming) live in references/figma-conventions.md.

The two paths

There are two governance flows. They share a beginning but diverge.

• Creating a new pattern. A pattern that doesn't yet exist. Path forks at "is this a Core Component, or a Recipe/Snowflake?" based on use cases and complexity.
• Modifying an existing component. A pattern that already exists. Always passes through the UI Foundation team because instances across the product are affected.