[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAG56BY751664XM7EC6H5F":3,"skill-same:01M7FAG56BY751664XM7EC6H5F":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7FAG56BY751664XM7EC6H5F","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmake-interfaces-feel-better\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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":24,"description":7},{"origin":25},"community","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fmake-interfaces-feel-better",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill make-interfaces-feel-better",{"tool":40,"command":41},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill make-interfaces-feel-better",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill make-interfaces-feel-better","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fmake-interfaces-feel-better\u002FSKILL.md",true,[],[49,56,61,68,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]