Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Feed your agent papers and half-formed ideas — it links them into a system design you can defend. Markdown keeps the record; a visual canvas makes it readable. An Agent Skill for Claude Code & any SKILL.md-compatible agent.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/tigerless-labs-design-harness)MCP servers that connect the AI to services for the same work
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Same kind of work, ordered like the Skills list
| This one design-harness | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | tigerless-labs | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | – |
| GitHub stars | 235 | 111,250 | 67,611 | 32,407 | 29,891 |
| Last code change | Sep 1, 2026 | Nov 17, 2026 | Nov 13, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | – | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (instruction sets) by tigerless-labs that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Claude CodeCodex
From the maker’s README and the folders in the repo
GitHub account tigerless-labs (organization) is only 5 months old: take extra care
★ 235 stars, few users so far · code last changed Sep 1, 2026
10 scripts that can run on a computer: scripts/build_canvas.py, scripts/check_doc_links.py, scripts/check_style_pack.py, scripts/check_workspace.py and 6 more
Could not check every script (some are too large); read them first
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 9aca84e (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the plugins/design-harness/skills/design-harness folder again. The ZIP must have a design-harness folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick design-harness.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /design-harness or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Put the design-harness folder at ~/.agents/skills/design-harness
~ is your home folder ($HOME)
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick design-harness
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: design-harness
description: A decision board for evidence-based calls — the human adjudicates, the agent runs the errands. Three layers (sources → ideas → output) in plain markdown, synced on the human's command, projected onto a visual canvas. Use for vendor/tool selection, literature reviews, due diligence, competitive analysis, or any contested call that must stand on traceable evidence — triggers like "file these papers", "put this on the board", "assemble the design", "how do we decide this".
license: MIT
allowed-tools: Bash(python3 ${CLAUDE_SKILL_DIR}/scripts/*)
metadata:
author: tigerless-labs
repository: https://github.com/tigerless-labs/design-harness
---
# design-harness — the human adjudicates, the agent runs errands
Markdown is the **single source of truth**; the canvas HTML, every layer index, and the
location registry are projections, rebuildable at any time. Judgment comes only from the
human; you lay out options and evidence and run the errands — never adjudicate in the
human's place.
## Structure
### Workspace layout
```
<workspace>/
├── target.md the human's acceptance criteria; source of the output form
├── logs.md append-only change ledger (see "Disciplines · Ledger")
├── index.md workspace entry point
├── sources/<type>/*.md ① evidence: one source, one card
├── ideas/*.md ② judgments (archive/ holds archived cards)
├── output/… ③ assembly; internal structure set by the chosen output form
└── board/*.md free surface: one file, one board
```
A host may hold many workspaces under any directory names; the sole registry is
`.design-harness/config.json` at the host root — discovery trusts the registry, never
the directory name.
Every layer also carries an `index.md`, grouped under tag headings (`## TAG: one line on
why they belong together`), unclassified cards flat at the end after a `---` divider and
an *unclassified* marker. Search goes through the indexes; there is no classification
layer.
### Three layers + the free surface
1. **sources/ — evidence.** One source, one card, filed under `sources/<type>/`. The
agent ingests and grades freely, and invents the type directories itself — no preset
list; name them after what the source is (papers, github, podcasts, …), adding
directories as needed. The directory name projects verbatim as the card's badge on
the canvas.
2. **ideas/ — judgments.** **Judgment comes only from the human**: decision judgments the
human voices in conversation are transcribed into idea cards automatically, and the
human can simply ask for a card to be added; the agent transcribes, never invents.
Two states: live (the file exists) and archived (moved into `ideas/archive/`, never
deleted). A new idea repeating an old card's judgment merges automatically; a
conflicting one puts both on the board for the human to pick.
3. **output/ — assembly, the convergent layer.** **First assembly is human-initiated**;
its form comes from [references/output-forms/](references/output-forms/system-design.md)
and the human's `target.md`. Ideas diverge, output converges: output changes only on
the human's word (see "Workflow · Sync").
One free surface besides: **board/** — the human's own boards, one markdown file per
board (comparison matrices, theme grids, any scratch reasoning). **No schema, no
required fields** — this freedom belongs to the human; edit only when asked ("lay these
three sources out as a comparison").
### Card schema and templates
- A card = **frontmatter + title + summary**. No fixed sections; references are inline
links in the summary.
- `ideas/` cards (including `archive/`): frontmatter **requires `id` and `type`**;
`tags` and `conflicts` optional (see "Exactly three structured facts"). No status
field — the file's existence is the live state, sitting under `archive/` is the
archived state.
- `sources/` cards: frontmatter optional; when present only `tags` is read.
- `board/` documents: **no schema**. The board is **terminal**: it may reference any
layer, but sources/ideas/output must never reference the board — distill a board's
conclusions into idea cards.
idea card template:
```markdown
---
id: <kebab-slug, matching the filename>
type: idea
tags: [<at most one; omit the whole line>]
conflicts: [<ids of prior cards this judgment contends with; omit when none>]
---
# <the judgment in one sentence>
<Summary: what the judgment says and why; the evidence and prior cards it stands on as
inline links.>
```
source card template:
```markdown
---
tags: [<at most one; the whole frontmatter may be omitted>]
---
# <source name + one-line characterization>
<Core content + relevance to this project; the original provenance (arXiv/URL/date/
authors) as inline links.>
```
target template:
```markdown
# target — acceptance criteria for the output
## Purpose
(One paragraph: what this workspace decides, for whom, and where the boundaries are.)
## Current requirements
- (One checkable requirement per line.)
## Fulfilment map
- (Requirement → output file mapping, updated with each assembly.)
```
### Exactly three structured facts
1. **References** — inline markdown links in the card body. Forward only: a link points
at the evidence or prior cards this card stands on, never at supporters. "Who cites
me" is a projection-derived backlink, never written down. **Acyclic**: mutual
references mean the two cards should merge, or one edge is a mistakenly written
backlink — delete it.
2. **Tags** — single level, **at most one per card**, optional. A card that truly
belongs to two tags is two cards: split it. No tag just means unclassified. Tags may
be proposed by the human or assigned by the agent.
3. **Conflict** — the optional `conflicts: [<other card's id>]` in the **newer** card's
frontmatter, declaring a judgment conflict with prior cards (written on the new card
only, acyclic, same direction as references). The field lives exactly as long as the
conflict: the human's adjudication removes it — archive the loser and the edge
vanishes with the card; rewrite in place and the entry is deleted. The indexes'
pending-conflict annotations derive from this field.
Everything else — backlinks, distances, coordinates, clusters, index groupings — is
derived and never enters the truth.
### Rendering contract — the engine's minimum
Everything projection needs. **This section is the engine; everything else in this file
is methodology**, freely reconfigurable per schema — one engine serves many thin
schemas, a new scenario is a new schema configuration rather than a new engine; the
contract binds files, and the CLI is only the first host.
- Four layer names: `sources/` and `ideas/` become canvas nodes, `output/` and `board/`
become document panels. Paths containing an `archive/` segment are excluded;
`index.md` is excluded.
- Files are UTF-8 markdown.
- Frontmatter is optional; when present it must close (`---` … `---`).
Everything else degrades without breaking: no H1 → show the filename stem; no tag → the
*unclassified* group; any source type directory → the name projects verbatim;
unresolvable link → no edge. Silent data loss is a validator error, never waved through:
markdown under an unknown top-level directory, or frontmatter opened but never closed,
is INVALID.
### Canvas — the only projection surface
The canvas is the human's main thinking surface and **only a projection** — it holds no
facts and accepts no writes that bypass markdown. It doubles as the sharing surface:
every card links back to its evidence, so handing someone the board hands them the
reasoning behind the design. There is exactly one canvas — the
unified canvas ([template](canvas/template.html); its interaction contract lives in the
workspace's canvas module doc) — and exactly one builder: the rules (truth-driven,
edges = in-card references, layout derived from referencesAsk, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.