メニュー
UX audit + design spec for web apps. Use for usability reviews, accessibility checks, user flows, microcopy, wireframes, and implementation-ready acceptance criteria.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
| name | ux-webapp |
| description | UX audit + design spec for web apps. Use for usability reviews, accessibility checks, user flows, microcopy, wireframes, and implementation-ready acceptance criteria. |
This skill helps you do high-quality UX work on web applications:
Use this skill when the user asks for:
Always attempt to see the actual UI before giving advice. Code alone is insufficient for UX evaluation.
If you have access to browser/chrome-tester MCP tools:
If you cannot capture screenshots yourself:
Do not hallucinate visual details. If you haven't seen it, say so.
Adapt recommendations to the type of product:
| Context | Pattern Preference | Delight Level | Examples |
|---|---|---|---|
| B2B / SaaS / Internal Tools | Conservative, conventional | Low | Admin dashboards, CRMs, dev tools |
| Consumer Apps | Balanced | Medium | Social apps, productivity, e-commerce |
| Marketing / Landing Pages | Creative, distinctive | High | Product launches, campaigns, portfolios |
Ask about context if unclear.
| Input | Action |
|---|---|
| Screenshots / URL / flow description | Quick UX Pass (default) or full audit if requested |
| Feature idea / problem statement only | Propose the flow + lightweight spec |
| Access to codebase | Capture screenshots first (if browser tools available), then Quick UX Pass |
| Browser tools available | Use them. Launch app, capture screenshots, then evaluate |
Default: Quick UX Pass. Only escalate when explicitly requested or clearly warranted.
| Format | When to Use | Output |
|---|---|---|
| Quick UX Pass (default) | "Review this", "Is this good?", "Quick feedback" | Top 5-10 issues with severity, rationale, and fixes |
| UX Audit | "Full audit", "Comprehensive review", complex multi-screen flows | Flow map + issue backlog + prioritized roadmap |
| Design Spec | "Write the spec", "Acceptance criteria", new feature design | Interaction rules, states, copy, criteria, analytics |
| Validation Plan | "Test plan", "How do we validate this?" | Usability test script + tasks + success criteria |
Escalation signals: User says "thorough", "comprehensive", "full", "deep dive", or task involves 5+ screens/states.
| ID | Location | Problem | Evidence | Principle | Sev | Impact | Confidence | Effort | Priority | Recommendation | Acceptance Criteria |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Login | Submit button disabled with no explanation | Users click repeatedly | H5 / L4 | 3 | 3 | 4 | 2 | 6.0 | Show helper text | Given incomplete form, When user views submit, Then helper shows required fields |
Severity Scale (0-4):
| File | Contents |
|---|---|
reference/HEURISTICS.md | Nielsen's 10 heuristics + cognitive laws + severity scale |
reference/CHECKLISTS.md | Forms, navigation, a11y, responsive checklists |
templates/UX_AUDIT.md | Audit output template |
templates/DESIGN_SPEC.md | Implementation spec template |
templates/USABILITY_TEST.md | User testing plan template |
When responding, always deliver:
