Small enhancement

Small enhancement

Adding a small capability to a component — something that does not affect the component's architecture, such as adding a colour to a label.

When to use this

Use this when you're extending an existing component in a contained way. If the change requires deeper integration or a refactor, it's a Large enhancement. If it introduces something new across the system, see New feature across components.

At a glance

Design	Code	Doc	Checkpoints	Typical release
optional	✓	✓	triage → (design) → review & merge	patch / minor

Design is optional here: a token- or style-level tweak may only need alignment with the design tokens, not a full Figma pass. When Design is skipped, there are two checkpoints; when it's included, three.

Flow

1. Propose

• Check existing issues.
• Open a Feature request and draft the requirements.

Checkpoint — Core team triage.

2. Design (if the change is visible)

• Start from the relevant Figma file (usually Components or Design Tokens).
• Align the change with the design tokens; annotate it.

Checkpoint — Core team design validation (before any code).

3. Code

• Create a branch (feat type in commitlint.config.js).
• Implement the change; extend the API if needed and document it.
• Add/update the Storybook view (visual + a11y).
• Add tests; verify supported browsers/devices.
• Update dependent packages; write the changelog.

4. Submit

• Open a Pull Request to dev, linking the issue.

Checkpoint — Core team review & merge.

5. Doc

• Update the component documentation (extend the existing page — e.g. the new colour in the set).

6. Release

• Handled by the core team — typically a patch or minor release.

---

Step descriptions: Steps reference. Questions: Stack Overflow.