[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79PD2S3B4DH2R46XWDDZEG5":3,"skill-same:01M79PD2S3B4DH2R46XWDDZEG5":47},{"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":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79PD2S3B4DH2R46XWDDZEG5","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.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\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":24,"description":7},{"origin":25},"community","main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Fmake-interfaces-feel-better","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill make-interfaces-feel-better",{"tool":39,"command":40},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill make-interfaces-feel-better",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill make-interfaces-feel-better","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fmake-interfaces-feel-better\u002FSKILL.md",true,[],[48,54,60,66,72,78],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]