Skip to content
AAOE
Draft2 min read

Design System-First Engineering

Purpose

This Standard defines Design System-First Engineering as the preferred engineering approach for developing consistent user-facing systems.

Engineering teams should establish reusable design foundations before creating individual interface implementations.


Standard

Engineering teams shall define a Design System before implementing individual screens whenever practical.

The Design System becomes the authoritative reference for visual, interaction, and component consistency.

Interface implementations shall conform to the Design System.


Principles

Design System-First Engineering shall:

  • establish reusable design foundations
  • improve interface consistency
  • reduce duplicated design effort
  • improve engineering collaboration
  • improve AI-assisted implementation
  • improve maintainability
  • preserve design traceability

Design System Components

A Design System may include:

  • Design Tokens
  • Component Library
  • Interaction Patterns
  • Accessibility Standards
  • Layout Principles
  • Typography
  • Color System
  • Iconography

Artifacts should be proportionate to project complexity.


Engineering Workflow

The preferred engineering sequence is:

User Needs

UX Specification

Design System

Architecture Review

Screen Design

Implementation

Validation

Screens should derive from the Design System rather than defining it.


Traceability

Interface implementations should remain traceable to:

  • Design System
  • UX Specifications
  • Functional Specifications
  • Standards
  • Discoveries

Design decisions should preserve consistency across implementations.


Exceptions

Small prototypes or disposable experiments may not require a complete Design System.

Long-lived products should establish reusable design foundations before expanding interface implementations.


Relationship to Discoveries

This Standard operationalizes DISC-0004 — Design Systems Before Screens.

The Discovery explains why this approach emerged. This Standard defines how engineering teams apply it.


Relationship to the Operating Model

The Operating Model applies this Standard through:

  • Design System Specifications
  • UX Specifications
  • Work Orders
  • Architecture Reviews
  • Implementation Reports

Compliance

Engineering work conforms to this Standard when:

  • Design foundations precede screen implementation.
  • Interface implementations conform to the Design System.
  • Design consistency is preserved.
  • Exceptions are explicitly documented.

Future Evolution

Future Standards may define:

  • Design Token Governance
  • Component Versioning
  • Accessibility Validation
  • Multi-Platform Design Systems
  • AI-Assisted Design System Generation