Skip to content
Back to search

ui-ux-tips

SkillWorks with Claude CodeGitHub

Use when building, reviewing, or polishing any user-facing UI — web pages, admin dashboards, mobile screens, React/React Native/Tailwind/antd components, forms, menus, tables, cards, charts, dialogs, empty states, login/signup, pricing or landing pages — or when asked for a UI/UX review, design feedback, or to make a screen look or feel better.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/nguyentienloc--ui-ux-review/badge.svg)](/listings/nguyentienloc--ui-ux-review)

HTML

<a href="/listings/nguyentienloc--ui-ux-review"><img src="/api/listings/nguyentienloc--ui-ux-review/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/nguyentienloc/ui-ux-review.git ~/.claude/skills/ui-ux-tips

Then ask Claude Code for a UI/UX review, or to build/polish a screen — the skill triggers automatically.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 109 lines
  1. ---
  2. name: ui-ux-tips
  3. description: Use when building, reviewing, or polishing any user-facing UI — web pages, admin dashboards, mobile screens, React/React Native/Tailwind/antd components, forms, menus, tables, cards, charts, dialogs, empty states, login/signup, pricing or landing pages — or when asked for a UI/UX review, design feedback, or to make a screen look or feel better.
  4. ---
  5. # UI/UX Tips (uidesign.tips)
  6. ## Overview
  7. 66 practical tips from uidesign.tips (Jim Raptis) as a checklist. Generic reviews already catch the obvious things: a loud delete button, Yes/No dialogs, status shown only by color. They miss the specific rules: bar vs line chart, steppers, empty-state templates, card buttons, radius math. **★ marks rules an unaided agent missed or contradicted in testing.** Treat them as must-check.
  8. Full text, examples and source URL per tip: `ui-tips.md` (39 UI tips) and `ux-tips.md` (27 UX tips) in this directory.
  9. ## How to apply
  10. - **Building UI:** write the screen, then walk every checklist section below whose element appears on it, and fix violations before you say you're done.
  11. - **Reviewing UI:** walk the same sections, including the ones that look fine at a glance. Each finding = line + the violated rule (tip name) + a concrete fix (classes, values, copy).
  12. - **Use the project's design system.** The tips decide *what* to do; the project's tokens, component library and existing screens decide *how*. Use the nearest existing token. Don't add new colors or libraries to satisfy a tip.
  13. ## Review deliverable: before/after HTML for approval
  14. A review of an existing screen ends with a before/after HTML page, every time. Make it without asking whether the user wants one. Implement only the items the user approves.
  15. 1. **Before = real screenshots.** Screenshot the real screen at the size users see, then crop one image per finding as JPEG. If the app points at production data, browse read-only and follow the project's production-safety rules.
  16. 2. **After = HTML in the real design system.** Read the real code first (theme colors, radius, font, icons, component patterns) and rebuild each fixed area at its native pixel size. A mockup that doesn't look like the real app gets rejected.
  17. 3. **One numbered section per finding**, in this order: title + priority tag, "Vấn đề / Đề xuất" (file:line + the tip applied), then **Trước** next to **Sau**. Add a second "Sau" for other states (with data, error) and label made-up numbers "minh họa". Keep numbers unique across pages so the user can reply "duyệt 1, 3, 7".
  18. 4. **Build** from `before-after/template.html`, then run `python3 -I before-after/build.py <template> <images_dir> <out.html>` to inline the crops. Keep each file under ~500 KB and split large reviews into one page per screen or tab.
  19. 5. **Check it renders before sending.** Open it in a browser, screenshot each section, and fix clipped frames or wrapped titles.
  20. 6. **Show it inline** if the chat can render HTML (e.g. an inline-visuals skill); otherwise give the file path. Close with how to approve by number.
  21. ## Checklist
  22. ### Hierarchy & typography
  23. - One primary CTA per view or section, and it's the most prominent element. Use the full brand color only on it and a few key elements. Use tints, shades or neutrals everywhere else.
  24. - Title heavier than the subtitle. Sizes on a ×1.25 scale (40 → 32 → 25.6 → 20px). Secondary text at lower contrast or opacity. Comfortable line-height on body text.
  25. - Left-align headers and text blocks. Don't center paragraphs.
  26. - Body text 500–700px wide (≈ `max-w-prose` / 65ch), never full-width.
  27. - Different element types must look different. Tags and badges never look like buttons.
  28. - Group related items. Separate groups with whitespace, or one divider *between sections*, never a divider under every item.
  29. - ★ Row of uneven items (logos, chips, tiles): give every item the width of the widest one. Equal gaps alone still look off.
  30. ### Color & state
  31. - Never use color alone. Pair it with text, an icon or a shape (status, validation, chart series).
  32. - Selected rows/items: change the background, not just the checkbox. Highlight the active nav/menu item.
  33. - To emphasize something (recommended plan) or de-emphasize it (dangerous action), change **≥2 traits**: color, size, elevation, button type, placement.
  34. ### Cards & shapes
  35. - ★ Nested rounded shapes: outer radius = 2 × inner radius (card 16px → image 8px).
  36. - ★ Rounded container: an edge next to non-round content (text, square icon) gets **2×** the padding of an edge next to round content (avatar, circle).
  37. - ★ Clickable card: show a visible button that names the action ("View stock"). Keep it even if the whole card is also a link, because hover effects alone don't signal clickability.
  38. - ★ Avatars: the container background equals the app background, plus a subtle border. Over a cover image, add a ring in the page background color (`ring-4 ring-white`). This keeps transparent PNG avatars looking right.
  39. ### Buttons, links & microcopy
  40. - ★ A standalone link outside the header, footer or body text should be rendered as a button.
  41. - Same action → same label and same style everywhere.
  42. - Button label = verb + object/outcome ("Send statement", "Create price list"). Never "Submit", "OK" or "Yes/No".
  43. - ★ For an ambiguous or high-stakes action, add one line saying what will and won't happen, next to or inside the button: "You won't be charged yet", "Customers aren't notified until you publish", "Record — we won't post it yet".
  44. - ★ Show the keyboard shortcut next to the button or menu item it triggers.
  45. ### Destructive actions
  46. - Never delete without a confirmation (inline or modal). Offer Undo when engineering allows.
  47. - On the page, make the dangerous action secondary to the default action (≥2 traits), e.g. red text on a secondary button, placed last. Group irreversible actions in a **Danger zone** with a red border. Each row: bold title + one-line consequence + a specific button ("Delete this warehouse").
  48. - In the confirm dialog, say what is lost. The confirm button repeats the action ("Delete warehouse") and may be solid red there. Cancel is the safe default.
  49. ### Forms & inputs
  50. - Placeholder = a format example, never a copy of the label: "+84 912 345 678", not "Enter phone number".
  51. - Constrain input with predefined values where possible (a country-code selector inside the phone field, selects, date pickers).
  52. - ★ Pick the control that fits the data. Small integers that are usually 1–3 (quantities) → a −/+ stepper, not a text or number box.
  53. - Option labels preview their value. Color options show a swatch plus the name; keep the name for color-blind users. Text-case options are written in their own case: lowercase / UPPERCASE / Title Case.
  54. ### Navigation & menus
  55. - ★ An icon before every menu item. Highlight the active item. Separate sections with whitespace. Put the destructive item last, set apart.
  56. - Don't put a promo or upsell in a slot users habitually tap for something else.
  57. ### Icons & tooltips
  58. - Give icons a short, subtle text label, always on mobile/touch. An icon-only button with a hover `title` isn't enough.
  59. - Touch screens have no hover: add a tappable (?) help icon next to the control for tooltip content.
  60. ### Charts
  61. - ★ Few discrete x-values (months, quarters, categories) → bar chart. Use a line chart only for continuous or dense series. A line through monthly totals implies data points you don't have; a smoothed `monotone` line is worse.
  62. ### Empty states, onboarding, upsell, permissions
  63. - ★ Empty state: offer ready-made templates or examples alongside "start from scratch", not just a create button.
  64. - ★ Onboarding: offer import/migration from what users use today (Excel/CSV, a competitor's export).
  65. - ★ Locked or paid feature: show the real UI blurred or locked under an upgrade overlay, not a plain text note.
  66. - ★ Before requesting permissions or OAuth scopes (e.g. "Connect Zalo OA"), say why each one is needed, and name any third-party constraint behind it.
  67. - Feature announcements can use the brand mascot instead of a plain notification. Easter eggs only work if users can discover them.
  68. ### Auth screens
  69. - Social login on top, email/password below. Always keep email/password for privacy-minded users.
  70. - Use the spare area of login and signup screens for product value: a product visual, or the testimonial closest to your value proposition.
  71. ### Landing, marketing & pricing pages
  72. - CTA above the fold, with one primary CTA in the hero. The header CTA adapts: new visitors see "Get started", signed-in users see "Open dashboard".
  73. - Let a glimpse of the next section show above the fold to prompt scrolling. Put a section's main CTA at the end of the Z-path (bottom-right).
  74. - Show the real product: mockups with an interactive feature picker, before/after against the old way, a product preview beside the closing CTA, a value calculator (time or money saved).
  75. - Social proof: people the audience knows or recognized experts; relatable faces whose gaze points at the CTA.
  76. - Use specific real numbers over round ones: "1,178 templates", not "1,000+".
  77. - Pricing: highlight the best/popular plan with ≥2 traits, and give each plan a distinct icon or persona illustration.
  78. - Personalize where it's cheap: the visitor's country, flag or name in demos and copy.
  79. - To be memorable: an unexpected headline, a distinctive interface, a mascot.
  80. ## Resolving conflicts
  81. | Tension | Resolution |
  82. |---|---|
  83. | "Use red for dangerous actions" vs "de-emphasize dangerous actions" | Do both. Red marks danger, but on the page the dangerous action is never the dominant control. Solid red only inside the confirm step. |
  84. | Whole card is a link vs explicit card button | Keep both. The visible button is required. |
  85. | Tip value vs project token (×1.25 scale, 2× radius) | Use the nearest existing token. Don't invent one-off values. |
README.md · README · 26 lines
  1. # ui-ux-tips — UI/UX review skill for Claude Code
  2. An agent skill that turns the 66 practical tips from [uidesign.tips](https://www.uidesign.tips) (Jim Raptis) into a checklist for building and reviewing user-facing UI: web pages, dashboards, mobile screens, forms, menus, tables, cards, charts, dialogs, empty states, auth and landing/pricing pages.
  3. Rules marked ★ are ones an unaided agent missed or contradicted in testing.
  4. ## Contents
  5. | File | What it is |
  6. |---|---|
  7. | `SKILL.md` | The checklist and how to apply it (build / review), plus conflict resolutions |
  8. | `ui-tips.md` | 39 UI tips — rule, why, details, source URL |
  9. | `ux-tips.md` | 27 UX tips — rule, why, details, source URL |
  10. | `before-after/` | Template + `build.py` to produce a single-file before/after HTML page for review findings |
  11. ## Install
  12. ```bash
  13. git clone https://github.com/nguyentienloc/ui-ux-review.git ~/.claude/skills/ui-ux-tips
  14. ```
  15. Then ask Claude Code for a UI/UX review, or to build/polish a screen — the skill triggers automatically.
  16. ## Credits
  17. Tips summarized from [uidesign.tips](https://www.uidesign.tips) by Jim Raptis. Each tip links back to its original page.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.