# Toyota — Design System
> Official visual identity of Toyota, featuring bold red accents, clean typography, and high-contrast layouts.
- **Canonical:** https://uiuxskills.com/library/toyota
- **Source:** https://www.toyota.com/
- **Category:** Automotive
- **Compatible tools:** claude, cursor, lovable, figma-make
- **Coverage:** 81%
- **License:** MIT
- **Last updated:** 2026-11-08T03:40:55.440Z

---

---
version: alpha
name: Toyota
tagline: New Cars, Trucks, SUVs & Hybrids
description: Official visual identity and design system tokens for Toyota's digital web presence.
tone: professional, aspirational, and reliable
color-scheme: light
colors:
  primary: "#EB0A1E"
  secondary: "#CEC6BC"
  accent: "#B00716"
  background: "#FFFFFF"
  surface: "#FFFFFF"
  surface-container: "#F6F6F6"
  surface-dim: "#EBEBEB"
  on-primary: "#FFFFFF"
  on-surface: "#000000"
  on-surface-variant: "#58595B"
  outline: "#D8D8D8"
  error: "#E10A1D"
typography:
  display-lg:
    fontFamily: tcomMed, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 64px
    fontWeight: 700
    lineHeight: "1.1"
    letterSpacing: "-0.02em"
  display-md:
    fontFamily: tcomMed, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 48px
    fontWeight: 700
    lineHeight: "1.15"
    letterSpacing: "-0.01em"
  headline-lg:
    fontFamily: tcomMed, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 32px
    fontWeight: 600
    lineHeight: "1.2"
    letterSpacing: 0em
  headline-md:
    fontFamily: tcomMed, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 24px
    fontWeight: 600
    lineHeight: "1.25"
    letterSpacing: 0em
  headline-sm:
    fontFamily: tcomMed, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 20px
    fontWeight: 500
    lineHeight: "1.3"
    letterSpacing: 0em
  body-lg:
    fontFamily: tcomSans, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 16px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  body-md:
    fontFamily: tcomSans, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 14px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  body-sm:
    fontFamily: tcomSans, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 12px
    fontWeight: 400
    lineHeight: "1.4"
    letterSpacing: 0em
  label-lg:
    fontFamily: tcomSans, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 14px
    fontWeight: 500
    lineHeight: "1"
    letterSpacing: 0.05em
  label-md:
    fontFamily: tcomSans, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 12px
    fontWeight: 500
    lineHeight: "1"
    letterSpacing: 0.05em
  label-sm:
    fontFamily: tcomSans, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 10px
    fontWeight: 600
    lineHeight: "1"
    letterSpacing: 0.1em
rounded:
  sm: 4px
  md: 8px
  lg: 16px
  xl: 24px
  full: 9999px
spacing:
  xs: 4px
  sm: 8px
  md: 16px
  lg: 24px
  xl: 32px
  2xl: 48px
components:
  button-primary:
    backgroundColor: "{colors.background}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-lg}"
    rounded: "{rounded.full}"
    padding: 12px 32px
    height: 48px
    width: auto
  button-primary-hover:
    backgroundColor: "{colors.surface-container}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-lg}"
    rounded: "{rounded.full}"
    padding: 12px 32px
    height: 48px
    width: auto
  button-secondary:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-lg}"
    rounded: 0px
    padding: 12px 32px
    height: 48px
    width: auto
  button-secondary-hover:
    backgroundColor: "{colors.accent}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-lg}"
    rounded: 0px
    padding: 12px 32px
    height: 48px
    width: auto
  card:
    backgroundColor: "{colors.background}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.md}"
    padding: "{spacing.lg}"
    height: auto
    width: 100%
    borderColor: "{colors.outline}"
  card-elevated:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.md}"
    padding: "{spacing.lg}"
    height: auto
    width: 100%
  input-field:
    backgroundColor: "{colors.surface-container}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.sm}"
    padding: 10px 16px
    height: 44px
    width: 100%
    borderColor: "{colors.outline}"
  input-field-focus:
    backgroundColor: "{colors.background}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.sm}"
    padding: 10px 16px
    height: 44px
    width: 100%
    borderColor: "{colors.primary}"
  link:
    backgroundColor: transparent
    textColor: "{colors.primary}"
    typography: "{typography.body-md}"
  link-hover:
    backgroundColor: transparent
    textColor: "{colors.accent}"
    typography: "{typography.body-md}"
  badge:
    backgroundColor: "{colors.surface-dim}"
    textColor: "{colors.on-surface-variant}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 4px 8px
    height: 24px
    width: auto
    borderColor: "{colors.secondary}"
  badge-error:
    backgroundColor: "{colors.error}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.sm}"
    padding: 4px 8px
    height: 24px
    width: auto
  divider:
    backgroundColor: "{colors.outline}"
    height: 1px
    width: 100%
  nav-item:
    backgroundColor: transparent
    textColor: "{colors.on-surface}"
    typography: "{typography.label-lg}"
    padding: 8px 16px
    height: auto
  swatch-secondary:
    backgroundColor: "{colors.secondary}"
    rounded: "{rounded.sm}"
    size: 32px
