[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ST15FSPN2WB4T98BP4HXE":3,"skill-same:01M78ST15FSPN2WB4T98BP4HXE":68},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78ST15FSPN2WB4T98BP4HXE","better-ui",null,"Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter\u002Fexit animations, choosing or reviewing icons, or any visual detail work. Triggers on UI polish, design details, \"make it feel better\", \"feels off\", stagger animations, border radius, optical alignment, image outlines, box shadows, icons, icon stroke weight, icon states, motion restraint.","fjooord\u002Fgamecube-decomp-harness","fjooord","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44952366?v=4","01M75A80KS3BN58VMNBG7AXAM1","Ford Lascari","01M75A80MCVXVSXGREY7Y9Z8H5",7,"MIT","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: better-ui\ndescription: Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter\u002Fexit animations, choosing or reviewing icons, or any visual detail work. Triggers on UI polish, design details, \"make it feel better\", \"feels off\", stagger animations, border radius, optical alignment, image outlines, box shadows, icons, icon stroke weight, icon states, motion restraint.\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\nWhen reviewing, slow the interface down: replay motion at 10% speed in the browser's Animations panel and walk every state: hover, focus, active, loading, empty. What feels off at 10% speed is what's subtly wrong at full speed.\n\nPreserve the project's component library, tokens, and density. Match its established motion language except where a principle below prescribes an exact interaction pattern.\n\nTypography (text wrapping, font rendering, tabular numbers, spacing) is covered by the `better-typography` skill; use that for anything text-related. Accessibility (hit areas, focus states, keyboard support, ARIA, reduced motion) is covered by the `better-accessibility` skill. Layout structure (grouping, spacing between sections, breakpoints, spatial RTL) is covered by the `better-layout` skill.\n\n## Quick Reference\n\n| Category | When to Use |\n| --- | --- |\n| [Surfaces](surfaces.md) | Border radius, optical alignment, shadows, image outlines |\n| [Animations](animations.md) | Interruptible animations, enter\u002Fexit transitions, icon animations, scale on press, motion restraint |\n| [Icons](icons.md) | Icon stroke weight, states via `currentColor`, outline vs fill, sizing, RTL flipping |\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 for Elevation, Borders for Structure\n\nFor buttons, cards, and containers whose border exists only to create depth, prefer layered transparent `box-shadow` values. Keep borders that communicate structure or state: dividers, layout separators, and selected or focus states.\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\nFor an infrequent staged entrance where sequence helps communicate hierarchy, break content into semantic chunks and stagger them by ~100ms instead of animating one container. Do not stagger routine, high-frequency interactions.\n\n### 6. Subtle Exit Animations\n\nUse a small fixed `translateY` instead of full height. Exits should be softer than enters. Use `ease-out` for both enter and exit transitions.\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`, match that package's import path (or the established nearby imports when both exist) and 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. 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 (`oklch(0 0 0 \u002F 0.1)`) and pure white in dark mode (`oklch(1 0 0 \u002F 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### 9. 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### 10. 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### 11. Never Use `transition: all`\n\nAlways specify exact properties: `transition-property: scale, opacity`. Tailwind's `transition-transform` covers `transform, translate, scale, rotate`.\n\n### 12. Use `will-change` Sparingly\n\nOnly for `transform`, `opacity`, `filter`, the properties the GPU can composite. Never use `will-change: all`. Only add when you notice first-frame stutter.\n\n### 13. Match Icon Stroke to Text Weight\n\nAn icon next to text carries the text's optical weight: `1.5px` stroke beside regular (400) text, `2px` beside semibold (600). One stroke weight per icon set; never mix libraries on one surface.\n\n### 14. One SVG, Recolored per State\n\nIcons use `currentColor` and get their states (hover, selected, disabled) from CSS color and opacity, never from separate assets. Outline variant is the default; fill variant marks the active state.\n\n### 15. Motion Restraint\n\nNo custom animation on high-frequency interactions: the attention cost repeats on every trigger. Motion is never the only feedback channel; every animated state change also needs a static cue (color, icon, label).\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Same border radius on closely nested parent and child | Calculate `outerRadius = innerRadius + padding` |\n| Icons look off-center | Adjust optically with padding or fix SVG directly |\n| Border used only to fake elevation | Use layered `box-shadow` with transparency; keep structural and state borders |\n| Jarring staged entrance or contextual exit | Stagger infrequent entrances and keep context-preserving exits subtle |\n| Stateful icon or toggle animates its default state on page load | Add `initial={false}` to that `AnimatePresence`; preserve intentional page entrances |\n| `transition: all` on elements | Specify exact properties |\n| First-frame animation stutter | Add `will-change: transform` (sparingly) |\n| Hairline icon beside bold text | Match the stroke width to the text weight |\n| Separate icon assets per state | One `currentColor` SVG, states via CSS |\n| Filled icons everywhere | Outline as default, fill only for the active state |\n| Entrance animation on every hover or keystroke | Instant feedback or ≤150ms opacity\u002Fcolor transition |\n\n## Review Output Format\n\nUse this format only when the user asks for a standalone UI-polish review. When `better-interface` orchestrates the review, provide domain evidence and findings to that skill and let its output format, severity scale, consolidation rules, cap, and verdict take precedence.\n\nPresent the standalone review in two parts.\n\n### Findings\n\nGroup all confirmed findings by principle. Use a markdown table with **Severity**, **Location**, **Before**, **After**, and **Why** columns. Never use separate \"Before:\" \u002F \"After:\" lines.\n\n- **Severity**: `HIGH` makes an interaction misleading, unresponsive, or repeatedly disruptive; `MEDIUM` creates a noticeable craft or consistency problem; `LOW` is isolated polish.\n- **Location**: cite `path\u002Fto\u002Ffile:line`. If the artifact has no source files, cite the exact screen and component instead.\n- **Before \u002F After**: show the current implementation and an actionable replacement.\n- **Why**: name the violated principle and explain how it affects the interface.\n\nConsolidate a repeated systemic issue into one row and list every affected location. Omit principles with no findings.\n\n### Example\n\n#### Concentric border radius\n| Severity | Location | Before | After | Why |\n| --- | --- | --- | --- | --- |\n| LOW | `src\u002FCard.tsx:28` | `rounded-xl` on card + `rounded-xl` on inner button (`p-2`) | `rounded-2xl` on card (`8 + 8 = 16`), `rounded-lg` on inner button | Nested corners should be concentric |\n| LOW | `src\u002Fcard.css:11` | `border-radius: 16px` on both nested surfaces | Outer `24px`, inner `16px` with `8px` padding | Equal nested radii make the inner surface look pinched |\n\n#### Scale on press\n| Severity | Location | Before | After | Why |\n| --- | --- | --- | --- | --- |\n| LOW | `src\u002FButton.tsx:19` | `\u003Cbutton className=\"...\">` | Add `active:scale-[0.96] transition-transform` | Press feedback makes the control feel responsive |\n| MEDIUM | `src\u002Fbutton.css:24` | `scale(0.9)` on press | Raise to `scale(0.96)` | Anything below `0.95` feels exaggerated |\n\n### Verification and Verdict\n\nAfter the findings:\n\n1. **Verification**: list the exact checks run and their observed results. Walk every relevant state and inspect motion at 10% speed when animation is involved. If a check was not run, state what still needs verification.\n2. **Verdict**: `Block` if any `HIGH` finding remains, `Needs changes` if only `MEDIUM` or `LOW` findings remain, and `Approve` only when no actionable findings remain.\n\nWhen there are no findings, omit the tables, state \"No actionable UI-polish findings\", report verification, and end with `Approve`.\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\nWhen reviewing, slow the interface down: replay motion at 10% speed in the browser's Animations panel and walk every state: hover, focus, active, loading, empty. What feels off at 10% speed is what's subtly wrong at full speed.\n\nPreserve the project's component library, tokens, and density. Match its established motion language except where a principle below prescribes an exact interaction pattern.\n\nTypography (text wrapping, font rendering, tabular numbers, spacing) is covered by the `better-typography` skill; use that for anything text-related. Accessibility (hit areas, focus states, keyboard support, ARIA, reduced motion) is covered by the `better-accessibility` skill. Layout structure (grouping, spacing between sections, breakpoints, spatial RTL) is covered by the `better-layout` skill.\n\n## Quick Reference\n\n| Category | When to Use |\n| --- | --- |\n| [Surfaces](surfaces.md) | Border radius, optical alignment, shadows, image outlines |\n| [Animations](animations.md) | Interruptible animations, enter\u002Fexit transitions, icon animations, scale on press, motion restraint |\n| [Icons](icons.md) | Icon stroke weight, states via `currentColor`, outline vs fill, sizing, RTL flipping |\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 for Elevation, Borders for Structure\n\nFor buttons, cards, and containers whose border exists only to create depth, prefer layered transparent `box-shadow` values. Keep borders that communicate structure or state: dividers, layout separators, and selected or focus states.\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\nFor an infrequent staged entrance where sequence helps communicate hierarchy, break content into semantic chunks and stagger them by ~100ms instead of animating one container. Do not stagger routine, high-frequency interactions.\n\n### 6. Subtle Exit Animations\n\nUse a small fixed `translateY` instead of full height. Exits should be softer than enters. Use `ease-out` for both enter and exit transitions.\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`, match that package's import path (or the established nearby imports when both exist) and 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. 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 (`oklch(0 0 0 \u002F 0.1)`) and pure white in dark mode (`oklch(1 0 0 \u002F 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### 9. 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### 10. 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### 11. Never Use `transition: all`\n\nAlways specify exact properties: `transition-property: scale, opacity`. Tailwind's `transition-transform` covers `transform, translate, scale, rotate`.\n\n### 12. Use `will-change` Sparingly\n\nOnly for `transform`, `opacity`, `filter`, the properties the GPU can composite. Never use `will-change: all`. Only add when you notice first-frame stutter.\n\n### 13. Match Icon Stroke to Text Weight\n\nAn icon next to text carries the text's optical weight: `1.5px` stroke beside regular (400) text, `2px` beside semibold (600). One stroke weight per icon set; never mix libraries on one surface.\n\n### 14. One SVG, Recolored per State\n\nIcons use `currentColor` and get their states (hover, selected, disabled) from CSS color and opacity, never from separate assets. Outline variant is the default; fill variant marks the active state.\n\n### 15. Motion Restraint\n\nNo custom animation on high-frequency interactions: the attention cost repeats on every trigger. Motion is never the only feedback channel; every animated state change also needs a static cue (color, icon, label).\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Same border radius on closely nested parent and child | Calculate `outerRadius = innerRadius + padding` |\n| Icons look off-center | Adjust optically with padding or fix SVG directly |\n| Border used only to fake elevation | Use layered `box-shadow` with transparency; keep structural and state borders |\n| Jarring staged entrance or contextual exit | Stagger infrequent entrances and keep context-preserving exits subtle |\n| Stateful icon or toggle animates its default state on page load | Add `initial={false}` to that `AnimatePresence`; preserve intentional page entrances |\n| `transition: all` on elements | Specify exact properties |\n| First-frame animation stutter | Add `will-change: transform` (sparingly) |\n| Hairline icon beside bold text | Match the stroke width to the text weight |\n| Separate icon assets per state | One `currentColor` SVG, states via CSS |\n| Filled icons everywhere | Outline as default, fill only for the active state |\n| Entrance animation on every hover or keystroke | Instant feedback or ≤150ms opacity\u002Fcolor transition |\n\n## Review Output Format\n\nUse this format only when the user asks for a standalone UI-polish review. When `better-interface` orchestrates the review, provide domain evidence and findings to that skill and let its output format, severity scale, consolidation rules, cap, and verdict take precedence.\n\nPresent the standalone review in two parts.\n\n### Findings\n\nGroup all confirmed findings by principle. Use a markdown table with **Severity**, **Location**, **Before**, **After**, and **Why** columns. Never use separate \"Before:\" \u002F \"After:\" lines.\n\n- **Severity**: `HIGH` makes an interaction misleading, unresponsive, or repeatedly disruptive; `MEDIUM` creates a noticeable craft or consistency problem; `LOW` is isolated polish.\n- **Location**: cite `path\u002Fto\u002Ffile:line`. If the artifact has no source files, cite the exact screen and component instead.\n- **Before \u002F After**: show the current implementation and an actionable replacement.\n- **Why**: name the violated principle and explain how it affects the interface.\n\nConsolidate a repeated systemic issue into one row and list every affected location. Omit principles with no findings.\n\n### Example\n\n#### Concentric border radius\n| Severity | Location | Before | After | Why |\n| --- | --- | --- | --- | --- |\n| LOW | `src\u002FCard.tsx:28` | `rounded-xl` on card + `rounded-xl` on inner button (`p-2`) | `rounded-2xl` on card (`8 + 8 = 16`), `rounded-lg` on inner button | Nested corners should be concentric |\n| LOW | `src\u002Fcard.css:11` | `border-radius: 16px` on both nested surfaces | Outer `24px`, inner `16px` with `8px` padding | Equal nested radii make the inner surface look pinched |\n\n#### Scale on press\n| Severity | Location | Before | After | Why |\n| --- | --- | --- | --- | --- |\n| LOW | `src\u002FButton.tsx:19` | `\u003Cbutton className=\"...\">` | Add `active:scale-[0.96] transition-transform` | Press feedback makes the control feel responsive |\n| MEDIUM | `src\u002Fbutton.css:24` | `scale(0.9)` on press | Raise to `scale(0.96)` | Anything below `0.95` feels exaggerated |\n\n### Verification and Verdict\n\nAfter the findings:\n\n1. **Verification**: list the exact checks run and their observed results. Walk every relevant state and inspect motion at 10% speed when animation is involved. If a check was not run, state what still needs verification.\n2. **Verdict**: `Block` if any `HIGH` finding remains, `Needs changes` if only `MEDIUM` or `LOW` findings remain, and `Approve` only when no actionable findings remain.\n\nWhen there are no findings, omit the tables, state \"No actionable UI-polish findings\", report verification, and end with `Approve`.\n",{"name":5,"description":7},"main","e7e6fb660782e780949acacded7546400b54f2ae","ref\u002Fjakubkrehel skills main skills\u002Fbetter-ui",3,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness","https:\u002F\u002Fgithub.com\u002Ffjooord","https:\u002F\u002Flascari.ai\u002F","2026-11-06 04:39:50",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add fjooord\u002Fgamecube-decomp-harness --skill better-ui",{"tool":38,"command":39},"bunx","bunx skills add fjooord\u002Fgamecube-decomp-harness --skill better-ui",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fjooord\u002Fgamecube-decomp-harness --skill better-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",113,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"animations.md",13214,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002Fanimations.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"icons.md",4422,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002Ficons.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"performance.md",3014,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002Fperformance.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"surfaces.md",6518,"https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-ui\u002Fsurfaces.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78ST6YK3EBH0GKFER68ZV8V","better-writing","UX writing and interface copy, from voice and button labels to error messages and empty states. Use when writing or reviewing any user-facing text: button and link labels, form errors, placeholders, settings labels, onboarding flows, notifications, or empty states. Triggers on UX writing, microcopy, interface copy, product copy, copywriting, button labels, link text, error messages, empty states, placeholder text, settings labels, capitalization, title case, sentence case, voice and tone.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-writing\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78SSSVHD4MB3GWJFPHAR6NX","better-typography","Web typography from choosing fonts to spacing, wrapping and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, checking heading hierarchy, styling text in components, truncating text, styling underlines, selection, placeholders or carets, or reviewing frontend code for typography. Triggers on typography, fonts, font formats, woff2, variable fonts, font-weight, opentype, font-feature-settings, letter-spacing, line-height, type scale, heading hierarchy, heading levels, tabular numbers, text-wrap, truncation, line clamp, underlines, text-decoration, text selection, iOS input zoom, font smoothing, text contrast, measure, line length, text-box, smart punctuation, drop cap.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-typography\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M78SSM8Z4ESHX0YA5GQSKREK","better-layout","Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-layout\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M78SSFS2YJ7CAJTS6PXA8YYY","better-interface","User-invoked, cross-discipline interface review that coordinates better-accessibility, better-layout, better-writing, better-typography, better-colors, and better-ui. Use when explicitly invoked for a holistic review of a screen, flow, feature, or product interface. Supports quick and full review modes. Triggers on better-interface, full interface review, holistic UI audit, cross-discipline design review, review the whole interface.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-interface\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M78SSB3HCMJVWVZYQ7QN5VPX","better-colors","OKLCH color space and color usage for web projects. Convert hex\u002Frgb\u002Fhsl to oklch, generate palettes, check contrast, handle gamut boundaries, theme with Tailwind v4, and apply color with meaning. Triggers on oklch, color conversion, palette generation, contrast ratio, gamut, display p3, design tokens, semantic color tokens, hue drift, chroma, dark mode colors, accent color, color meaning, light and dark appearance, increased contrast.","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-colors\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M78SS50WJGTS3AYGE4SRBNQK","better-accessibility","Accessibility engineering for product interfaces, from focus states and keyboard support to ARIA, forms, and screen readers. Use when building or reviewing UI components, modals, menus, forms, custom widgets, or when the user says \"make this accessible\" or reports keyboard or screen-reader issues. Triggers on accessibility, a11y, WCAG, aria, focus ring, focus-visible, focus trap, keyboard navigation, tab order, tabindex, screen reader, sr-only, aria-live, alt text, hit area, touch target, prefers-reduced-motion, autoplay, toast duration, skip link, semantic HTML, aria-label, form errors, disabled buttons, \"not keyboard accessible\".","https:\u002F\u002Fgithub.com\u002Ffjooord\u002Fgamecube-decomp-harness\u002Fblob\u002Fmain\u002Fref\u002Fjakubkrehel skills main skills\u002Fbetter-accessibility\u002FSKILL.md",[],[]]