HyperFrames by HeyGen
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
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
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
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.
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 refactoring-ui-skill | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 제작자 | edisonmbli | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 472 | 111,265 | 67,613 | 32,407 | 29,891 |
| 마지막 코드 변경 | 2026년 11월 16일 | 2026년 11월 17일 | 2026년 11월 13일 | 2026년 6월 24일 | 2026년 10월 30일 |
| 라이선스 | – | Apache-2.0 | MIT | MIT | AGPL-3.0 |
edisonmbli의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCodexCursorGitHub CopilotWindsurf
제작자 README와 repo 폴더 기준
GitHub account edisonmbli (person), 12 years old
★ 472 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질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.