Back to all projects

Design Repo Workflows

Page
Build from a page brief
Copy
Adapt a reference
Audit
Check against design rules

Design Repo Workflows

Design tooling · Plugin development

Give an agent the same brief and rules a designer uses.

  • AI repository
  • Agent skills
  • Design systems
  • Codex
Prototype package
· v0.1.0
Scope
3 skills · Copy, Page, Audit
Artifact
Local Codex package

Design Repo Workflows is a local package for giving agents the right design context for one task. It defines what the agent can read or change and how to report the evidence for its result.

Context comes from the repositorySelected paths from the local source
DESIGN.md
profiles/navis/pages/
tokens/
.agents/skills/
.agents/design/

Give every rule an address

  • Repository structure
  • Native tokens

Shared rules live in the design repository. A project profile supplies the product’s identity and authoritative sources. One selected page brief defines the surface in scope. The agent loads the components and token records the task actually needs.

The workflow preserves the token identities, modes and aliases from the native source. This lets a reviewer trace an implementation choice back to the design system instead of reconstructing the choice from a prompt.

One brief, three workflowsCapabilities of v0.1.0
Copy
Adapt an inspected reference to the project system
Page
Create or refine one specified surface
Audit
Read the target and report evidence and unresolved checks

Separate creating from reviewing

  • Copy
  • Page
  • Audit

Copy takes a reference and identifies the structure worth carrying into the project. Page starts from the project’s own brief and components. Audit is read-only. Its findings can inform a later change with a separate brief.

Keeping each task explicit gives the reviewer a clear boundary. An audit of a page can identify a missing token or an unverified interaction while leaving the page untouched.

A reviewable handoffEvidence follows the result
  1. Record the brief, source and target
  2. Check the result against applicable rules
  3. List evidence and unresolved checks

Show what was actually checked

  • Verification
  • Handoff

The local package uses synthetic fixtures to exercise how it locates the requested context and checks a bounded design spec. The resulting report separates observed findings from checks that need a real browser or design file.

For an actual interface, a reviewer still needs to inspect layout at the required widths, use the controls with a keyboard and confirm contrast and design bindings. These checks stay visible in the handoff.

Read the note on design context
Next Project

Yumo

Find, compare and book car care.