motion:
  duration-short: 200ms
  duration-medium: 500ms
  easing-standard: ease
elevation:
  sm: 0 1px 2px rgba(0,0,0,0.1)
  md: 0 2px 4px rgba(0,0,0,0.2)
  lg: 0 4px 8px rgba(0,0,0,0.3)
---

## Overview

The Toyota visual identity is built around a premium, bold, and highly functional aesthetic. It balances high-impact, full-bleed automotive photography with clean, structured layouts to convey reliability, innovation, and adventure. The interface utilizes a stark black, white, and signature Toyota Red color palette to establish an authoritative and engineered presence.

## Colors

The color strategy relies on a high-contrast, minimalist palette dominated by stark white and deep black, punctuated by a vibrant signature red for focus and interaction. This ensures maximum legibility, premium brand recognition, and clear interactive pathways.

*   Primary (`{colors.primary}`): `#EB0A1E` - The iconic Toyota Red, used as the primary brand identifier, logo background, and key interactive accents.
*   Secondary (`{colors.secondary}`): `#CEC6BC` - A warm, premium metallic sand/gray tone used for subtle backgrounds and secondary brand accents.
*   Accent (`{colors.accent}`): `#B00716` - A deeper red used for hover states and active links to maintain high contrast and interactive feedback.
*   Background (`{colors.background}`): `#FFFFFF` - The default clean canvas background for the entire website.
*   Surface (`{colors.surface}`): `#FFFFFF` - Used for cards, navigation bars, and content containers.
*   Surface Container (`{colors.surface-container}`): `#F6F6F6` - An off-white surface variant used to group content blocks and provide subtle depth.
*   Surface Dim (`{colors.surface-dim}`): `#EBEBEB` - A light gray surface variant used for tags, disabled states, and secondary containers.
*   On Primary (`{colors.on-primary}`): `#FFFFFF` - High-contrast white text used on top of primary red elements.
*   On Surface (`{colors.on-surface}`): `#000000` - The primary text color used for maximum readability on white and light gray surfaces.
*   On Surface Variant (`{colors.on-surface-variant}`): `#58595B` - A medium-dark gray used for secondary body copy, captions, and metadata.
*   Outline (`{colors.outline}`): `#D8D8D8` - A light gray border color used to define boundaries without adding visual noise.
*   Error (`{colors.error}`): `#E10A1D` - A bright red used for error states, alerts, and critical notifications.

## Typography

The typography strategy employs two highly functional sans-serif families: `tcomMed` for bold, structured headings and `tcomSans` for clean, readable body copy. This dual-stack approach ensures high legibility across technical specifications and marketing copy.

*   `typography.display-lg`: Massive hero titles and vehicle model names on desktop screens.
*   `typography.display-md` (inferred): Secondary hero titles and major section headers.
*   `typography.headline-lg` (inferred): Prominent section headings and feature titles.
*   `typography.headline-md`: Card titles and medium-sized promotional headings.
*   `typography.headline-sm`: Small card headers and sub-sections.
*   `typography.body-lg`: Primary body copy and introductory paragraphs.
*   `typography.body-md`: Standard body text size used across the site for descriptions and specifications.
*   `typography.body-sm` (inferred): Legal disclaimers, footnotes, and fine print.
*   `typography.label-lg` (inferred): Navigation items and primary button labels.
*   `typography.label-md` (inferred): Secondary button labels, tags, and interactive controls.
*   `typography.label-sm` (inferred): Small uppercase badges and category tags.

## Layout

The layout is structured around a clean, high-impact grid system designed to showcase vehicles. It features a sticky top navigation bar with a centered logo, followed by a full-bleed marquee carousel. Content sections are organized into structured grids (typically 1 to 4 columns depending on viewport size) with generous vertical spacing to separate vehicle categories, shopping tools, and promotional content. The observed section order from top to bottom is `nav`, `hero`, `features`, `shopping-tools`, and `footer`. The hero composition pattern relies on a full-bleed background image carousel showcasing vehicles in dramatic outdoor settings with centered white typography and a prominent white pill CTA button. The layout is fully responsive, collapsing the desktop navigation into a hamburger menu on mobile devices and scaling multi-column grids down to a single column layout using spacing tokens like `{spacing.md}` for gutters and `{spacing.2xl}` for section gaps.

