Accenture Media Suite:
Design Systems for
LLM Consumption

PRODUCT DESIGN · DESIGN SYSTEMS · AGENTIC AI

A next-generation streaming platform

Accenture Media Suite is an award-winning platform for creating modular streaming services, serving over 100 million monthly viewers worldwide. As its products evolved, it needed a unified design system that could support a cohesive yet configurable visual identity while meeting the different demands of desktop, mobile, and TV.

  1. 01 / FoundationBuilding the token architecture
  2. 02 / Quality assuranceEliminating daily QA meetings with AI
  3. 03 / OptimisationDocumentation & AI
  4. 04 / IntegrationPutting the foundations to work
  5. 05 / SamplesClient highlights

One foundation.
Across every screen.

As design systems lead, I guided the product’s evolution into an AI-based platform, positioning agentic AI as the foundation for its new core feature: rapidly tailoring and deploying custom streaming experiences.

To make this possible, I worked with developers and C-suite stakeholders to create a structured, well-governed design system built to support reliable, AI-assisted feature development.

Intelligent Customization

Clients can tailor branding, layouts, and content to their audiences, while agentic AI simplifies customization and enables more adaptive streaming experiences.

Consistency Without Compromise

Shared tokens, reusable components, and clear guidelines give clients a common foundation while preserving each streaming service’s distinct identity.

AI-Ready by Design

With a design system optimized for AI coding, ideas can be transformed into production-ready features and brought to market faster than ever.

01 / Design system

Building the token architecture

I used Claude to define an early shared set of design values, then organised them into a clear hierarchy of primitives and semantic tokens. This gave AI tools explicit rules to build from, with accessible colour pairings and a DTCG-aligned format keeping the foundation consistent and machine-readable.

Token architecture

From a colour value to a component role.

  1. Primitivepurple/500#a100ff
    Semantic--ds-brand-default
    Componentbutton.primary.background
  2. Primitiveneutral/0#fafafa
    Semantic--ds-surface-base
    Componentbutton.secondary.background
  3. Primitiveneutral/700#26262e
    Semantic--ds-text-primary
    Componentbutton.secondary.foreground
  4. Primitivegreen/500#1a9455
    Semantic--ds-success-fill
    ComponentSuccess fill
  5. Primitiveamber/400#f5a800
    Semantic--ds-warning-fill
    ComponentWarning fill
Brand
Success
Error
Warning
Neutral

Typography

Display40px / 48px · 700
The quick brown fox...
Heading28px / 36px · 600
The quick brown fox...
Body16px / 24px · 400
The quick brown fox...

Using Tokens Studio

Tokens Studio was used to connect the token architecture to native Figma variables, establishing a consistent foundation for the UI kit. With AI speeding up component creation, Tokens Studio helped maintain the token hierarchy and keep design and code aligned.

Tokens Studio for Figma plugin alongside Figma Variables panel

Establishing the design system

The system eventually took shape as a reusable component library with defined variants, states, and responsive behaviour. AI greatly accelerated development, enabling each designer on my team to deliver up to 10 production-ready components per day.

Design system components page showing button variants and states

02 / Quality assurance

Eliminating daily QA meetings with AI

Components were being built faster than ever but they still needed manual review. Spacing, auto-layout, and responsive behaviour often required correction, leaving designers and developers spending hours each week solving QA issues.

Errors. Warnings.
One-click fixes.

I wanted to reduce QA meetings, so I built Component QA using Claude Code and Figma Agents. Connected to Figma’s API, the plugin checks components for design inconsistencies and offers one-click fixes. By catching issues early, it halved the time my team spent in QA meetings within its first week.

Component QA Settings panel
Component QA Reminders panel

03 / Optimisation

Automatic documentation and lowering AI credit usage

I configured Claude with custom skills and routines to generate and maintain documentation for design and engineering teams. These defined how component behaviour, usage guidelines, and implementation details should be captured, keeping documentation consistent and making updates part of the workflow.

Claude custom skill settings and Dev Handoff Spec documentation

Button — Spec

What it is

An interactive control that triggers an action or event when clicked, rendered as a labeled rectangle in one of three visual emphasis levels.

When to use it

  • Submitting a form (e.g. the “Save” or “Confirm” action in a dialog).
  • The single primary call-to-action in a view — use the primary type.

Button — Dev Handoff

Render as a native <button>. 3 Type × 3 Size × 4 State = 36 variants. Box-sizing is border-box: the 1px border on secondary is drawn inside the fixed height, and its content padding is compensated +1px so all types at a given size share the same outer height.

Parts

  • Container — the <button> element, an inline-flex auto-layout box, center-aligned axes. Carries background, border, radius, height and padding.
  • Label — single centered text node; white-space: nowrap. The only child.

The value of markdown and .md files

When I joined the project in early 2026, Accenture was still in the initial stages of its AI enablement journey, with only five million credits shared across several high-priority projects. Ours was the largest consumer, prompting me to investigate ways to reduce usage.

Alongside converting documents into markdown, I introduced reusable .md files containing project context and task instructions, reducing the need to rebuild context every session. Combined with more concise inputs, this helped my team lower unnecessary credit consumption.

04 / Integration

Putting the foundations to work

With the initial design system framework nearly complete after three weeks, we could begin testing Claude’s ability to generate layouts from it. In parallel, the team was also finalising the redesign of the UI builder, preparing the platform for agentic AI workflows.

Accenture Video Solution interfaces for analytics, content management, and UI building

Assessing early issues

We used Claude to generate test layouts and assess how well AI interpreted our design system. Early experiments revealed that some layouts required too many iterations to reach the intended result.

Early featured component for The Last Frontier with Play and My List actions

Trade-offs and rules for consistency

Adopting stricter atomic design rules helped Claude generate layouts faster and more consistently. The results were more rigid, but the better reliability made the trade-off worthwhile.

05 / Samples

Client highlights

Conclusions

< 3 weeksTo establish design system framework
Almost zeroDaily QA meetings
30%Accelerated Feature Delivery
25%Lower platform setup time