[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DB2T1KJ75K7ZXR7GA866P8":3,"skill-same:01M7DB2T1KJ75K7ZXR7GA866P8":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7DB2T1KJ75K7ZXR7GA866P8","make-interfaces-feel-better",null,"Apply concrete design-engineering details that make interfaces feel polished. Use when reviewing or improving UI spacing, typography, borders, shadows, motion, hit areas, icons, text wrapping, and interaction states.","MoradDev\u002Fskills-unified","MoradDev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F72839584?v=4","01M7DASN3HYHFBYW4ZNMPTHQ63","01M7DASN4N6P4P9WMEFRE2V0TF",2,"MIT","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fmake-interfaces-feel-better\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: make-interfaces-feel-better\ndescription: Apply concrete design-engineering details that make interfaces feel polished. Use when reviewing or improving UI spacing, typography, borders, shadows, motion, hit areas, icons, text wrapping, and interaction states.\nmetadata:\n  origin: community\n---\n\n# Make Interfaces Feel Better\n\nUse this skill for the small design-engineering details that compound into a\nmore polished interface.\n\nSource: salvaged from stale community PR #1659 by `linus707`.\n\n## When to Use\n\n- The user says the UI feels off, flat, generic, cramped, jumpy, or unfinished.\n- You are building controls, cards, lists, dashboards, navigation, forms, or\n  toolbars.\n- A component needs hover, active, focus, enter, exit, loading, or empty states.\n- A frontend review needs specific before\u002Fafter recommendations.\n\n## Core Principles\n\n### Concentric Radius\n\nFor nearby nested rounded surfaces:\n\n```text\nouter radius = inner radius + padding\n```\n\nIf padding is large, treat layers as separate surfaces instead of forcing the\nmath. The point is optical coherence, not formula worship.\n\n### Optical Alignment\n\nGeometric centering is not always visual centering. Icon buttons, play\ntriangles, arrows, stars, and asymmetric icons often need a small offset. Fix the\nSVG when possible; otherwise adjust with a pixel-level margin or padding change.\n\n### Shadows And Borders\n\nUse borders for separation and focus rings. Use layered shadows when a card,\nbutton, dropdown, or popover needs depth. Shadows should be transparent and\nsubtle enough to work across backgrounds.\n\n### Text Wrapping\n\n- Use `text-wrap: balance` on headings and short titles.\n- Use `text-wrap: pretty` on short-to-medium body text, captions, descriptions,\n  and list items.\n- Avoid both on long prose, code, and preformatted content.\n- Use `font-variant-numeric: tabular-nums` for counters, timers, prices, tables,\n  and other updating numbers.\n\n### Font Smoothing\n\nOn macOS, apply antialiased font smoothing at the root layout when the project\ndoes not already do so:\n\n```css\nhtml {\n  -webkit-font-smoothing: antialiased;\n  -moz-osx-font-smoothing: grayscale;\n}\n```\n\n### Image Outlines\n\nImages often need a subtle inset outline so their edges do not blur into the\nsurface.\n\n```css\nimg {\n  outline: 1px solid rgba(0, 0, 0, 0.1);\n  outline-offset: -1px;\n}\n\n@media (prefers-color-scheme: dark) {\n  img {\n    outline-color: rgba(255, 255, 255, 0.1);\n  }\n}\n```\n\nUse neutral black or white alpha outlines. Do not tint image outlines with the\nbrand palette.\n\n### Motion\n\nUse CSS transitions for interactive state changes because they can retarget\nwhen the user changes intent mid-motion. Reserve keyframes for staged\none-shot entrances or loading sequences.\n\nGood motion defaults:\n\n- Enter: combine opacity, small `translateY`, and optionally blur.\n- Exit: shorter and quieter than enter, usually 150ms.\n- Press: `scale(0.96)` for tactile buttons, with a way to disable it when the\n  movement distracts.\n- Icon swaps: cross-fade with opacity, scale, and blur instead of instant\n  visibility toggles.\n\n### Transition Scope\n\nNever use `transition: all`. Specify the changed properties:\n\n```css\n.button {\n  transition-property: transform, background-color, box-shadow;\n  transition-duration: 150ms;\n  transition-timing-function: ease-out;\n}\n```\n\nUse `will-change` only for first-frame stutter on compositor-friendly\nproperties such as `transform`, `opacity`, and `filter`. Never use\n`will-change: all`.\n\n### Hit Areas\n\nInteractive controls should have at least a 40x40px hit area, ideally 44x44px\nwhere the layout allows it. Expand with a pseudo-element when the visible icon\nis smaller, but do not let expanded hit areas overlap.\n\n## Review Output\n\nWhen reviewing a UI polish pass, report concrete changes in before\u002Fafter rows:\n\n| Principle | Before | After |\n| --- | --- | --- |\n| Concentric radius | Same radius on parent and child | Parent radius accounts for padding |\n| Tabular numbers | Counter shifts as digits change | Counter uses `tabular-nums` |\n| Transition scope | `transition: all` | Explicit transition properties |\n\nInclude file paths and properties when they are not obvious from the snippets.\nOmit principles that you checked but did not change.\n\n## Checklist\n\n- Nested rounded elements are optically coherent.\n- Icons are visually centered.\n- Buttons, cards, and popovers use borders or shadows for the right reason.\n- Headings and short text avoid awkward wrapping.\n- Dynamic numbers use tabular numerals.\n- Images have neutral outlines where needed.\n- Enter and exit animations are split, subtle, and interruptible where\n  appropriate.\n- Buttons have tactile active states without exaggerated motion.\n- `transition: all` and `will-change: all` are absent.\n- Small controls still have usable hit areas.\n","# Make Interfaces Feel Better\n\nUse this skill for the small design-engineering details that compound into a\nmore polished interface.\n\nSource: salvaged from stale community PR #1659 by `linus707`.\n\n## When to Use\n\n- The user says the UI feels off, flat, generic, cramped, jumpy, or unfinished.\n- You are building controls, cards, lists, dashboards, navigation, forms, or\n  toolbars.\n- A component needs hover, active, focus, enter, exit, loading, or empty states.\n- A frontend review needs specific before\u002Fafter recommendations.\n\n## Core Principles\n\n### Concentric Radius\n\nFor nearby nested rounded surfaces:\n\n```text\nouter radius = inner radius + padding\n```\n\nIf padding is large, treat layers as separate surfaces instead of forcing the\nmath. The point is optical coherence, not formula worship.\n\n### Optical Alignment\n\nGeometric centering is not always visual centering. Icon buttons, play\ntriangles, arrows, stars, and asymmetric icons often need a small offset. Fix the\nSVG when possible; otherwise adjust with a pixel-level margin or padding change.\n\n### Shadows And Borders\n\nUse borders for separation and focus rings. Use layered shadows when a card,\nbutton, dropdown, or popover needs depth. Shadows should be transparent and\nsubtle enough to work across backgrounds.\n\n### Text Wrapping\n\n- Use `text-wrap: balance` on headings and short titles.\n- Use `text-wrap: pretty` on short-to-medium body text, captions, descriptions,\n  and list items.\n- Avoid both on long prose, code, and preformatted content.\n- Use `font-variant-numeric: tabular-nums` for counters, timers, prices, tables,\n  and other updating numbers.\n\n### Font Smoothing\n\nOn macOS, apply antialiased font smoothing at the root layout when the project\ndoes not already do so:\n\n```css\nhtml {\n  -webkit-font-smoothing: antialiased;\n  -moz-osx-font-smoothing: grayscale;\n}\n```\n\n### Image Outlines\n\nImages often need a subtle inset outline so their edges do not blur into the\nsurface.\n\n```css\nimg {\n  outline: 1px solid rgba(0, 0, 0, 0.1);\n  outline-offset: -1px;\n}\n\n@media (prefers-color-scheme: dark) {\n  img {\n    outline-color: rgba(255, 255, 255, 0.1);\n  }\n}\n```\n\nUse neutral black or white alpha outlines. Do not tint image outlines with the\nbrand palette.\n\n### Motion\n\nUse CSS transitions for interactive state changes because they can retarget\nwhen the user changes intent mid-motion. Reserve keyframes for staged\none-shot entrances or loading sequences.\n\nGood motion defaults:\n\n- Enter: combine opacity, small `translateY`, and optionally blur.\n- Exit: shorter and quieter than enter, usually 150ms.\n- Press: `scale(0.96)` for tactile buttons, with a way to disable it when the\n  movement distracts.\n- Icon swaps: cross-fade with opacity, scale, and blur instead of instant\n  visibility toggles.\n\n### Transition Scope\n\nNever use `transition: all`. Specify the changed properties:\n\n```css\n.button {\n  transition-property: transform, background-color, box-shadow;\n  transition-duration: 150ms;\n  transition-timing-function: ease-out;\n}\n```\n\nUse `will-change` only for first-frame stutter on compositor-friendly\nproperties such as `transform`, `opacity`, and `filter`. Never use\n`will-change: all`.\n\n### Hit Areas\n\nInteractive controls should have at least a 40x40px hit area, ideally 44x44px\nwhere the layout allows it. Expand with a pseudo-element when the visible icon\nis smaller, but do not let expanded hit areas overlap.\n\n## Review Output\n\nWhen reviewing a UI polish pass, report concrete changes in before\u002Fafter rows:\n\n| Principle | Before | After |\n| --- | --- | --- |\n| Concentric radius | Same radius on parent and child | Parent radius accounts for padding |\n| Tabular numbers | Counter shifts as digits change | Counter uses `tabular-nums` |\n| Transition scope | `transition: all` | Explicit transition properties |\n\nInclude file paths and properties when they are not obvious from the snippets.\nOmit principles that you checked but did not change.\n\n## Checklist\n\n- Nested rounded elements are optically coherent.\n- Icons are visually centered.\n- Buttons, cards, and popovers use borders or shadows for the right reason.\n- Headings and short text avoid awkward wrapping.\n- Dynamic numbers use tabular numerals.\n- Images have neutral outlines where needed.\n- Enter and exit animations are split, subtle, and interruptible where\n  appropriate.\n- Buttons have tactile active states without exaggerated motion.\n- `transition: all` and `will-change: all` are absent.\n- Small controls still have usable hit areas.\n",{"name":5,"metadata":23,"description":7},{"origin":24},"community","main","7542b2fc80051758dfb288b450cb344d3bdfca35","curation\u002Fskills\u002Fmake-interfaces-feel-better",0,"https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified","https:\u002F\u002Fgithub.com\u002FMoradDev","2026-11-07 21:53:24",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MoradDev\u002Fskills-unified --skill make-interfaces-feel-better",{"tool":38,"command":39},"bunx","bunx skills add MoradDev\u002Fskills-unified --skill make-interfaces-feel-better",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MoradDev\u002Fskills-unified --skill make-interfaces-feel-better","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fmake-interfaces-feel-better\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7DB9J6N2PSGECQ6FTWW7B2H","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7DB9CCWT4YW7B791QN43E3Q","vue-patterns","Vue.js 3 Composition API patterns, component architecture, reactivity best practices, Pinia state management, Vue Router navigation, and Nuxt SSR patterns. Activates for Vue, Nuxt, Vite, or Pinia projects. Use when building or reviewing Vue 3, Nuxt, or Pinia code — Composition API, reactivity, or router navigation.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fvue-patterns\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7DB976FM2CAWT807EA36MXM","vite-patterns","Vite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fvite-patterns\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7DB93JZRAWFB5QHH0C8DZ8N","using-agent-skills","Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fusing-agent-skills\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7DB8YYW1PEDS7H2AA86TE2E","ui-demo","Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fui-demo\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7DB8RPQPW2R6GKJW618VDST","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices. Use when building or reviewing SwiftUI views, @Observable state, navigation, or render performance.","https:\u002F\u002Fgithub.com\u002FMoradDev\u002Fskills-unified\u002Fblob\u002Fmain\u002Fcuration\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[]]