菜单
Use this skill when UI text is vague, generic, missing, or confusing, including buttons, errors, empty states, loading messages, success feedback, and recovery guidance. Do not use for long-form marketing copy, PRDs, or product positioning that belongs to growth-launch-pack or requirements-griller.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this whenever a PR has a Vercel preview URL and needs browser QA against acceptance criteria — happy path, errors, empty states, responsive behavior, a11y basics — even if the user just says "check the preview". Requires a preview URL. NOT for release/deploy-readiness checks (no preview needed there) — use deploy-ready.
Plan and split work into parallel worktree sessions. Use whenever the user wants to work on multiple tasks at once, mentions parallel sessions, worktrees, "split this up", "dispatch", or lists several independent tasks for one work session.
Use this skill when implementing or reviewing UI that needs semantic HTML, keyboard navigation, focus management, ARIA labels, color contrast, reduced motion, forms, modals, or public-facing pages. Do not use as a standalone product-planning or backend workflow; pair it with design-system-ui, responsive-ui, or vercel-preview-qa when broader UI review is needed.
Use this skill when working across client, agency, consulting, or personal projects where code, data, credentials, prompts, or reusable patterns could leak between contexts. Do not use for ordinary single-project work with no cross-client or cross-workspace boundary risk.
Use this skill when creating components, implementing Figma designs, cleaning inconsistent styling, adding or reviewing tokens, spacing, typography, or component variants. Do not use for backend work, feature scoping, or visual QA that requires a live preview instead of design-system decisions.
Use this skill when importing ChatGPT or Claude exports, old Notion databases, local notes, or messy knowledge dumps into a durable knowledge system after redaction, deduplication, and classification. Do not use for live project planning, raw unredacted client data, or content that should remain out of Notion.
| name | ui-copy |
| description | Use this skill when UI text is vague, generic, missing, or confusing, including buttons, errors, empty states, loading messages, success feedback, and recovery guidance. Do not use for long-form marketing copy, PRDs, or product positioning that belongs to growth-launch-pack or requirements-griller. |
Interface copy that helps users: buttons, errors, empty states, success feedback, loading messages.
Replace generic or confusing UI text with specific, helpful copy. Every string the user reads should help them understand what's happening or what to do next.
Before UI work or review, read rules/ui.md and apply the project’s responsive, accessibility, component-state, and design-token expectations.
# Copy audit — [screen/flow]
| Location | Current text | Problem | Suggested |
|---|---|---|---|
| [Save button] | "Submit" | generic verb | "Save changes" |
| [Empty list] | "No data" | no next action | "No projects yet. Create your first one." |
| [Error toast] | "Error 500" | raw code, no recovery | "Couldn't save — check your connection and retry." |
design-system-ui — copy is part of the componentaccessibility-ui — error messages need ARIA live regionsgrowth-launch-pack — landing page copy follows positioningDeveloper language in UI — "null reference exception" in a user-facing error. Catch and translate to something helpful.
"Are you sure?" without consequences — Users click "yes" reflexively. Show what they're about to lose.
Optimistic copy that lies — A toast says "Saved!" the instant the button is clicked, before the request resolves. When the save then fails, the user has already navigated away believing it worked. Confirm success only on the actual success response; show a pending state in between.