Design System Governor logo

Design System Governor

Community
Jason904
design-system-governor

This skill should be used after visual-spec-review passes and before OpenSpec UI update or frontend implementation. It expands screenshot-derived visual specs into a production design system by adding interaction states, responsive behavior, accessibility rules, UX checklist, and implementation constraints without overriding UI type, layout paradigm, component tree, rejected assumptions, or asset strategy.

Overview

PublisherJason904
Repositoryui-skill-lab
Skill namedesign-system-governor
Stars
144
Forks
9
Bundled files
17
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 17 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Jason904 on GitHub. Read the source before you install it.

Installation

Install the Design System Governor AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Jason904/ui-skill-lab/tree/main/.codex/skills/design-system-governor
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Jason904/ui-skill-lab.git /tmp/ui-skill-lab
mkdir -p .claude/skills
cp -r /tmp/ui-skill-lab/.codex/skills/design-system-governor .claude/skills/design-system-governor
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design System Governor in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Design System Governor on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Design System Governor is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Version: 2.0.0

design-system-governor

Expand a reviewed visual spec into a product-grade design system.

This skill reads the seven visual-to-spec files and optional visual-spec-review results. It adds the missing product-level rules that static screenshots cannot show: states, responsive behavior, accessibility, motion, and implementation constraints.

It must never redesign the UI or override screenshot-derived facts.

Trigger Conditions

Use this skill when:

  • visual-spec-review has passed or conditionally passed
  • the user asks to build or expand a design system from visual specs
  • the user asks to add hover/focus/loading/empty/error states
  • the user asks to add responsive and accessibility rules
  • the visual spec must be prepared for OpenSpec UI update or Codex implementation

Required Inputs

Read:

text
03_visual_spec/
  visual-analysis.md
  layout-spec.md
  component-tree.md
  DESIGN.md
  tokens.json
  implementation-risks.md
  human-review-needed.md

Recommended:

text
04_visual_spec_review/
  spec-review-report.md
  conflict-log.md
  revised-files-needed.md

If spec-review-report.md says Fail, stop. Do not generate 05_design_system/.

Source of Truth

  1. reference.png — visual appearance
  2. visual-analysis.md / UI Type Classification
  3. visual-analysis.md / Visible Element Inventory
  4. visual-analysis.md / Rejected Assumptions
  5. layout-spec.md / Layout Paradigm
  6. layout-spec.md / Layer Model
  7. component-tree.md
  8. component-tree.md / Prohibited Components
  9. implementation-risks.md / Asset Strategy
  10. DESIGN.md
  11. tokens.json
  12. human-review-needed.md

Required Sections to Read

From visual-analysis.md:

  • UI Type Classification
  • Visible Element Inventory
  • Rejected Assumptions

From layout-spec.md:

  • Layout Paradigm
  • Layer Model
  • Region Layout
  • Forbidden Layouts

From component-tree.md:

  • Component Tree Type
  • bboxRef for reference-visible components
  • Prohibited Components

From implementation-risks.md:

  • Asset Strategy
  • UI Type Drift Risks
  • Asset Misuse Risks
  • Hallucinated Component Risks

From DESIGN.md:

  • UI Type and Rendering Strategy
  • Asset Strategy
  • Forbidden Assumptions
  • Implementation Rules

From tokens.json:

  • source
  • confidence
  • strictness
  • usedBy
  • bboxRef if present

Main Workflow

  1. Confirm visual-spec-review did not fail.
  2. Read UI Type and Layout Paradigm.
  3. Read Rejected Assumptions and Prohibited Components.
  4. Read Asset Strategy.
  5. Branch design-system generation by UI Type.
  6. Generate component states only for allowed components.
  7. Generate responsive rules without changing layout paradigm.
  8. Generate accessibility rules.
  9. Generate implementation constraints.
  10. Write 05_design_system/.

Hard Rules

  • Do not override screenshot-derived values.
  • Do not change UI Type.
  • Do not change Layout Paradigm.
  • Do not change Asset Strategy.
  • Do not add prohibited components.
  • Do not add rejected layouts.
  • Do not invent dashboard components for non-dashboard UIs.
  • Do not redraw raster/photorealistic main visuals with CSS/SVG if Asset Strategy forbids it.
  • Do not generate frontend code.
  • Do not modify 03_visual_spec/.
  • Do not modify 04_visual_spec_review/.
  • Do not merge this skill with implementation or validation skills.

Output

Write:

text
05_design_system/
  MASTER.md
  pages/
    target-page.md
  ux-checklist.md
  component-state-spec.md
  responsive-spec.md
  accessibility-spec.md
  implementation-constraints.md

Supporting Files

Read these references directly:

  • references/governance-workflow.md
  • references/ui-type-branching-rules.md
  • references/state-rules.md
  • references/responsive-rules.md
  • references/accessibility-rules.md
  • references/asset-aware-design-rules.md
  • references/implementation-constraints-rules.md
  • references/external-skill-usage.md
  • references/output-files.md

Examples:

  • examples/master.example.md
  • examples/target-page.panorama.example.md
  • examples/target-page.dashboard.example.md
  • examples/component-state-spec.panorama.example.md
  • examples/component-state-spec.dashboard.example.md
  • examples/responsive-spec.example.md
  • examples/accessibility-spec.example.md
  • examples/implementation-constraints.example.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Design System Governor AI skill do?

This skill should be used after visual-spec-review passes and before OpenSpec UI update or frontend implementation. It expands screenshot-derived visual specs into a production design system by adding interaction states, responsive behavior, accessibility rules, UX checklist, and implementation constraints without overriding UI type, layout paradigm, component tree, rejected assumptions, or asset strategy.

Why use Design System Governor on TypingMind?

Because you install it once and use it with any model. Design System Governor is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Design System Governor in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Jason904/ui-skill-lab/tree/main/.codex/skills/design-system-governor. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Design System Governor?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Design System Governor?

As many as you like. As long as a model supports skills, you can use Design System Governor with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Design System Governor AI skill free?

Yes. It is published on GitHub by Jason904 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