## Elevation & Depth

Subtle single-layer shadows are utilized across three levels to maintain a modern, clean, and flat aesthetic. Depth is conveyed primarily through flat, high-contrast color blocks and crisp borders rather than heavy shadows.

*   `elevation.sm` - Used for subtle interactive card lift and minor container separation.
*   `elevation.md` - Applied to dropdown menus, popovers, and interactive hover states.
*   `elevation.lg` - Reserved strictly for modals, drawer overlays, and high-priority floating UI elements.

## Shapes

Toyota's design system utilizes a deliberate mix of sharp and rounded shapes to balance consumer friendliness with an engineered, technical feel. Primary interactive buttons in high-impact areas (like the hero carousel) utilize a fully rounded `{rounded.full}` pill shape to stand out aggressively against photographic backgrounds.

Conversely, secondary buttons and functional UI elements (such as cards and input fields) use sharp 0px corners or subtle `{rounded.sm}` to `{rounded.md}` border radii to maintain a structured, engineered feel. Larger containers and promotional blocks may scale up to `{rounded.lg}` or `{rounded.xl}` to soften the layout where appropriate.

## Components

> **Note:** This spec was generated from a website scrape and contains visual approximations.
> For production use, add a deep reference to each component pointing to its authoritative
> source (Storybook story, metadata file, or component spec):
> `→ Deep reference: src/components/Button/metadata.ts`

### button-primary
The primary button is a fully rounded pill shape using `{rounded.full}`. It features a clean `{colors.background}` fill with `{colors.on-surface}` text and `{typography.label-lg}` typography, designed to stand out against rich photographic backgrounds.

### button-secondary
The secondary button is a sharp, technical button with 0px border radius. It uses `{colors.primary}` as its background, `{colors.on-primary}` for text, and `{typography.label-lg}` typography, switching to `{colors.accent}` on hover.

### card
A structured container using `{rounded.md}` and `{colors.background}`. It features a subtle border defined by `{colors.outline}` and internal padding of `{spacing.lg}` to display vehicle specs and shopping tools.

### card-elevated
An elevated variant of the card component that relies on `{colors.surface}` and `{elevation.sm}` instead of a border. It uses `{rounded.md}` and `{spacing.lg}` padding to group promotional content.

### input-field
A clean form input field with a `{colors.surface-container}` background, `{colors.outline}` border, and `{rounded.sm}` corners. On focus, it transitions to a `{colors.background}` fill with a `{colors.primary}` border.

### badge
A small metadata tag utilizing `{colors.surface-dim}` background, `{colors.on-surface-variant}` text, and `{rounded.sm}` corners. It is used to display category labels and vehicle features.

### badge-error
A high-visibility alert badge utilizing `{colors.error}` background and `{colors.on-primary}` text. It is used for critical notifications, recalls, and system errors.

### divider
A thin horizontal rule utilizing `{colors.outline}` with a height of 1px. It is used to separate content blocks and maintain structural hierarchy.

### nav-item
A clean navigation link using `{colors.on-surface}` text and `{typography.label-lg}` typography. It features transparent backgrounds and generous horizontal padding for touch targets.

### swatch-secondary
A small, square color swatch utilizing `{colors.secondary}` and `{rounded.sm}` corners. It is used in vehicle configurators to represent exterior and interior color options.

## Do's and Don'ts

| Do | Don't |
| --- | --- |
| Use `{colors.primary}` for primary brand accents, active links, and key interactive highlights. | Never use `{colors.primary}` for body text as it degrades readability and brand hierarchy. |
| Apply `{colors.on-surface}` for all primary body text to ensure maximum readability against `{colors.background}`. | Do not use `{colors.surface-dim}` as a text color on `{colors.background}` due to poor contrast. |
| Use `{rounded.full}` on `{colors.background}` for hero carousel call-to-action buttons to ensure they stand out. | Avoid applying `{rounded.full}` to standard content cards; keep them structured with `{rounded.md}`. |
| Utilize `{colors.surface-container}` for secondary content blocks to create visual separation without using heavy borders. | Avoid using heavy shadows from `{elevation.lg}` on standard flat cards; reserve them for overlays. |
| Apply `{typography.display-lg}` exclusively for main hero titles and vehicle model names. | Never mix multiple font families; stick strictly to the `{typography.display-lg}` and `{typography.body-lg}` font stacks. |
| Ensure `{colors.outline}` is used for subtle borders on cards and input fields to maintain a clean structure. | Do not apply `{colors.accent}` to static text; reserve it strictly for hover states like `{colors.accent}` on buttons and links. |
| Use `{spacing.lg}` for internal card padding to maintain a consistent, breathable layout. | Do not use arbitrary spacing values; always snap to the defined scale from `{spacing.xs}` to `{spacing.2xl}`. |
| Apply `{rounded.sm}` on `{colors.surface-dim}` for small metadata badges to maintain an engineered aesthetic. | Never use `{rounded.full}` on `{input-field}` elements; keep them structured with `{rounded.sm}`. |

