// SLIDE 07 — .GITHUB/WORKFLOWS/TOKENS.YML

.GITHUB/WORKFLOWS/TOKENS.YML

usesactions/checkout@v4

usesactions/setup-node@v4

runnpm ci

namePreflight check

nameExtract tokens

NARRATION

on: repository_dispatch: types: workflow_dispatch: manual trigger for testing permissions: contents: write pull-requests: write

// SLIDE 11 — WHAT COMES NEXT

WHAT COMES NEXT.

Chapter 9 handles the other half of the canvas: the images, icons, and graphics that live in Figma as vector nodes and n

NARRATION

Chapter 9 handles the other half of the canvas: the images, icons, and graphics that live in Figma as vector nodes and need to arrive in the repository as optimized, production-ready files. Token extraction deals in structured data , names, values, types. Asset extraction deals in rendered output , SVG, PNG, PDF , and introduces a different set of API surfaces and transformation problems.

// SLIDE 12 — THESIS

THE CORE CLAIM.

Chapter 9 handles the other half of the canvas: the images, icons, and graphics that live in Figma as vector nodes and n

NARRATION

Chapter 9 handles the other half of the canvas: the images, icons, and graphics that live in Figma as vector nodes and need to arrive in the repository as optimized, production-ready files. Token extraction deals in structured data , names, values, types. Asset extraction deals in rendered output , SVG, PNG, PDF , and introduces a different set of API surfaces and transformation problems.

// SLIDE 13 — CLOSE

ASK THE QUESTION. APPLY THE FRAMEWORK.

THE ENTERPRISE GATE//THE ENTERPRISE PATH: EXTR//THE NON-ENTERPRISE PATH:

Brutalist Figma + Claude · Ch.8 · Chapter 8 — Design Token Pipelines

NARRATION

That is the framework. Brutalist Figma + Claude, chapter 8: Chapter 8 , Design Token Pipelines. The patterns are now in place. Apply them.