[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EC5GHTT4CMXDXKC84S9HCT":3,"skill-same:01M7EC5GHTT4CMXDXKC84S9HCT":55},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7EC5GHTT4CMXDXKC84S9HCT","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.","syedmehedihussain\u002Fcherry","syedmehedihussain","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F183754033?v=4","01M7EC34EA312J2XV37SD5C840","Syed Mehedi Hussain","01M7EC34EZR59ARY7C75C41EKJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fdesign\u002Fskills\u002Fmake-interfaces-feel-better\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fdesign\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":25,"description":7},{"origin":26},"community","main","adb38ff1e06b1bb57c84131717dd3d9c01292a8b","packages\u002Fdaemon\u002Fstages\u002Fdesign\u002Fskills\u002Fmake-interfaces-feel-better",0,"https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry","https:\u002F\u002Fsyedmehedihussain.github.io\u002Fcherry\u002F","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain","https:\u002F\u002Fsyedmehedihussain.codes\u002F","What should I say?","2026-11-10 02:42:31",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add syedmehedihussain\u002Fcherry --skill make-interfaces-feel-better",{"tool":43,"command":44},"bunx","bunx skills add syedmehedihussain\u002Fcherry --skill make-interfaces-feel-better",{"tool":46,"command":47},"pnpm","pnpm dlx skills add syedmehedihussain\u002Fcherry --skill make-interfaces-feel-better","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Fdesign\u002Fskills\u002Fmake-interfaces-feel-better\u002FSKILL.md",true,[51],{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE","许可证",1071,[56,64,72,80,88,96],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":20},"01M7ECBMEN6N02N2NGHMYTJTY1","verification-loop","Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fverification-loop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":20},"01M7ECBFBZ3GJEWJJHKRPCYX8J","e2e-testing","Playwright E2E testing patterns, Page Object Model, configuration, CI\u002FCD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fe2e-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fe2e-testing\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":20},"01M7ECB8WD04GN1SF0J7XM0252","browser-qa","Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP \u002F DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fbrowser-qa\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fbrowser-qa\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":20},"01M7ECB2QHYKHYT9EJV089FVT4","ai-regression-testing","Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fai-regression-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Ftesting\u002Fskills\u002Fai-regression-testing\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":20},"01M7ECAXS1W69TNH9MV1J1WHM2","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fstory-lifecycle\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fstory-lifecycle\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":20},"01M7ECAQVHTTS6M1T62XYAP9NP","intent-driven-development","Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security\u002Fdata\u002Fmigration\u002Fintegration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fintent-driven-development\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsyedmehedihussain\u002Fcherry\u002Fblob\u002Fmain\u002Fpackages\u002Fdaemon\u002Fstages\u002Frequirements\u002Fskills\u002Fintent-driven-development\u002FSKILL.md",[],[]]