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.
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/tigerless-labs-design-harness)Servidores MCP que conectan la IA a servicios para el mismo trabajo
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.
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este design-harness | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Autor | tigerless-labs | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | – |
| Estrellas de GitHub | 235 | 111.250 | 67.611 | 32.407 | 29.891 |
| Último cambio de código | 1 sept 2026 | 17 nov 2026 | 13 nov 2026 | 24 jun 2026 | 30 oct 2026 |
| Licencia | – | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (conjuntos de instrucciones) de tigerless-labs que la IA lee y sigue · no es un MCP server
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Claude CodeCodex
Según el README del autor y las carpetas del repo
GitHub account tigerless-labs (organization) is only 5 months old: take extra care
★ 235 stars, few users so far · code last changed 1 sept 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
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
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 12 nov 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Copia esta frase y pégala en un chat de Claude Code
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
Vuelve a abrir Claude Code y escribe /design-harness, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Copiado del README del autor; descarga y ejecuta su código
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el 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
Coloca la carpeta design-harness en ~/.agents/skills/design-harness
~ es tu carpeta de inicio ($HOME)
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Copia esta frase y pégala en un chat de Cursor
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
En el chat Agent de Cursor escribe / y elige design-harness
Checked against official docs 12 nov 2026 · Source: cursor.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu 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 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en 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 referencesPregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.