[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C534EXWB4P9151RNKRW03":3,"skill-same:01M73C534EXWB4P9151RNKRW03":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M73C534EXWB4P9151RNKRW03","ui-ux-design-intelligence",null,"Provides comprehensive UI\u002FUX design capabilities including design system creation, component design, visual hierarchy, and user-centered design principles. Use when: building design systems, creating visual designs, designing UI components, or establishing design specifications.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fui-ux-design-intelligence\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: ui-ux-design-intelligence\ndescription: >\n  Provides comprehensive UI\u002FUX design capabilities including design system creation,\n  component design, visual hierarchy, and user-centered design principles. Use when:\n  building design systems, creating visual designs, designing UI components, or establishing\n  design specifications.\nversion: 1.0.1\nscope: common\nstatus: active\nowner: pm\nlast_reviewed: 2026-09-06\nprerequisites: none\nrelates_to:\n  - skill: documentation-writing\n    type: follows\ngemini-parity: skip\nmetadata:\n  type: implementation\n  triggers:\n    - design system\n    - ui design\n    - ux design\n    - component design\n    - visual design\n    - design tokens\n    - interface design\n---\n\n## Context\n\nThis skill provides end-to-end UI\u002FUX design capabilities, from design system architecture through component specification. It combines design thinking, visual design principles, and systematic approaches to create cohesive, scalable user interfaces.\n\n## When to Use\n\n**Design System Creation:**\n- Trigger: \"Create design system\" or \"Establish design tokens\"\n- Use Case: Starting new project or redesigning existing system\n\n**Component Design:**\n- Trigger: \"Design component\" or \"Create UI element\"\n- Use Case: Building individual interface components with specifications\n\n**Visual Design:**\n- Trigger: \"Design interface\" or \"Create visual layout\"\n- Use Case: Creating screen designs, layouts, or visual compositions\n\n**Design Specification:**\n- Trigger: \"Specify design\" or \"Create design documentation\"\n- Use Case: Documenting design decisions for handoff to developers\n\n---\n\n## Execution Steps\n\n## Step 1: Design System Architecture\n\n**Purpose**: Establish foundational design system structure.\n\n**Design Token Definition**:\n1. **Color System**:\n   - Primary colors (brand colors)\n   - Secondary colors (supporting colors)\n   - Semantic colors (success, warning, error, info)\n   - Neutral colors (grays for text, backgrounds, borders)\n   - Define color values in HEX, RGB, HSL formats\n\n2. **Typography Scale**:\n   - Font families (primary, secondary, code)\n   - Type scale (heading sizes, body sizes, caption sizes)\n   - Font weights (light, regular, medium, semibold, bold)\n   - Line height ratios (body: 1.5-1.7, headings: 1.1-1.3)\n   - Letter spacing for different sizes\n\n3. **Spacing System**:\n   - Base unit (typically 4px or 8px)\n   - Spacing scale (4, 8, 12, 16, 24, 32, 48, 64, 96 pixels)\n   - Consistent padding and margins\n   - Component spacing rules\n\n4. **Border Radius**:\n   - Scale for corner radii (0, 4, 8, 16, 24 pixels)\n   - Usage guidelines for each radius size\n   - Special cases (circles, pills)\n\n5. **Shadows & Elevation**:\n   - Elevation levels (flat, raised, overlay, modal)\n   - Shadow definitions for each level\n   - Usage contexts\n\n**Output**: Design token documentation with all token categories\n\n---\n\n## Step 2: Component Design Principles\n\n**Purpose**: Create systematic approach to component design.\n\n**Component Design Process**:\n1. **Identify Component Purpose**:\n   - What user problem does it solve?\n   - In what contexts will it be used?\n   - What are the accessibility requirements?\n\n2. **Define Component States**:\n   - Default state\n   - Hover state\n   - Focus state (keyboard navigation)\n   - Active\u002Fpressed state\n   - Disabled state\n   - Error\u002Finvalid state\n\n3. **Design Component Variants**:\n   - Size variants (small, medium, large)\n   - Importance variants (primary, secondary, tertiary)\n   - Context variants (contained, outlined, text)\n\n4. **Specify Component Behavior**:\n   - Interaction patterns\n   - Animation transitions\n   - Responsive behavior\n   - Edge cases\n\n**Output**: Component specification sheet with all states and variants\n\n---\n\n## Step 3: Visual Hierarchy & Layout\n\n**Purpose**: Establish clear visual hierarchy and layout systems.\n\n**Hierarchy Principles**:\n1. **Size Hierarchy**:\n   - Establish clear size relationships (H1 > H2 > H3 > body)\n   - Use modular scale for consistent sizing\n   - Ensure visual distinction between levels\n\n2. **Color Hierarchy**:\n   - Primary actions: high contrast, prominent color\n   - Secondary actions: medium contrast, supporting color\n   - Tertiary actions: low contrast, minimal color\n   - De-emphasized actions: neutral\u002Fmonochrome\n\n3. **Spacing Hierarchy**:\n   - More whitespace = more importance\n   - Group related elements with less spacing\n   - Separate unrelated elements with more spacing\n   - Establish vertical rhythm\n\n4. **Layout Systems**:\n   - Grid system (columns, gutters, margins)\n   - Breakpoints for responsive design\n   - Container max-widths\n   - Component spacing rules\n\n**Output**: Layout system documentation with hierarchy guidelines\n\n---\n\n## Step 4: Accessibility & WCAG Compliance\n\n**Purpose**: Ensure designs meet accessibility standards.\n\n**Accessibility Checklist**:\n1. **Color Contrast**:\n   - Text contrast ratio: 4.5:1 (AA) for body text\n   - Large text contrast ratio: 3:1 (AA) for 18pt+\n   - Graphic contrast ratio: 3:1 (AA) for UI components\n   - Test with contrast checker tools\n\n2. **Touch Targets**:\n   - Practical baseline: 44×44 CSS pixels (from WCAG 2.5.5 Target Size, Level AAA)\n   - AA conformance minimum: 24×24 CSS pixels (WCAG 2.5.8, Level AA) — the 44px baseline exceeds it\n   - Recommended size: 48×48 CSS pixels (tokenized as `--target-size` in tokens.json)\n   - Spacing between touch targets: 8px minimum\n\n3. **Typography**:\n   - Base font size: 16px minimum (100%)\n   - Scalable text units (rem, em, %)\n   - Line height: 1.5-1.7 for body text\n   - Paragraph spacing: 1.5× line height\n\n4. **Keyboard Navigation**:\n   - Visible focus indicators\n   - Logical tab order\n   - Skip navigation links\n   - No keyboard traps\n\n5. **Screen Reader Support**:\n   - Semantic HTML elements\n   - ARIA labels where needed\n   - Alt text for images\n   - Meaningful link text\n\n**Output**: Accessibility compliance report with remediation steps\n\n---\n\n## Step 5: Design Documentation & Handoff\n\n**Purpose**: Create comprehensive design specifications for implementation.\n\n**Documentation Structure**:\n1. **Component Specification**:\n   - Component name and purpose\n   - Visual examples (all states and variants)\n   - Design tokens used\n   - Spacing and positioning\n   - Interaction behaviors\n   - Code examples (CSS, design tokens)\n\n2. **Layout Specifications**:\n   - Grid system documentation\n   - Responsive breakpoints\n   - Container behaviors\n   - Spacing utilities\n\n3. **Usage Guidelines**:\n   - When to use the component\n   - When NOT to use the component\n   - Do's and don'ts\n   - Common mistakes to avoid\n\n4. **Implementation Notes**:\n   - Technical considerations\n   - Browser compatibility notes\n   - Performance considerations\n   - Accessibility requirements\n\n**Output**: Complete design handoff package with specifications and examples\n\n---\n\n## Step 6: Design Quality Validation\n\n**Purpose**: Ensure design meets quality standards and best practices.\n\n**Validation Checklist**:\n- [ ] All design tokens defined and documented\n- [ ] Component states are complete (default, hover, focus, active, disabled)\n- [ ] Color contrast meets WCAG AA standards\n- [ ] Touch targets meet minimum size requirements\n- [ ] Typography uses proper hierarchy and scale\n- [ ] Layout follows grid system\n- [ ] Spacing follows spacing system\n- [ ] Components work responsively\n- [ ] Accessibility considerations addressed\n- [ ] Design documentation is complete\n- [ ] Implementation examples provided\n\n**Quality Gates**:\n1. **Design System Review**: All tokens defined systematically\n2. **Component Review**: All components have complete specifications\n3. **Accessibility Review**: WCAG AA compliance verified\n4. **Documentation Review**: Handoff documentation is complete\n\n**Output**: Design quality report with pass\u002Ffail status and recommendations\n\n---\n\n## Output Format\n\n**For Design System Creation**:\n- Complete design token system (color, typography, spacing, borders, shadows)\n- Design system documentation\n- Component library structure\n- Usage guidelines\n\n**For Component Design**:\n- Component specification sheet\n- Visual examples for all states and variants\n- Design token mappings\n- Implementation code examples\n- Accessibility compliance report\n\n**For Visual Design**:\n- Layout compositions\n- Visual hierarchy documentation\n- Responsive design specifications\n- Grid system documentation\n\n---\n\n## Best Practices\n\n**Design System Design**:\n✅ **Do**:\n- Start with tokens before components\n- Use systematic approaches (scales, ratios)\n- Document all decisions and rationale\n- Test with real content and scenarios\n- Iterate based on feedback\n\n❌ **Don't**:\n- Design components without system context\n- Skip documentation (\"self-documenting\" doesn't scale)\n- Ignore accessibility or responsive design\n- Create arbitrary values without system\n- Mix metaphors or paradigms\n\n**Component Design**:\n✅ **Do**:\n- Design for all states upfront\n- Consider accessibility from the start\n- Use design tokens consistently\n- Think about responsive behavior\n- Create reusable patterns\n\n❌ **Don't**:\n- Design only the \"happy path\"\n- Add visual treatments arbitrarily\n- Hard-code values instead of using tokens\n- Ignore mobile or different screen sizes\n- Create one-off components without system\n\n---\n\n## Common Mistakes to Avoid\n\n**Design System Anti-Patterns**:\n1. **Pixel Perfect Fixation**: Obsessing over exact pixels instead of systematic relationships\n2. **Token Explosion**: Creating too many overly-specific tokens\n3. **Component Sprawl**: Designing every possible variant instead of flexible components\n4. **Documentation Debt**: Letting documentation fall out of sync with designs\n5. **Accessibility Afterthought**: Treating accessibility as optional instead of foundational\n\n**Component Design Anti-Patterns**:\n1. **State Explosion**: Creating too many state combinations\n2. **Hard-Coded Values**: Not using design tokens\n3. **Mobile Neglect**: Designing only for desktop\n4. **Inconsistency**: Not following established patterns\n5. **Over-Engineering**: Making components too complex\n\n---\n\n## Related Skills\n\n- **service-design**: For broader service experience design\n- **typography-expert**: For specialized font and type system design\n- **accessibility-review**: For detailed accessibility auditing\n\n---\n\n## Design Tools Integration\n\n**Figma**:\n- Use design token variables\n- Create component variants properly\n- Document components with descriptions\n- Use auto-layout for responsive components\n\n**Design Token Formats**:\n- Style Dictionary format\n- CSS Custom Properties\n- Design Tokens JSON\n- Figma Variables\n\n**Handoff Formats**:\n- Figma Dev Mode\n- Zeplin\n- Design token exports\n- Code snippets (CSS, React, etc.)\n","## Context\n\nThis skill provides end-to-end UI\u002FUX design capabilities, from design system architecture through component specification. It combines design thinking, visual design principles, and systematic approaches to create cohesive, scalable user interfaces.\n\n## When to Use\n\n**Design System Creation:**\n- Trigger: \"Create design system\" or \"Establish design tokens\"\n- Use Case: Starting new project or redesigning existing system\n\n**Component Design:**\n- Trigger: \"Design component\" or \"Create UI element\"\n- Use Case: Building individual interface components with specifications\n\n**Visual Design:**\n- Trigger: \"Design interface\" or \"Create visual layout\"\n- Use Case: Creating screen designs, layouts, or visual compositions\n\n**Design Specification:**\n- Trigger: \"Specify design\" or \"Create design documentation\"\n- Use Case: Documenting design decisions for handoff to developers\n\n---\n\n## Execution Steps\n\n## Step 1: Design System Architecture\n\n**Purpose**: Establish foundational design system structure.\n\n**Design Token Definition**:\n1. **Color System**:\n   - Primary colors (brand colors)\n   - Secondary colors (supporting colors)\n   - Semantic colors (success, warning, error, info)\n   - Neutral colors (grays for text, backgrounds, borders)\n   - Define color values in HEX, RGB, HSL formats\n\n2. **Typography Scale**:\n   - Font families (primary, secondary, code)\n   - Type scale (heading sizes, body sizes, caption sizes)\n   - Font weights (light, regular, medium, semibold, bold)\n   - Line height ratios (body: 1.5-1.7, headings: 1.1-1.3)\n   - Letter spacing for different sizes\n\n3. **Spacing System**:\n   - Base unit (typically 4px or 8px)\n   - Spacing scale (4, 8, 12, 16, 24, 32, 48, 64, 96 pixels)\n   - Consistent padding and margins\n   - Component spacing rules\n\n4. **Border Radius**:\n   - Scale for corner radii (0, 4, 8, 16, 24 pixels)\n   - Usage guidelines for each radius size\n   - Special cases (circles, pills)\n\n5. **Shadows & Elevation**:\n   - Elevation levels (flat, raised, overlay, modal)\n   - Shadow definitions for each level\n   - Usage contexts\n\n**Output**: Design token documentation with all token categories\n\n---\n\n## Step 2: Component Design Principles\n\n**Purpose**: Create systematic approach to component design.\n\n**Component Design Process**:\n1. **Identify Component Purpose**:\n   - What user problem does it solve?\n   - In what contexts will it be used?\n   - What are the accessibility requirements?\n\n2. **Define Component States**:\n   - Default state\n   - Hover state\n   - Focus state (keyboard navigation)\n   - Active\u002Fpressed state\n   - Disabled state\n   - Error\u002Finvalid state\n\n3. **Design Component Variants**:\n   - Size variants (small, medium, large)\n   - Importance variants (primary, secondary, tertiary)\n   - Context variants (contained, outlined, text)\n\n4. **Specify Component Behavior**:\n   - Interaction patterns\n   - Animation transitions\n   - Responsive behavior\n   - Edge cases\n\n**Output**: Component specification sheet with all states and variants\n\n---\n\n## Step 3: Visual Hierarchy & Layout\n\n**Purpose**: Establish clear visual hierarchy and layout systems.\n\n**Hierarchy Principles**:\n1. **Size Hierarchy**:\n   - Establish clear size relationships (H1 > H2 > H3 > body)\n   - Use modular scale for consistent sizing\n   - Ensure visual distinction between levels\n\n2. **Color Hierarchy**:\n   - Primary actions: high contrast, prominent color\n   - Secondary actions: medium contrast, supporting color\n   - Tertiary actions: low contrast, minimal color\n   - De-emphasized actions: neutral\u002Fmonochrome\n\n3. **Spacing Hierarchy**:\n   - More whitespace = more importance\n   - Group related elements with less spacing\n   - Separate unrelated elements with more spacing\n   - Establish vertical rhythm\n\n4. **Layout Systems**:\n   - Grid system (columns, gutters, margins)\n   - Breakpoints for responsive design\n   - Container max-widths\n   - Component spacing rules\n\n**Output**: Layout system documentation with hierarchy guidelines\n\n---\n\n## Step 4: Accessibility & WCAG Compliance\n\n**Purpose**: Ensure designs meet accessibility standards.\n\n**Accessibility Checklist**:\n1. **Color Contrast**:\n   - Text contrast ratio: 4.5:1 (AA) for body text\n   - Large text contrast ratio: 3:1 (AA) for 18pt+\n   - Graphic contrast ratio: 3:1 (AA) for UI components\n   - Test with contrast checker tools\n\n2. **Touch Targets**:\n   - Practical baseline: 44×44 CSS pixels (from WCAG 2.5.5 Target Size, Level AAA)\n   - AA conformance minimum: 24×24 CSS pixels (WCAG 2.5.8, Level AA) — the 44px baseline exceeds it\n   - Recommended size: 48×48 CSS pixels (tokenized as `--target-size` in tokens.json)\n   - Spacing between touch targets: 8px minimum\n\n3. **Typography**:\n   - Base font size: 16px minimum (100%)\n   - Scalable text units (rem, em, %)\n   - Line height: 1.5-1.7 for body text\n   - Paragraph spacing: 1.5× line height\n\n4. **Keyboard Navigation**:\n   - Visible focus indicators\n   - Logical tab order\n   - Skip navigation links\n   - No keyboard traps\n\n5. **Screen Reader Support**:\n   - Semantic HTML elements\n   - ARIA labels where needed\n   - Alt text for images\n   - Meaningful link text\n\n**Output**: Accessibility compliance report with remediation steps\n\n---\n\n## Step 5: Design Documentation & Handoff\n\n**Purpose**: Create comprehensive design specifications for implementation.\n\n**Documentation Structure**:\n1. **Component Specification**:\n   - Component name and purpose\n   - Visual examples (all states and variants)\n   - Design tokens used\n   - Spacing and positioning\n   - Interaction behaviors\n   - Code examples (CSS, design tokens)\n\n2. **Layout Specifications**:\n   - Grid system documentation\n   - Responsive breakpoints\n   - Container behaviors\n   - Spacing utilities\n\n3. **Usage Guidelines**:\n   - When to use the component\n   - When NOT to use the component\n   - Do's and don'ts\n   - Common mistakes to avoid\n\n4. **Implementation Notes**:\n   - Technical considerations\n   - Browser compatibility notes\n   - Performance considerations\n   - Accessibility requirements\n\n**Output**: Complete design handoff package with specifications and examples\n\n---\n\n## Step 6: Design Quality Validation\n\n**Purpose**: Ensure design meets quality standards and best practices.\n\n**Validation Checklist**:\n- [ ] All design tokens defined and documented\n- [ ] Component states are complete (default, hover, focus, active, disabled)\n- [ ] Color contrast meets WCAG AA standards\n- [ ] Touch targets meet minimum size requirements\n- [ ] Typography uses proper hierarchy and scale\n- [ ] Layout follows grid system\n- [ ] Spacing follows spacing system\n- [ ] Components work responsively\n- [ ] Accessibility considerations addressed\n- [ ] Design documentation is complete\n- [ ] Implementation examples provided\n\n**Quality Gates**:\n1. **Design System Review**: All tokens defined systematically\n2. **Component Review**: All components have complete specifications\n3. **Accessibility Review**: WCAG AA compliance verified\n4. **Documentation Review**: Handoff documentation is complete\n\n**Output**: Design quality report with pass\u002Ffail status and recommendations\n\n---\n\n## Output Format\n\n**For Design System Creation**:\n- Complete design token system (color, typography, spacing, borders, shadows)\n- Design system documentation\n- Component library structure\n- Usage guidelines\n\n**For Component Design**:\n- Component specification sheet\n- Visual examples for all states and variants\n- Design token mappings\n- Implementation code examples\n- Accessibility compliance report\n\n**For Visual Design**:\n- Layout compositions\n- Visual hierarchy documentation\n- Responsive design specifications\n- Grid system documentation\n\n---\n\n## Best Practices\n\n**Design System Design**:\n✅ **Do**:\n- Start with tokens before components\n- Use systematic approaches (scales, ratios)\n- Document all decisions and rationale\n- Test with real content and scenarios\n- Iterate based on feedback\n\n❌ **Don't**:\n- Design components without system context\n- Skip documentation (\"self-documenting\" doesn't scale)\n- Ignore accessibility or responsive design\n- Create arbitrary values without system\n- Mix metaphors or paradigms\n\n**Component Design**:\n✅ **Do**:\n- Design for all states upfront\n- Consider accessibility from the start\n- Use design tokens consistently\n- Think about responsive behavior\n- Create reusable patterns\n\n❌ **Don't**:\n- Design only the \"happy path\"\n- Add visual treatments arbitrarily\n- Hard-code values instead of using tokens\n- Ignore mobile or different screen sizes\n- Create one-off components without system\n\n---\n\n## Common Mistakes to Avoid\n\n**Design System Anti-Patterns**:\n1. **Pixel Perfect Fixation**: Obsessing over exact pixels instead of systematic relationships\n2. **Token Explosion**: Creating too many overly-specific tokens\n3. **Component Sprawl**: Designing every possible variant instead of flexible components\n4. **Documentation Debt**: Letting documentation fall out of sync with designs\n5. **Accessibility Afterthought**: Treating accessibility as optional instead of foundational\n\n**Component Design Anti-Patterns**:\n1. **State Explosion**: Creating too many state combinations\n2. **Hard-Coded Values**: Not using design tokens\n3. **Mobile Neglect**: Designing only for desktop\n4. **Inconsistency**: Not following established patterns\n5. **Over-Engineering**: Making components too complex\n\n---\n\n## Related Skills\n\n- **service-design**: For broader service experience design\n- **typography-expert**: For specialized font and type system design\n- **accessibility-review**: For detailed accessibility auditing\n\n---\n\n## Design Tools Integration\n\n**Figma**:\n- Use design token variables\n- Create component variants properly\n- Document components with descriptions\n- Use auto-layout for responsive components\n\n**Design Token Formats**:\n- Style Dictionary format\n- CSS Custom Properties\n- Design Tokens JSON\n- Figma Variables\n\n**Handoff Formats**:\n- Figma Dev Mode\n- Zeplin\n- Design token exports\n- Code snippets (CSS, React, etc.)\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":37,"description":41,"gemini-parity":42,"last_reviewed":43,"prerequisites":44},"pm","common","active","1.0.1",{"type":28,"triggers":29},"implementation",[30,31,32,33,34,35,36],"design system","ui design","ux design","component design","visual design","design tokens","interface design",[38],{"type":39,"skill":40},"follows","documentation-writing","Provides comprehensive UI\u002FUX design capabilities including design system creation, component design, visual hierarchy, and user-centered design principles. Use when: building design systems, creating visual designs, designing UI components, or establishing design specifications.\n","skip",1788652800000,"none","main","1162ccc568cf90c01b3886d6143cbfd851a37883",".gemini\u002Fskills\u002Fui-ux-design-intelligence",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill ui-ux-design-intelligence",{"tool":59,"command":60},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill ui-ux-design-intelligence",{"tool":62,"command":63},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill ui-ux-design-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fui-ux-design-intelligence\u002FSKILL.md",true,[],[68,76,81,86,91,96],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":77,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":75},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":82,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":75},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":87,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":75},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":92,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":75},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":97,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":75},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]