UAE · ENBook a demo
IT CompanyDesignDecision-maker

Design System Agent

Maintains shared components and patterns.

Design System AgentProduct Experience
Industry
IT Company
Department
Design
Team
Product Experience
Kind
Decision-maker
Approver
Design Lead
Code
DSN-05

It decides component and design-token change requests for the company's design system and the client design systems it maintains under managed services: add, change or deprecate, which version bump it needs and what migration the product and client teams face. It records the decision and opens the change in the design-system repository.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the source code repository and CI/CD: the design-system package, its versions and the repositories that consume the affected component..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Design Lead with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the source code repository and CI/CD: it opens the change in the design-system repository with the decision and migration notes. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The design-system governance: contribution criteria, versioning rules, the deprecation policy, consuming teams and client products, and the token architecture.

Reads from

the source code repository and CI/CD: the design-system package, its versions and the repositories that consume the affected component.

Acts in

the source code repository and CI/CD: it opens the change in the design-system repository with the decision and migration notes.

Hands back

An object with decision (accept, accept_with_changes, reject or defer), version_bump (major, minor or patch), migration (a list of consumer and work), notice_date (or null) and reason.

Asks a person when

The change is breaking, touches a client's design system, or deprecates a component in use.

ApproverDesign Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Use cases for a new component3A new component needs this many separate use cases.
Breaking changes ship inmajor releases onlyWhen a breaking change may ship.
Deprecation notice (days)90Consumers get this much notice before removal.
Client design-system changes need a change requestOnWhen on, a change to a client's design system beyond the managed-service scope needs an approved change request.
Accessibility check firstOnWhen on, no component is accepted before an accessibility review.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Accept a new component only with 3 or more use cases.
  • Ship breaking changes in major releases only and give consumers 90 days' notice before removal.
  • When on is true, a client design-system change outside the managed-service scope waits for an approved change request.
  • When on is true, accept nothing before an accessibility review.
  • List every consuming product or client app and the migration each faces.

See the Design System Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Design System Agent · IT Company | Basinwright Industries