跳到正文
cccskills
免费在 GitHub 公开

make-interfaces-feel-better

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

中文简介正在准备中。当前显示原文说明。

try-works/role-model星标 117(GitHub 117 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(5)

  • SKILL.md7.6 KB
  • animations.md10.8 KB
  • performance.md2.8 KB
  • surfaces.md7.1 KB
  • typography.md3.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Details that make interfaces feel better

Great interfaces rarely come from a single thing. It's usually a collection of small details that compound into a great experience. Apply these principles when building or reviewing UI code.

Quick Reference

CategoryWhen to Use
TypographyText wrapping, font smoothing, tabular numbers
SurfacesBorder radius, optical alignment, shadows, image outlines, hit areas
AnimationsInterruptible animations, enter/exit transitions, icon animations, scale on press
PerformanceTransition specificity, will-change usage

Core Principles

1. Concentric Border Radius

Outer radius = inner radius + padding. Mismatched radii on nested elements is the most common thing that makes interfaces feel off.

2. Optical Over Geometric Alignment

When geometric centering looks off, align optically. Buttons with icons, play triangles, and asymmetric icons all need manual adjustment.

3. Shadows Over Borders

Layer multiple transparent box-shadow values for natural depth. Shadows adapt to any background; solid borders don't.

4. Interruptible Animations

Use CSS transitions for interactive state changes — they can be interrupted mid-animation. Reserve keyframes for staged sequences that run once.

5. Split and Stagger Enter Animations

Don't animate a single container. Break content into semantic chunks and stagger each with ~100ms delay.

6. Subtle Exit Animations

Use a small fixed translateY instead of full height. Exits should be softer than enters.

7. Contextual Icon Animations

Animate icons with opacity, scale, and blur instead of toggling visibility. Use exactly these values: scale from 0.25 to 1, opacity from 0 to 1, blur from 4px to 0px. If the project has motion or framer-motion in package.json, use transition: { type: "spring", duration: 0.3, bounce: 0 } — bounce must always be 0. If no motion library is installed, keep both icons in the DOM (one absolute-positioned) and cross-fade with CSS transitions using cubic-bezier(0.2, 0, 0, 1) — this gives both enter and exit animations without any dependency.

8. Font Smoothing

Apply -webkit-font-smoothing: antialiased to the root layout on macOS for crisper text.

9. Tabular Numbers

Use font-variant-numeric: tabular-nums for any dynamically updating numbers to prevent layout shift.

10. Text Wrapping

Use text-wrap: balance on headings. Use text-wrap: pretty for body text to avoid orphans.

11. Image Outlines

Add a subtle 1px outline with low opacity to images for consistent depth. The color must be pure black in light mode (rgba(0, 0, 0, 0.1)) and pure white in dark mode (rgba(255, 255, 255, 0.1)) — never a near-black like slate, zinc, or any tinted neutral. A tinted outline picks up the surface color underneath it and reads as dirt on the image edge.

12. Scale on Press

A subtle scale(0.96) on click gives buttons tactile feedback. Always use 0.96. Never use a value smaller than 0.95 — anything below feels exaggerated. Add a static prop to disable it when motion would be distracting.

13. Skip Animation on Page Load

Use initial={false} on AnimatePresence to prevent enter animations on first render. Verify it doesn't break intentional entrance animations.

14. Never Use transition: all

Always specify exact properties: transition-property: scale, opacity. Tailwind's transition-transform covers transform, translate, scale, rotate.

15. Use will-change Sparingly

Only for transform, opacity, filter — properties the GPU can composite. Never use will-change: all. Only add when you notice first-frame stutter.

16. Minimum Hit Area

Interactive elements need at least 40×40px hit area. Extend with a pseudo-element if the visible element is smaller. Never let hit areas of two elements overlap.

Common Mistakes

MistakeFix
Same border radius on parent and childCalculate outerRadius = innerRadius + padding
Icons look off-centerAdjust optically with padding or fix SVG directly
Hard borders between sectionsUse layered box-shadow with transparency
Jarring enter/exit animationsSplit, stagger, and keep exits subtle
Numbers cause layout shiftApply tabular-nums
Heavy text on macOSApply antialiased to root
Animation plays on page loadAdd initial={false} to AnimatePresence
transition: all on elementsSpecify exact properties
First-frame animation stutterAdd will-change: transform (sparingly)
Tiny hit areas on small controlsExtend with pseudo-element to 40×40px

Review Output Format

Always present changes as a markdown table with Before and After columns. Include every change you made — not just a subset. Never list findings as separate "Before:" / "After:" lines outside of a table. Group changes by principle using a heading above each table, and keep each row focused on a single diff so the reader can scan the whole list quickly.

Example

Concentric border radius

BeforeAfter
rounded-xl on card + rounded-xl on inner button (p-2)rounded-2xl on card (12 + 8), rounded-lg on inner button
border-radius: 16px on both nested surfacesOuter 24px, inner 16px with 8px padding

Tabular numbers

BeforeAfter
<span>{count}</span> on animated counter<span className="tabular-nums">{count}</span>
Default numerals on timerAdded font-variant-numeric: tabular-nums to root

Scale on press

BeforeAfter
<button className="...">Added active:scale-[0.96] transition-transform
scale(0.9) on pressRaised to scale(0.96) — anything below 0.95 feels exaggerated

Rows should cite the specific file and the specific property that changed when it isn't obvious from the snippet. If a principle was reviewed but nothing needed to change, omit that table entirely — empty tables add noise.

Review Checklist

  • Nested rounded elements use concentric border radius
  • Icons are optically centered, not just geometrically
  • Shadows used instead of borders where appropriate
  • Enter animations are split and staggered
  • Exit animations are subtle
  • Dynamic numbers use tabular-nums
  • Font smoothing is applied
  • Headings use text-wrap: balance
  • Images have subtle outlines
  • Buttons use scale on press where appropriate
  • AnimatePresence uses initial={false} for default-state elements
  • No transition: all — only specific properties
  • will-change only on transform/opacity/filter, never all
  • Interactive elements have at least 40×40px hit area

Reference Files

  • typography.md — Text wrapping, font smoothing, tabular numbers
  • surfaces.md — Border radius, optical alignment, shadows, image outlines
  • animations.md — Interruptible animations, enter/exit transitions, icon animations, scale on press
  • performance.md — Transition specificity, will-change usage

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable execution, queues, retries, observability, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

中文简介正在准备中。当前显示原文说明。

try-works/role-model1172026年10月25日 更新

Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

中文简介正在准备中。当前显示原文说明。

try-works/role-model1172026年10月25日 更新

Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deliverability, SPF/DKIM/DMARC, wrangler email setup, MCP email tools, or when a coding agent needs to send emails. Even for simple requests like "add email to my Worker" — this skill has critical config details.

中文简介正在准备中。当前显示原文说明。

try-works/role-model1172026年10月25日 更新

Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs.

中文简介正在准备中。当前显示原文说明。

try-works/role-model1172026年10月25日 更新

Plans migrations from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, SWG, or SASE stacks to Cloudflare One. Use for migration assessments, policy mapping, rollout plans, and parity/gap analysis.

中文简介正在准备中。当前显示原文说明。

try-works/role-model1172026年10月25日 更新

Review the changed lines of a single file in a pull request for bugs, correctness, error handling, security, and maintainability, and return structured findings.

中文简介正在准备中。当前显示原文说明。

try-works/role-model1172026年10月25日 更新

查看 try-works 的全部技能

报告此技能的问题