loom-design
v2.2.0Optional using-loom-design discovery routing and two stations — capture-intent, write-spec — turn a rough idea into a confirmed intent and a risk-declared spec, route non-blocking second-vendor suggestions, and provide product-principles and design-system tools. Reads loom-code's contract package. Claude Code, Codex + Antigravity CLI.
By koukoLicense: MIT0 GitHub starsUpdated 3 days ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 21, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install loom-design for Codex and Claude Code
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add loom-design@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/kouko/loom-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is loom-design/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/capture-intent/SKILL.md├── skills/design-system/SKILL.md├── skills/product-principles/SKILL.md├── skills/using-loom-design/SKILL.md└── skills/write-spec/SKILL.md
Included Skills5
Capture and confirm a change intent. Use when someone wants a feature or change and no intent file exists yet.
Ratify a visual DESIGN.md. Use for a UI design system: colors, type, layout, and component tokens. 視覺設計系統 / デザインシステム.
Ratify PRINCIPLES.md. Use when a product needs principles or someone asks what should govern product, design, or engineering trade-offs.
Route broad Loom product-definition requests to intent, specification, principles, or visual design skills when the needed skill is unclear.
Write a design spec from a confirmed intent. Use for a requested spec or a needs-design: yes intent without one.
Plugin manifests2
{
"name": "loom-design",
"version": "2.2.0",
"description": "Optional using-loom-design discovery routing and two stations — capture-intent, write-spec — turn a rough idea into a confirmed intent and a risk-declared spec, route non-blocking second-vendor suggestions, and provide product-principles and design-system tools. Reads loom-code's contract package. Claude Code, Codex + Antigravity CLI.",
"author": {
"name": "kouko",
"url": "https://github.com/kouko"
},
"homepage": "https://github.com/kouko/loom-plugins/tree/main/loom-design",
"repository": "https://github.com/kouko/loom-plugins",
"license": "MIT",
"keywords": [
"loom-design",
"capture-intent",
"write-spec",
"product-principles",
"design-system",
"intent",
"spec",
"ui-flows",
"design-tokens",
"interface-design",
"ui-ux",
"constitution",
"principles",
"portable"
],
"skills": "./skills/",
"interface": {
"displayName": "loom-design",
"shortDescription": "Intent and spec stations for the loom flow, for Codex CLI",
"longDescription": "The design side of the loom flow. capture-intent interviews the user until the change has a problem statement in their own words, writes it as an intent, and reads it back for confirmation — decision point ①, the first of the three the user ever answers. write-spec turns that confirmed intent into a spec: requirements with acceptance criteria, the design decisions and who made each, the evidence for the current state, and the UI flows; for a product change it reads the visible behaviour back before any plan exists — decision point ②. Two tools sit beside them: product-principles writes a product's PRINCIPLES.md and records who ratified it, and design-system emits DESIGN.md tokens (or a conventions stub for TUI/CLI) and never blocks. Verdicts are not rendered here — the spec goes to loom-code's closing-review station under its spec and design-conformance lenses. This plugin reads loom-code's versioned contract package and declares the version it requires.",
"developerName": "kouko",
"category": "Productivity",
"capabilities": [
"Interactive",
"Read",
"Write"
],
"defaultPrompt": [
"I have a rough idea — help me pin down what the change actually is.",
"Turn this confirmed intent into a spec.",
"Draft the product principles for this idea.",
"Design the look for this feature."
],
"websiteURL": "https://github.com/kouko/loom-plugins/tree/main/loom-design",
"brandColor": "#0E7490"
}
}{
"name": "loom-design",
"version": "2.2.0",
"requires-contract": ">=2.1",
"description": "Optional using-loom-design discovery routing and two stations — capture-intent, write-spec — turn a rough idea into a confirmed intent and a risk-declared spec, route non-blocking second-vendor suggestions, and provide product-principles and design-system tools. Reads loom-code's contract package. Claude Code, Codex + Antigravity CLI.",
"author": {
"name": "kouko",
"url": "https://github.com/kouko"
},
"homepage": "https://github.com/kouko/loom-plugins/tree/main/loom-design",
"repository": "https://github.com/kouko/loom-plugins",
"license": "MIT",
"keywords": [
"loom-design",
"capture-intent",
"write-spec",
"product-principles",
"design-system",
"intent",
"spec",
"ui-flows",
"design-tokens",
"interface-design",
"ui-ux",
"constitution",
"principles",
"portable"
],
"skills": "./skills/"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[loom-design on Agent Plugins Marketplace](https://pluginsmp.com/plugins/loom-design)