AI Literacy · CLI Curriculum · For Engineering Teams

Teach the `od` Workflow

Open Design from the command line — scripted, composable, agent-ready

01

Why Now

Design is the last unscripted tool left in the stack

Q3 2026 training backlog

Engineers Already Script Everything Else

Deploys, migrations, and CI all run from the terminal — design still means a mouse and a shared Figma seat
New hires ask why there's a git for code but no equivalent for design work
Agent-native CLIs (Claude Code, Codex, Cursor) already live in every engineer's shell today
No onboarding path teaches design as a scriptable, agent-driven step in the pipeline

Before — GUI Habit

One Designer, One Screen

Every request queues behind a single Figma seat
No way to template or script a repeat layout
Handoff means screenshots dropped in Slack
No audit trail of who changed what, or when

Pilot — Week 1–6

Any Engineer, One Command

14 engineers ran od project create in week one, zero onboarding tickets
Design specs live as git-diffable files, reviewed in normal PRs
od plugin apply scripts a full page from a design system in under 90s
Full shell history doubles as the change-audit trail

02

The Workflow Map

Five commands, one continuous loop

Five Commands, One Loop

od init

new project

od design

import system

design system

od agent

run task

sandbox

od export

ship files

od plugin

apply template

or preview

od preview

html → live

od skill

learns style

next run

more precise

learns your taste workflow stage

Pilot Results, Six Weeks In

14

Engineers Onboarded

zero design-tool tickets filed

38

Pages Shipped via CLI

reviewed in PRs, not Slack

6 min

Median Cycle Time

prompt to merged PR

-71%

Design Backlog

queue length, week 1 → week 6

Guardrails Before Rollout

Control	Detail	Surface	Status
Sandboxed runs	Agent writes only inside the project workspace, never the host	`sandbox`	shipped
BYOK keys	Each engineer's provider key stays in their local env, never centralized	`byok`	shipped
Git-diffable output	Every generated file reviewable in a normal pull request	`diff`	shipped
Command allowlist	`od` subcommands scoped per role through CI policy	`policy`	shipped
Local-first data	No design content leaves the laptop unless explicitly exported	`local`	shipped
Rollback via git	A bad agent run reverts with a plain `git checkout`	`rollback`	evolving

The Five Commands to Teach First

od-101.md

[week 1]
init     = "od project create <name>"     # first command every hire runs
import   = "od design import <repo>"
[week 2]
run      = "od agent run --prompt-file brief.md" # --json pipes into CI
apply    = "od plugin apply <template>"
[week 3]
ship     = "od file export --to ./dist"       # git-diffable, PR-ready

>

The moment od agent run --json piped cleanly into our CI, design stopped being the one GUI-shaped exception in an otherwise scripted stack.

— Staff engineer, pilot cohort

Rollout · Weeks 7–12

Ship the curriculum,
not just the tool.

Week 7: guild office hours — Week 9: od added to onboarding checklist — Week 12: org-wide, CLI-first

Teach the od Workflow