---
title: "component libraries | Skills We Assign For | Azendo"
description: "Component libraries — API design, versioning, adoption, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/component-libraries/"
---

[Skills](https://azendo.co/skills/) Design and research 

# component libraries.

A component library is the implemented set of reusable interface elements — the code counterpart of a design system — versioned, documented and consumed by the applications that use it.

## Where component libraries fits on a long engagement.

Component API design decides whether a library is used or worked around. Too rigid and teams copy the component to modify it; too flexible and it stops enforcing anything, becoming a styled div with a hundred props. Finding that balance is the actual skill, and it is judged by what teams do rather than by the API's elegance.

Versioning has to be taken seriously because every consumer is affected. A breaking change in a shared component means coordinating upgrades across applications, and without semantic versioning and a deprecation path that coordination becomes an event rather than a routine.

## What an assigned team does with component libraries.

Adoption is the measure that matters and the one nobody tracks. A library nobody uses is worse than none, because it consumed the effort and delivered nothing while teams built their own.

Measuring adoption and fixing what blocks it is ongoing product work rather than a build, held within an agreed [committed monthly capacity](https://azendo.co/pricing/).

## What we use component libraries for.

* Components that do not get copied An API flexible enough that teams extend rather than fork.
* Breaking changes with a deprecation path Semantic versioning so upgrades are routine rather than coordinated events.
* Adoption measured Tracking real usage, because an unused library delivered nothing.

## How component libraries capacity is assigned.

Component library capacity is assigned across design and frontend on one agreement, with adoption treated as the success measure.

## Roles we assign component libraries for

* [UI Designer UX/UI design](https://azendo.co/services/ux-ui-design/ui-designer/)

## Service lines it sits in

* [UX/UI design](https://azendo.co/services/ux-ui-design/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in design and research

* [Figma — skill we assign for](https://azendo.co/skills/figma/)
* [Storybook — skill we assign for](https://azendo.co/skills/storybook/)
* [Maze — skill we assign for](https://azendo.co/skills/maze/)
* [Hotjar — skill we assign for](https://azendo.co/skills/hotjar/)
* [usability testing — skill we assign for](https://azendo.co/skills/usability-testing/)
* [design systems — skill we assign for](https://azendo.co/skills/design-systems/)
* [design tokens — skill we assign for](https://azendo.co/skills/design-tokens/)
* [Figma Dev Mode — skill we assign for](https://azendo.co/skills/figma-dev-mode/)

## Tell us what your roadmap needs component libraries for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)