[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70D0MGWS9BNNWCBG2PYRVXZ":3,"skill-same:01M70D0MGWS9BNNWCBG2PYRVXZ":76},{"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":29,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M70D0MGWS9BNNWCBG2PYRVXZ","make-interfaces-feel-better",null,"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\u002Fexit 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.","EthanYoQ\u002FSkill-hub","EthanYoQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257484394?v=4","01M70C9QKWR1YS0S7V26DNB18H","Ethan","01M70C9QMER047R5ANZZA6KC2P",11,"MIT","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fmake-interfaces-feel-better\u002F1f53c813f78de5f9\u002Fmake-interfaces-feel-better\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[],"2026-11-10 10:12:30",false,"---\nname: make-interfaces-feel-better\ndescription: 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\u002Fexit 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.\n---\n\n# Details that make interfaces feel better\n\nGreat 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.\n\n## Quick Reference\n\n| Category | When to Use |\n| --- | --- |\n| [Typography](typography.md) | Text wrapping, font smoothing, tabular numbers |\n| [Surfaces](surfaces.md) | Border radius, optical alignment, shadows, image outlines, hit areas |\n| [Animations](animations.md) | Interruptible animations, enter\u002Fexit transitions, icon animations, scale on press |\n| [Performance](performance.md) | Transition specificity, `will-change` usage |\n\n## Core Principles\n\n### 1. Concentric Border Radius\n\nOuter radius = inner radius + padding. Mismatched radii on nested elements is the most common thing that makes interfaces feel off.\n\n### 2. Optical Over Geometric Alignment\n\nWhen geometric centering looks off, align optically. Buttons with icons, play triangles, and asymmetric icons all need manual adjustment.\n\n### 3. Shadows Over Borders\n\nLayer multiple transparent `box-shadow` values for natural depth. Shadows adapt to any background; solid borders don't.\n\n### 4. Interruptible Animations\n\nUse CSS transitions for interactive state changes — they can be interrupted mid-animation. Reserve keyframes for staged sequences that run once.\n\n### 5. Split and Stagger Enter Animations\n\nDon't animate a single container. Break content into semantic chunks and stagger each with ~100ms delay.\n\n### 6. Subtle Exit Animations\n\nUse a small fixed `translateY` instead of full height. Exits should be softer than enters.\n\n### 7. Contextual Icon Animations\n\nAnimate 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.\n\n### 8. Font Smoothing\n\nApply `-webkit-font-smoothing: antialiased` to the root layout on macOS for crisper text.\n\n### 9. Tabular Numbers\n\nUse `font-variant-numeric: tabular-nums` for any dynamically updating numbers to prevent layout shift.\n\n### 10. Text Wrapping\n\nUse `text-wrap: balance` on headings. Use `text-wrap: pretty` for body text to avoid orphans.\n\n### 11. Image Outlines\n\nAdd 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.\n\n### 12. Scale on Press\n\nA 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.\n\n### 13. Skip Animation on Page Load\n\nUse `initial={false}` on `AnimatePresence` to prevent enter animations on first render. Verify it doesn't break intentional entrance animations.\n\n### 14. Never Use `transition: all`\n\nAlways specify exact properties: `transition-property: scale, opacity`. Tailwind's `transition-transform` covers `transform, translate, scale, rotate`.\n\n### 15. Use `will-change` Sparingly\n\nOnly for `transform`, `opacity`, `filter` — properties the GPU can composite. Never use `will-change: all`. Only add when you notice first-frame stutter.\n\n### 16. Minimum Hit Area\n\nInteractive 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.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Same border radius on parent and child | Calculate `outerRadius = innerRadius + padding` |\n| Icons look off-center | Adjust optically with padding or fix SVG directly |\n| Hard borders between sections | Use layered `box-shadow` with transparency |\n| Jarring enter\u002Fexit animations | Split, stagger, and keep exits subtle |\n| Numbers cause layout shift | Apply `tabular-nums` |\n| Heavy text on macOS | Apply `antialiased` to root |\n| Animation plays on page load | Add `initial={false}` to `AnimatePresence` |\n| `transition: all` on elements | Specify exact properties |\n| First-frame animation stutter | Add `will-change: transform` (sparingly) |\n| Tiny hit areas on small controls | Extend with pseudo-element to 40×40px |\n\n## Review Output Format\n\nAlways 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:\" \u002F \"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.\n\n### Example\n\n#### Concentric border radius\n| Before | After |\n| --- | --- |\n| `rounded-xl` on card + `rounded-xl` on inner button (`p-2`) | `rounded-2xl` on card (`12 + 8`), `rounded-lg` on inner button |\n| `border-radius: 16px` on both nested surfaces | Outer `24px`, inner `16px` with `8px` padding |\n\n#### Tabular numbers\n| Before | After |\n| --- | --- |\n| `\u003Cspan>{count}\u003C\u002Fspan>` on animated counter | `\u003Cspan className=\"tabular-nums\">{count}\u003C\u002Fspan>` |\n| Default numerals on timer | Added `font-variant-numeric: tabular-nums` to root |\n\n#### Scale on press\n| Before | After |\n| --- | --- |\n| `\u003Cbutton className=\"...\">` | Added `active:scale-[0.96] transition-transform` |\n| `scale(0.9)` on press | Raised to `scale(0.96)` — anything below `0.95` feels exaggerated |\n\nRows 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.\n\n## Review Checklist\n\n- [ ] Nested rounded elements use concentric border radius\n- [ ] Icons are optically centered, not just geometrically\n- [ ] Shadows used instead of borders where appropriate\n- [ ] Enter animations are split and staggered\n- [ ] Exit animations are subtle\n- [ ] Dynamic numbers use tabular-nums\n- [ ] Font smoothing is applied\n- [ ] Headings use text-wrap: balance\n- [ ] Images have subtle outlines\n- [ ] Buttons use scale on press where appropriate\n- [ ] AnimatePresence uses `initial={false}` for default-state elements\n- [ ] No `transition: all` — only specific properties\n- [ ] `will-change` only on transform\u002Fopacity\u002Ffilter, never `all`\n- [ ] Interactive elements have at least 40×40px hit area\n\n## Reference Files\n\n- [typography.md](typography.md) — Text wrapping, font smoothing, tabular numbers\n- [surfaces.md](surfaces.md) — Border radius, optical alignment, shadows, image outlines\n- [animations.md](animations.md) — Interruptible animations, enter\u002Fexit transitions, icon animations, scale on press\n- [performance.md](performance.md) — Transition specificity, `will-change` usage\n","# Details that make interfaces feel better\n\nGreat 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.\n\n## Quick Reference\n\n| Category | When to Use |\n| --- | --- |\n| [Typography](typography.md) | Text wrapping, font smoothing, tabular numbers |\n| [Surfaces](surfaces.md) | Border radius, optical alignment, shadows, image outlines, hit areas |\n| [Animations](animations.md) | Interruptible animations, enter\u002Fexit transitions, icon animations, scale on press |\n| [Performance](performance.md) | Transition specificity, `will-change` usage |\n\n## Core Principles\n\n### 1. Concentric Border Radius\n\nOuter radius = inner radius + padding. Mismatched radii on nested elements is the most common thing that makes interfaces feel off.\n\n### 2. Optical Over Geometric Alignment\n\nWhen geometric centering looks off, align optically. Buttons with icons, play triangles, and asymmetric icons all need manual adjustment.\n\n### 3. Shadows Over Borders\n\nLayer multiple transparent `box-shadow` values for natural depth. Shadows adapt to any background; solid borders don't.\n\n### 4. Interruptible Animations\n\nUse CSS transitions for interactive state changes — they can be interrupted mid-animation. Reserve keyframes for staged sequences that run once.\n\n### 5. Split and Stagger Enter Animations\n\nDon't animate a single container. Break content into semantic chunks and stagger each with ~100ms delay.\n\n### 6. Subtle Exit Animations\n\nUse a small fixed `translateY` instead of full height. Exits should be softer than enters.\n\n### 7. Contextual Icon Animations\n\nAnimate 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.\n\n### 8. Font Smoothing\n\nApply `-webkit-font-smoothing: antialiased` to the root layout on macOS for crisper text.\n\n### 9. Tabular Numbers\n\nUse `font-variant-numeric: tabular-nums` for any dynamically updating numbers to prevent layout shift.\n\n### 10. Text Wrapping\n\nUse `text-wrap: balance` on headings. Use `text-wrap: pretty` for body text to avoid orphans.\n\n### 11. Image Outlines\n\nAdd 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.\n\n### 12. Scale on Press\n\nA 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.\n\n### 13. Skip Animation on Page Load\n\nUse `initial={false}` on `AnimatePresence` to prevent enter animations on first render. Verify it doesn't break intentional entrance animations.\n\n### 14. Never Use `transition: all`\n\nAlways specify exact properties: `transition-property: scale, opacity`. Tailwind's `transition-transform` covers `transform, translate, scale, rotate`.\n\n### 15. Use `will-change` Sparingly\n\nOnly for `transform`, `opacity`, `filter` — properties the GPU can composite. Never use `will-change: all`. Only add when you notice first-frame stutter.\n\n### 16. Minimum Hit Area\n\nInteractive 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.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Same border radius on parent and child | Calculate `outerRadius = innerRadius + padding` |\n| Icons look off-center | Adjust optically with padding or fix SVG directly |\n| Hard borders between sections | Use layered `box-shadow` with transparency |\n| Jarring enter\u002Fexit animations | Split, stagger, and keep exits subtle |\n| Numbers cause layout shift | Apply `tabular-nums` |\n| Heavy text on macOS | Apply `antialiased` to root |\n| Animation plays on page load | Add `initial={false}` to `AnimatePresence` |\n| `transition: all` on elements | Specify exact properties |\n| First-frame animation stutter | Add `will-change: transform` (sparingly) |\n| Tiny hit areas on small controls | Extend with pseudo-element to 40×40px |\n\n## Review Output Format\n\nAlways 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:\" \u002F \"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.\n\n### Example\n\n#### Concentric border radius\n| Before | After |\n| --- | --- |\n| `rounded-xl` on card + `rounded-xl` on inner button (`p-2`) | `rounded-2xl` on card (`12 + 8`), `rounded-lg` on inner button |\n| `border-radius: 16px` on both nested surfaces | Outer `24px`, inner `16px` with `8px` padding |\n\n#### Tabular numbers\n| Before | After |\n| --- | --- |\n| `\u003Cspan>{count}\u003C\u002Fspan>` on animated counter | `\u003Cspan className=\"tabular-nums\">{count}\u003C\u002Fspan>` |\n| Default numerals on timer | Added `font-variant-numeric: tabular-nums` to root |\n\n#### Scale on press\n| Before | After |\n| --- | --- |\n| `\u003Cbutton className=\"...\">` | Added `active:scale-[0.96] transition-transform` |\n| `scale(0.9)` on press | Raised to `scale(0.96)` — anything below `0.95` feels exaggerated |\n\nRows 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.\n\n## Review Checklist\n\n- [ ] Nested rounded elements use concentric border radius\n- [ ] Icons are optically centered, not just geometrically\n- [ ] Shadows used instead of borders where appropriate\n- [ ] Enter animations are split and staggered\n- [ ] Exit animations are subtle\n- [ ] Dynamic numbers use tabular-nums\n- [ ] Font smoothing is applied\n- [ ] Headings use text-wrap: balance\n- [ ] Images have subtle outlines\n- [ ] Buttons use scale on press where appropriate\n- [ ] AnimatePresence uses `initial={false}` for default-state elements\n- [ ] No `transition: all` — only specific properties\n- [ ] `will-change` only on transform\u002Fopacity\u002Ffilter, never `all`\n- [ ] Interactive elements have at least 40×40px hit area\n\n## Reference Files\n\n- [typography.md](typography.md) — Text wrapping, font smoothing, tabular numbers\n- [surfaces.md](surfaces.md) — Border radius, optical alignment, shadows, image outlines\n- [animations.md](animations.md) — Interruptible animations, enter\u002Fexit transitions, icon animations, scale on press\n- [performance.md](performance.md) — Transition specificity, `will-change` usage\n",{"name":5,"description":7},"mine","1e7390741dffd3d5041fca4ebc056071ee3ba137","archives\u002Fuser-installed-skills\u002Fmake-interfaces-feel-better\u002F1f53c813f78de5f9\u002Fmake-interfaces-feel-better",5,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub","https:\u002F\u002Fgithub.com\u002FEthanYoQ","www.orz.md","Part Marketer, Part AI Explorer.","2026-11-07 14:52:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add EthanYoQ\u002FSkill-hub --skill make-interfaces-feel-better",{"tool":50,"command":51},"bunx","bunx skills add EthanYoQ\u002FSkill-hub --skill make-interfaces-feel-better",{"tool":53,"command":54},"pnpm","pnpm dlx skills add EthanYoQ\u002FSkill-hub --skill make-interfaces-feel-better","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fmake-interfaces-feel-better\u002F1f53c813f78de5f9\u002Fmake-interfaces-feel-better\u002FSKILL.md",true,[58,64,68,72],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"animations.md","REFERENCE","参考文档",11092,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fmake-interfaces-feel-better\u002F1f53c813f78de5f9\u002Fmake-interfaces-feel-better\u002Fanimations.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"performance.md",2884,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fmake-interfaces-feel-better\u002F1f53c813f78de5f9\u002Fmake-interfaces-feel-better\u002Fperformance.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"surfaces.md",7284,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fmake-interfaces-feel-better\u002F1f53c813f78de5f9\u002Fmake-interfaces-feel-better\u002Fsurfaces.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"typography.md",3799,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fmake-interfaces-feel-better\u002F1f53c813f78de5f9\u002Fmake-interfaces-feel-better\u002Ftypography.md",[77,105,136,160,178,193],{"skillNo":78,"name":79,"nameZh":6,"description":80,"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":84,"publishedAt":30},"01M713CBDSYARG4PXFXK2R2NNN","xhs-pharma-social-listening","Run evidence-disciplined Xiaohongshu social listening for foreign pharma employee pain points. Use when the user asks to collect and analyze notes\u002Fcomments about pharma companies, aliases, roles, compliance, medical affairs, or AI topics, then produce a cited and scored sampled-insight report. Includes independent-evidence counting, MediaCrawler batch collection, and CAPTCHA\u002F461 fallback to Agent Reach\u002FOpenCLI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fxhs-pharma-social-listening\u002FSKILL.md",[83],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"social","xhs pharma social listening","social listening","xhs","medical","counting","when","collection","batch","analyze","notes","run","opencli","fallback","captcha","agent reach","evidence","for","collect","produce",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":117,"publishedAt":30},"01M713C8Q76ZP0WXXBRAFKS6EE","healthcare-phi-compliance","Protected Health Information (PHI) and Personally Identifiable Information (PII) compliance patterns for healthcare applications. Covers data classification, access control, audit trails, encryption, and common leak vectors. Use when code touches PHI or PII in a healthcare system, or when auditing access control, audit trails, or leak vectors.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-phi-compliance\u002FSKILL.md",[111,112],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[118,119,120,121,122,123,124,125,91,126,127,128,129,130,131,132,102,133,134,135],"healthcare","phi","compliance","healthcare phi compliance","pii","compliance patterns","information","access","encryption","code","common","audit","data","patterns","Access Control","system","applications","Auditing Access Control",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":30},"01M713C5R2GE43X45T2K75TB76","healthcare-eval-harness","Patient safety evaluation harness for healthcare application deployments. Automated test suites for CDSS accuracy, PHI exposure, clinical workflow integrity, and integration compliance. Blocks deployments on safety failures. Use when a healthcare deployment must be gated on patient-safety tests for CDSS accuracy, PHI exposure, and workflow integrity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-eval-harness\u002FSKILL.md",[142],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[118,144,145,146,147,148,149,91,150,151,152,153,119,102,154,155,156,157,158,159],"eval","harness","healthcare eval harness","eval harness","clinical","patient","workflow","Evaluation","Safety","integrity","deployment","accuracy","tests","deployments","use","super",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":30},"01M713C2J17S91VYR7A8M696VR","healthcare-emr-patterns","EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-emr-patterns\u002FSKILL.md",[166],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[118,168,131,169,170,89,148,171,91,172,173,174,152,130,175,176,177,102,134,158],"EMR","healthcare emr patterns","decision","workflows","support","clinical decision support","features","ui","as","development",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":30},"01M713BZERTXV0N8X6SW9DDVWZ","healthcare-cdss-patterns","Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows. Use when building clinical decision support — drug interaction checks, dose validation, clinical scoring, or alert severity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-cdss-patterns\u002FSKILL.md",[184],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[118,131,186,170,148,168,171,91,187,188,172,173,189,177,133,190,158,191,159,192],"healthcare cdss patterns","scoring","interaction","severity","classification","alert","decision support",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":200,"publishedAt":30},"01M713BVK3PQR7V4ZKYGMWMXJD","dxy-task-clarify","用户的请求含糊、缺背景、缺资料说明、缺读者或用途时使用。先用少量带选项的追问把任务问清楚，写成任务卡，用户确认后再执行。尤其适用于医生、科研人员和药企各岗位的工作，例如「帮我分析一下这些数据」「帮我准备明天的拜访」「写个总结」「做个 PPT」「回一下这封邮件」「整理一下会议纪要」「整理一下这些文献」「帮我准备下周的讲课」「写个病例汇报」「帮我写个提示词」。用户说「先问我」「帮我理清需求」「我不知道怎么描述」「我不会问 AI」时也使用。用途、资料、读者都已说清的请求，纯翻译，以及写代码、改代码，不使用。","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fdxy-task-clarify\u002FSKILL.md",[199],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[201,202,203,204,205,206,207,208],"clarify","dxy task clarify","task","pptx","整理","翻译","数据","总结"]