Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Unofficial Claude Skill derived from the book Refactoring UI — a design rulebook and diagnostic layer for web UI. 151 tracked rules, design token generation, and Tailwind mappings.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/edisonmbli-refactoring-ui-skill)同じ作業で AI をサービスにつなぐ MCP
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.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
同じ種類の作業。Skill 一覧と同じ並び
| これ refactoring-ui-skill | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 作者 | edisonmbli | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 482 | 112,544 | 68,069 | 32,514 | 30,030 |
| 最終コード更新 | 2026年11月16日 | 2026年11月18日 | 2026年11月13日 | 2026年6月24日 | 2026年10月30日 |
| ライセンス | – | Apache-2.0 | MIT | MIT | AGPL-3.0 |
edisonmbli による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeCodexCursorGitHub CopilotWindsurf
提供元の README と repo のフォルダから判断
GitHub account edisonmbli (person), 12 years old
★ 482 stars, few users so far · code last changed 2026年11月16日
3 scripts that can run on a computer: scripts/check_contrast.py, scripts/emit_tokens.py, scripts/generate_palette.py
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 6a69966 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
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 skills/refactoring-ui folder again. The ZIP must have a refactoring-ui folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick refactoring-ui.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 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
この文をコピーして 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
Claude Code を開き直し、/refactoring-ui と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
コマンドを確認中 · 確認が通るとコピーボタンが出ます
提供元の README から引用。提供元のコードをダウンロードして実行します
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
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
refactoring-ui フォルダを ~/.agents/skills/refactoring-ui に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、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 は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
この文をコピーして 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
Cursor の Agent チャットで / を入力し refactoring-ui を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Skill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · 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 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: refactoring-ui
description: Design rulebook and diagnostic layer for web UI, distilled from Refactoring UI by Adam Wathan and Steve Schoger. Use when building a new page or component, refining UI that looks off or amateurish, running a design review, or establishing design tokens (color shades, type scale, spacing scale, elevation, radius). Covers visual hierarchy, layout and spacing, typography, color and contrast, depth and shadows, images, and finishing touches, with Tailwind mappings throughout. Also triggers on non-English requests for the same things - for example Chinese: 页面/界面设计, 样式调整, UI 太丑, 设计评审, 视觉层级, 配色, 对比度, 间距, 排版, 阴影, 空状态, 设计规范, 设计系统. Not for backend logic, copy editing, or changes with no visual surface.
---
# Refactoring UI
## What this skill is
This skill is the **constraint and diagnosis layer** for interface work. It supplies the rules a design must satisfy and finds where a design breaks them.
It is deliberately **not a generator of aesthetics**. When a design-generation capability is present (a Design mode, `frontend-design`, a canvas tool), that capability decides what the interface *looks like*; this skill decides what it must *obey*, and afterwards checks whether it did. See [Composing with design generators](#composing-with-design-generators).
The rules come from a book whose authors went on to build Tailwind CSS. Its scales are Tailwind's defaults, so the path from principle to code is unusually short.
## Step 0 — Detect before you decide
**Never make a design judgment before running this.** It takes one pass and prevents the two worst failure modes: fighting an existing design system, and emitting code the project can't use.
Detect and state briefly:
1. **Framework** — React/Vue/Svelte/plain HTML; SSR or SPA.
2. **Tailwind, and which major version.** v4 declares theme in CSS via `@theme`; v3 uses `tailwind.config.js`. Check `package.json`, then look for `@import "tailwindcss"` (v4) vs `@tailwind base` (v3).
3. **Existing design tokens** — CSS custom properties, a theme object, a `tokens.json`, a `theme/` directory.
4. **Component library** — shadcn/ui, MUI, Ant Design, Chakra, Radix. These carry their own token contracts — for shadcn/ui, load `16-component-libraries.md` before writing or editing any component.
5. **Dark mode** — present, planned, or absent.
**The prime directive that follows from this: an existing system always wins.** Where the project has a system, translate the book's principles into that system's vocabulary. Where it has none, propose one. Never overwrite, never silently migrate, never add a build-time dependency the user didn't ask for.
## Reading the reference files
The reference files mix two kinds of content, and confusing them is the main way this skill can do damage. The notation keeps them apart.
**Invariants — the book's actual rules.** In every `Values` block, **bold numbers are invariants**: font weights 400/500 and 600/700, a maximum of three text colors, one primary action per page, 45–75 characters per line, 4.5:1 and 3:1 contrast, no two scale steps closer than 25%, hue rotation capped at 20–30°, five elevation levels. These do not vary by project. Apply them as written.
**Illustrative choices — everything else.** Unbolded values in `Values`, and every size, spacing and color in a code example, are one valid instance of the rule, not the required answer.
**Colors in examples are always placeholders**, written in braces so they cannot be pasted verbatim:
| Placeholder | Resolves to |
|---|---|
| `{primary}` | the project's primary/brand ramp |
| `{neutral}` | the project's grey ramp — `gray`, `slate`, `zinc`, `stone`, or a custom one |
| `{danger}` | the project's destructive ramp |
| `{accent}` | a semantic accent ramp (warning, success, info) |
`bg-{primary}-600` means "the 600 stop of whatever this project's primary is." Never emit a brace into real code, and never substitute Tailwind's own default palette names unless Step 0 confirmed the project actually uses them. Defaulting to indigo and gray because the examples showed them is the single most recognizable tell of machine-generated UI.
**Resolution order for any concrete value:**
1. A token that already exists in the project (found in Step 0).
2. A token generated by Workflow A in this session.
3. The book's default scale from the relevant reference file — and say that you fell back to it.
If none of the three yields a value, that gap is itself a finding: the project needs a token before this decision can be made consistently.
## Route by intent
| The user is asking to… | Workflow | Load |
|---|---|---|
| set up a theme, palette, design system, "we have no design standards" | **A · Tokens** | `11-design-tokens.md` |
| build a new page, screen, component, feature UI | **B · Build** | `12-component-recipes.md` + lens refs as needed |
| improve / clean up / "make this look better" / "this looks off" | **C · Refine** | `13-audit-rubric.md`, then lens refs |
| review, critique, "what's wrong with this", pre-launch check | **D · Audit** | `13-audit-rubric.md` + `14-antipatterns.md` |
| understand a specific principle, "why does this look bad" | **Explain** | the single relevant lens ref |
Intent is often mixed. "Build me a settings page in this app that has no design system" is A then B. Run them in order and say so.
## The Twelve Laws
These apply to every task. They are the highest-cost rules to violate and need no reference lookup.
1. **Hierarchy is the job.** Making something look designed is mostly about making importance visible — not about styling. A flat wall of equally-weighted content reads as noise no matter how good the colors are. `§2.1`
2. **Emphasize by de-emphasizing.** When the primary element won't stand out, soften what competes with it rather than shouting louder. `§2.4`
3. **Every value comes from a system.** Font sizes, spacing, colors, shadows, radii, border widths — all chosen from a predefined scale. No hand-tuned one-offs, no arbitrary values. `§1.5 §3.2 §4.1`
4. **Start with too much white space and remove it.** Space added until something stops looking bad always undershoots. `§3.1`
5. **Space around a group must exceed space within it.** This one rule fixes most "why does this look confusing" problems. `§3.6`
6. **Size is not the only lever.** Use weight and color. Two weights (400/500 and 600/700) and three text colors (dark / grey / lighter grey) carry almost all UI hierarchy. Never go below 400 for UI text. `§2.2`
7. **Never put grey text on a colored background.** The effect you want is reduced contrast, not greyness. Hand-pick a color at the background's hue with adjusted saturation and lightness. Not white-at-lower-opacity. `§2.3`
8. **Semantics are secondary to hierarchy.** One primary action per page, a couple of secondary, a few tertiary. A destructive action is not automatically a loud one. `§2.8`
9. **Choose elements semantically, style them hierarchically.** An `h1` is a document-structure decision, not a font-size decision. Section titles usually behave as labels and should be small. `§2.6`
10. **Light comes from above.** Raised = lighter top edge plus a small, sharp shadow below. Inset = shadow at the top, lighter bottom edge. Everything about depth follows from this. `§6.1`
11. **Text measures 45–75 characters (20–35em).** Line-height rises with line length (1.5 narrow → 2 wide) and falls as font size grows (large headlines can sit at 1). `§4.3 §4.5`
12. **Never rely on color alone.** Color supports a signal the design already carries some other way. `§5.7`
## Workflow A · Tokens
Establishing a design system where none exists, or filling gaps in a partial one.
1. **Interview.** Load `11-design-tokens.md` and run its question script — at most four rounds, batched, every question skippable. If the user says "just pick for me," take the documented defaults and go straight to step 2.
2. **Generate.** Run `scripts/generate_palette.py` for each color ramp. The b質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。