菜单
While iterating on UI, do not waste time on tsc, lint, typecheck, format, full test suites, commit, or push until the user likes how it looks and works. Use for any UI/UX work, layout, redesign, Figma implementation, visual polish, "make it look right", or when they want to see the UI before cleanup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Polish your own diff by hand with KISS/DRY and local style — the pre-handoff pass, not a test run and not a subagent sweep. Use for /clean, "clean it up", "tidy this", and automatically before creating, updating, or automerging a PR or moving to the next one.
The general profile-driven perf loop for any language or runtime: baseline, profile, fix the real hot path, re-measure. Use for /perf, "this is slow", or optimization work.
Prove a visual change by looking at the rendered surface — screenshot it and compare to the reference before saying done. Use after any UI, layout, theme, or color change, or when the user says it still looks wrong or doesn't match.
Clear everything blocking an existing PR/MR from merging — rebase onto the default branch, get CI green, and resolve review threads (Copilot and human). Use for "rebase on main", "make CI green", "fix CI/CD", "address the reviews", "address Copilot", "review-loop", or "get this mergeable".
Maintainer triage on OTHER people's PRs/MRs — verdict of approve, supersede, or close, salvage with credit, close the cluster. Use for a review batch, a pasted Discord thread with a PR, or salvage/supersede/close asks. Not for your own PR (that's pr-ready).
Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff. Preserves any media already in the body. Use when the user says /pr-update, open a PR, update the PR, refresh the PR title/description, or wants the PR opener/manager flow.
| name | ui-only |
| description | While iterating on UI, do not waste time on tsc, lint, typecheck, format, full test suites, commit, or push until the user likes how it looks and works. Use for any UI/UX work, layout, redesign, Figma implementation, visual polish, "make it look right", or when they want to see the UI before cleanup. |
When you're changing how something looks or interacts: get the UI right first. Don't burn turns on tsc, lint, or commit until they say it's good.
Until they like the UI (or explicitly say to clean/commit):
tsc / typecheck / npm run build as a finish stepgit commit / git push / opening the PR as doneDev server, screenshots, and targeted runs needed to see or use the UI are fine. Don't start a dev server the user already has running — assume it's up unless told otherwise. Keep debug logging in place while something's still broken; remove it only once it works.
clean, commit, and do whatever else the repo needs.If you're not sure whether to keep iterating, ask.
Any UI surface (web, desktop, TUI). Skip for backend-only work.
For primitives and tokens, also use ui-system.