## Content Style

CTA labels must be action-oriented, concise, and direct. Button copy should read as clear, high-impact verb forms in sentence case (such as "Learn More", "Schedule Now", or "Shop Now") to drive immediate engagement.

Headlines must remain bold, aspirational, and product-focused. Phrasing should emphasize performance, reliability, and adventure (for example, "Momentum without boundaries" or "Always in its element") rather than purely technical specifications.

The layout maintains a low to medium copy density. The interface relies heavily on high-impact imagery and short, scannable feature descriptions, utilizing generous whitespace and clear spacing to prevent cognitive overload.

## Imagery & Icons

The visual language relies on high-contrast, dramatic, and professional photographic treatments of vehicles in natural, rugged, or clean studio environments. Photography should feel aspirational and authentic, avoiding artificial staging. Icons are minimal, clean, and stroke-based to complement the modern engineering aesthetic, utilizing thin lines that align with the `{colors.outline}` weight. Logo lockups must remain clean and uncluttered, surrounded by ample whitespace to preserve brand authority.

---

## Companion prompt

## Role
You are an AI assistant generating UI components and layouts for Toyota, a professional, aspirational, and reliable automotive brand with a minimal, enterprise-grade aesthetic. Content, copy, and information architecture remain owned by the product team.

## How to use design.md
1. Reference every visual value by token name — `{colors.primary}`, `{typography.body-md}`, `{rounded.sm}` — never hardcode hex values, font sizes, or pixel radii.
2. Respect the components block exactly: `button-primary`, `card`, `input-field`, `badge`, and all other listed variants. Do not invent variants (e.g., `button-ghost`, `card-outlined`) that the spec does not define.
3. Follow the shape rule: `{rounded.full}` applies to hero carousel CTAs only; standard cards and inputs use `{rounded.md}` or sharp corners per the Shapes narrative. Never apply `{rounded.full}` to cards.
4. Consult the Do's and Don'ts as authoritative overrides. If a user request conflicts — for example, using `{colors.primary}` for body text — surface the conflict explicitly before proceeding.
5. Use the Layout narrative (sticky nav, full-bleed marquee, 1–4 column grid, generous vertical rhythm) to guide all layout and spacing decisions.

## Output contract

**Must:**
- Use all tokens by name on every generated component.
- Cover hover, focus, and disabled states for all interactive components (`button-primary-hover`, `input-field-focus`, `link-hover`, etc.) where the spec defines them.
- Apply `{spacing.xs}` through `{spacing.2xl}` for all padding, margin, and gap values.
- Match CTA copy style — action-oriented and concise — and heading tone — bold and aspirational — per the Voice and Content section.
- Maintain a minimum 4.5:1 contrast ratio; use `{colors.on-primary}` on red surfaces and `{colors.on-surface}` on light surfaces.

**Must NOT:**
- Invent colors, font families, or radii outside the spec.
- Use generic utility defaults (e.g., `gray-500`, `rounded-md` as a literal string) when a named token exists.
- Use `{colors.primary}` for body text.
- Mix `tcomSans` and `tcomMed` outside their designated type roles.
- Rewrite, replace, or invent page copy, headings, navigation labels, or content hierarchy.
- Alter navigation structure or page sections as a side effect of applying tokens.

## When in doubt
- If the spec does not define a value, ask the user before introducing one.
- For ambiguous backgrounds, default to `{colors.surface-container}` for grouped content blocks and `{colors.background}` for the base canvas.
- For unspecified breakpoints, use mobile-first layout with a single breakpoint at 768px, consistent with the 1–4 column grid described in Layout.
- Tokens not explicitly listed in the spec (e.g., elevation values) should not be assumed; ask before applying shadow or depth treatments beyond what the components block implies.
- When torn between two compliant options, prefer the more structured, restrained choice — this brand reads engineered, not decorative.
