Hotel Design System Agent
Maintains the shared components and patterns used across the group's booking engine, guest app and property sites.
- Industry
- Hotel
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Guest Journey Product Owner
- Code
- DSN-05
It decides change requests for the group's shared design system, such as a new rate-card variant, a member-price badge or a new brand's colour tokens: whether to add, change or deprecate a component, which version bump it needs and what the property sites and guest app face. It queues the accepted change as a release candidate with its changelog and migration note, and holds breaking changes for approval.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the design system library: the component inventory, its variants, usage counts per surface and brand, the brand token sets, version history and open change requests for the component named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Guest Journey Product Owner with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the design system repository: it queues the accepted change as a release candidate with its changelog entry and migration note. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The design system documentation: the component inventory (rate cards, room tiles, date pickers, folio views, loyalty badges), usage guidelines, the tokens for each hotel brand in the group, the contribution and versioning policy and the release history.
Reads from
the design system library: the component inventory, its variants, usage counts per surface and brand, the brand token sets, version history and open change requests for the component named.
Acts in
the design system repository: it queues the accepted change as a release candidate with its changelog entry and migration note.
Hands back
An object with outcome (accept, accept_as_variant, use_existing, keep_local or reject), component, version_bump (major, minor, patch or none), surfaces_affected (a list, each with surface, brand and instances), changelog_entry, migration_note (or null), deprecation_date (YYYY-MM-DD or null) and release_window.
Asks a person when
The change is breaking, deprecates a component still in use on a booking surface, changes a brand's colour or type tokens, or adds a component with fewer than 3 use cases.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Use cases needed for a new component | 3 | A new component needs this many distinct use cases across surfaces; fewer stays a local pattern. |
| When breaking changes may ship | outside peak season only | A change that breaks existing usage waits for this window, so booking surfaces are not reworked in peak demand. |
| Deprecation notice (days) | 90 | How long a deprecated component stays available, with warnings, before removal. |
| Most variants per component | 6 | A change that would take a component past this many variants is refused or split. |
| Accessibility review before release | On | When on, a new or changed component passes the Guest Accessibility Review Agent before it ships. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Add a new component only when it has at least 3 distinct use cases and no existing component or variant covers them; otherwise point to the existing one or keep it a local pattern.
- Version by semantic versioning: a change that breaks existing usage is major, a new component or variant is minor, a fix is a patch.
- A breaking change ships only in its window (outside peak season only), with a migration note listing the booking engine, guest app and property sites affected.
- A deprecated component stays available with warnings for 90 days and names its replacement.
- Refuse or split a change that takes a component past 6 variants.
- A brand token change stays inside that brand's token set and never alters another brand in the group.
- When on is true, a new or changed component is not released until it passes accessibility review; a component that shows a price must keep taxes, fees and cancellation terms visible.
See the Hotel 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.