[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72V55H88CVSXD2FS39GP9HP":3,"skill-same:01M72V55H88CVSXD2FS39GP9HP":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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M72V55H88CVSXD2FS39GP9HP","frontend-design",null,"React-oriented UI\u002FUX design principles for frontend development. Covers React patterns, component architecture, hooks, layout, typography, color, accessibility, and responsive design. Use when building React UI, reviewing frontend code, designing components, or making visual\u002Finteraction decisions. Assumes React with a meta-framework (TanStack Start, Next.js, Remix, etc.).","roerohan\u002Fskills","roerohan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42958812?v=4","01M72V46MPJK55W3BZ44Y869D1","Rohan Mukherjee","01M72V46N9GPDNRC4RHVRR2YCB",29,"MIT","https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: frontend-design\ndescription: React-oriented UI\u002FUX design principles for frontend development. Covers React patterns, component architecture, hooks, layout, typography, color, accessibility, and responsive design. Use when building React UI, reviewing frontend code, designing components, or making visual\u002Finteraction decisions. Assumes React with a meta-framework (TanStack Start, Next.js, Remix, etc.).\n---\n\n# Frontend Design\n\nUI\u002FUX principles for building well-designed, accessible, maintainable React interfaces.\n\n**Context:** This skill assumes React as the UI layer, typically with a meta-framework (TanStack Start, Next.js, Remix, etc.) and a styling approach (Tailwind, CSS Modules, etc.). Raw HTML\u002FCSS guidance is provided only where it underpins React patterns.\n\n## Core Principles\n\n1. **Clarity over cleverness** — Users should understand the interface immediately\n2. **Consistency over novelty** — Reuse established patterns; deviate only with reason\n3. **Accessibility is not optional** — Design for all users from the start\n4. **Content drives layout** — Structure follows information hierarchy, not decoration\n5. **Composition over configuration** — Prefer `children` and compound components over prop sprawl\n6. **Server-first data, client-first interaction** — Load data on the server; keep interactivity on the client\n\n## Decision Tree\n\n```\nWhat are you working on?\n├─ React component design \u002F hooks \u002F state  → See react.md\n├─ Reusable UI component patterns          → See components.md\n├─ Page layout \u002F spacing                   → See layout.md\n├─ Text styling \u002F hierarchy                → See typography.md\n├─ Colors \u002F theming \u002F contrast             → See color.md\n├─ Keyboard \u002F screen reader \u002F a11y         → See accessibility.md\n├─ Multi-device \u002F breakpoints              → See responsive.md\n└─ Multiple concerns                       → Start with react.md, layer in others\n```\n\n## Quick Reference\n\n### Visual Hierarchy Checklist\n\n| Level | Purpose | Techniques |\n|-------|---------|------------|\n| Primary | Single main action\u002Fcontent | Size, weight, color, position |\n| Secondary | Supporting actions\u002Fcontent | Reduced size\u002Fweight, muted color |\n| Tertiary | Contextual\u002Fmetadata | Smallest size, lightest weight |\n\n### Spacing System\n\nUse a consistent base unit (4px or 8px). Apply multiples:\n\n| Token | Value (8px base) | Use |\n|-------|-------------------|-----|\n| `xs` | 4px | Inline elements, icon gaps |\n| `sm` | 8px | Tight grouping |\n| `md` | 16px | Default element spacing |\n| `lg` | 24px | Section padding |\n| `xl` | 32px | Major section separation |\n| `2xl` | 48px | Page-level separation |\n\n### The 60-30-10 Rule\n\n| Proportion | Role | Example |\n|------------|------|---------|\n| 60% | Dominant \u002F background | Page background, card surfaces |\n| 30% | Secondary \u002F supporting | Section backgrounds, borders |\n| 10% | Accent \u002F emphasis | CTAs, active states, highlights |\n\n## Design Review Checklist\n\nWhen reviewing frontend code or designs:\n\n- [ ] **Hierarchy**: Is the most important content\u002Faction visually dominant?\n- [ ] **Consistency**: Do similar elements look and behave the same?\n- [ ] **Spacing**: Is spacing systematic (not arbitrary pixel values)?\n- [ ] **Color contrast**: Do text\u002Fbackground combos meet WCAG AA (4.5:1)?\n- [ ] **Interactive states**: Do clickable elements have hover, focus, active, disabled states?\n- [ ] **Responsive**: Does the layout work at mobile, tablet, and desktop widths?\n- [ ] **Keyboard**: Can all interactive elements be reached and operated via keyboard?\n- [ ] **Loading states**: Are empty\u002Floading\u002Ferror states designed, not just happy path?\n- [ ] **Touch targets**: Are tap targets at least 44x44px on mobile?\n- [ ] **Content overflow**: Does the layout handle long text, missing images, edge cases?\n\n## Common Anti-Patterns\n\n| Anti-Pattern | Problem | Fix |\n|-------------|---------|-----|\n| Magic numbers | `margin: 13px` breaks system | Use spacing tokens |\n| Color hardcoding | `#3b82f6` everywhere | Use semantic color tokens |\n| Hover-only affordance | Hidden from keyboard\u002Ftouch users | Always show affordance; enhance on hover |\n| Fixed dimensions | Breaks on different content\u002Fscreens | Use min\u002Fmax + fluid sizing |\n| Z-index wars | Escalating `z-index: 9999` | Use a layering system (base, dropdown, modal, toast) |\n| Truncation without access | `text-overflow: ellipsis` hides content | Add tooltip or expand mechanism |\n\n## Interaction Principles\n\n1. **Feedback is immediate** — Every user action gets a visible response within 100ms\n2. **State is visible** — Users can always tell what state the system is in\n3. **Actions are reversible** — Destructive actions require confirmation; prefer undo over \"are you sure?\"\n4. **Errors are recoverable** — Show what went wrong and how to fix it\n5. **Transitions are meaningful** — Animation communicates change, not decoration\n\n## React Review Checklist (Addendum)\n\nOn top of the design review checklist above, verify for React code:\n\n- [ ] **Component boundaries**: Is each component focused on one concern?\n- [ ] **Props**: Are props minimal and well-typed? No boolean prop sprawl?\n- [ ] **Composition**: Using `children`\u002Frender props instead of mega-config objects?\n- [ ] **Effects**: Are effects necessary, or can derived state \u002F event handlers replace them?\n- [ ] **Keys**: Are list keys stable and meaningful (not array index)?\n- [ ] **Memoization**: Is `useMemo`\u002F`useCallback` used only where measured necessary?\n- [ ] **Server vs client**: Is data fetching on the server? Is client JS minimal?\n- [ ] **Error boundaries**: Do async\u002Ffallible sections have error boundaries?\n- [ ] **Suspense**: Are loading states handled with Suspense where appropriate?\n\n## Reading Order\n\n| Task | Files to Read |\n|------|---------------|\n| React component architecture | react.md |\n| Building a page layout | layout.md |\n| Designing a reusable UI component | react.md + components.md |\n| Styling text content | typography.md |\n| Choosing \u002F applying colors | color.md |\n| Making UI accessible | accessibility.md |\n| Supporting multiple screen sizes | responsive.md |\n| Full design review | This file + all references |\n\n## In This Reference\n\n| File | Purpose |\n|------|---------|\n| [react.md](.\u002Freferences\u002Freact.md) | React patterns, hooks, composition, state, meta-frameworks |\n| [components.md](.\u002Freferences\u002Fcomponents.md) | Common UI component design patterns |\n| [layout.md](.\u002Freferences\u002Flayout.md) | Spatial organization, grid, flexbox, spacing |\n| [typography.md](.\u002Freferences\u002Ftypography.md) | Type scale, font selection, readability |\n| [color.md](.\u002Freferences\u002Fcolor.md) | Color systems, contrast, theming, dark mode |\n| [accessibility.md](.\u002Freferences\u002Faccessibility.md) | WCAG compliance, keyboard, screen readers |\n| [responsive.md](.\u002Freferences\u002Fresponsive.md) | Breakpoints, mobile-first, fluid design |\n","# Frontend Design\n\nUI\u002FUX principles for building well-designed, accessible, maintainable React interfaces.\n\n**Context:** This skill assumes React as the UI layer, typically with a meta-framework (TanStack Start, Next.js, Remix, etc.) and a styling approach (Tailwind, CSS Modules, etc.). Raw HTML\u002FCSS guidance is provided only where it underpins React patterns.\n\n## Core Principles\n\n1. **Clarity over cleverness** — Users should understand the interface immediately\n2. **Consistency over novelty** — Reuse established patterns; deviate only with reason\n3. **Accessibility is not optional** — Design for all users from the start\n4. **Content drives layout** — Structure follows information hierarchy, not decoration\n5. **Composition over configuration** — Prefer `children` and compound components over prop sprawl\n6. **Server-first data, client-first interaction** — Load data on the server; keep interactivity on the client\n\n## Decision Tree\n\n```\nWhat are you working on?\n├─ React component design \u002F hooks \u002F state  → See react.md\n├─ Reusable UI component patterns          → See components.md\n├─ Page layout \u002F spacing                   → See layout.md\n├─ Text styling \u002F hierarchy                → See typography.md\n├─ Colors \u002F theming \u002F contrast             → See color.md\n├─ Keyboard \u002F screen reader \u002F a11y         → See accessibility.md\n├─ Multi-device \u002F breakpoints              → See responsive.md\n└─ Multiple concerns                       → Start with react.md, layer in others\n```\n\n## Quick Reference\n\n### Visual Hierarchy Checklist\n\n| Level | Purpose | Techniques |\n|-------|---------|------------|\n| Primary | Single main action\u002Fcontent | Size, weight, color, position |\n| Secondary | Supporting actions\u002Fcontent | Reduced size\u002Fweight, muted color |\n| Tertiary | Contextual\u002Fmetadata | Smallest size, lightest weight |\n\n### Spacing System\n\nUse a consistent base unit (4px or 8px). Apply multiples:\n\n| Token | Value (8px base) | Use |\n|-------|-------------------|-----|\n| `xs` | 4px | Inline elements, icon gaps |\n| `sm` | 8px | Tight grouping |\n| `md` | 16px | Default element spacing |\n| `lg` | 24px | Section padding |\n| `xl` | 32px | Major section separation |\n| `2xl` | 48px | Page-level separation |\n\n### The 60-30-10 Rule\n\n| Proportion | Role | Example |\n|------------|------|---------|\n| 60% | Dominant \u002F background | Page background, card surfaces |\n| 30% | Secondary \u002F supporting | Section backgrounds, borders |\n| 10% | Accent \u002F emphasis | CTAs, active states, highlights |\n\n## Design Review Checklist\n\nWhen reviewing frontend code or designs:\n\n- [ ] **Hierarchy**: Is the most important content\u002Faction visually dominant?\n- [ ] **Consistency**: Do similar elements look and behave the same?\n- [ ] **Spacing**: Is spacing systematic (not arbitrary pixel values)?\n- [ ] **Color contrast**: Do text\u002Fbackground combos meet WCAG AA (4.5:1)?\n- [ ] **Interactive states**: Do clickable elements have hover, focus, active, disabled states?\n- [ ] **Responsive**: Does the layout work at mobile, tablet, and desktop widths?\n- [ ] **Keyboard**: Can all interactive elements be reached and operated via keyboard?\n- [ ] **Loading states**: Are empty\u002Floading\u002Ferror states designed, not just happy path?\n- [ ] **Touch targets**: Are tap targets at least 44x44px on mobile?\n- [ ] **Content overflow**: Does the layout handle long text, missing images, edge cases?\n\n## Common Anti-Patterns\n\n| Anti-Pattern | Problem | Fix |\n|-------------|---------|-----|\n| Magic numbers | `margin: 13px` breaks system | Use spacing tokens |\n| Color hardcoding | `#3b82f6` everywhere | Use semantic color tokens |\n| Hover-only affordance | Hidden from keyboard\u002Ftouch users | Always show affordance; enhance on hover |\n| Fixed dimensions | Breaks on different content\u002Fscreens | Use min\u002Fmax + fluid sizing |\n| Z-index wars | Escalating `z-index: 9999` | Use a layering system (base, dropdown, modal, toast) |\n| Truncation without access | `text-overflow: ellipsis` hides content | Add tooltip or expand mechanism |\n\n## Interaction Principles\n\n1. **Feedback is immediate** — Every user action gets a visible response within 100ms\n2. **State is visible** — Users can always tell what state the system is in\n3. **Actions are reversible** — Destructive actions require confirmation; prefer undo over \"are you sure?\"\n4. **Errors are recoverable** — Show what went wrong and how to fix it\n5. **Transitions are meaningful** — Animation communicates change, not decoration\n\n## React Review Checklist (Addendum)\n\nOn top of the design review checklist above, verify for React code:\n\n- [ ] **Component boundaries**: Is each component focused on one concern?\n- [ ] **Props**: Are props minimal and well-typed? No boolean prop sprawl?\n- [ ] **Composition**: Using `children`\u002Frender props instead of mega-config objects?\n- [ ] **Effects**: Are effects necessary, or can derived state \u002F event handlers replace them?\n- [ ] **Keys**: Are list keys stable and meaningful (not array index)?\n- [ ] **Memoization**: Is `useMemo`\u002F`useCallback` used only where measured necessary?\n- [ ] **Server vs client**: Is data fetching on the server? Is client JS minimal?\n- [ ] **Error boundaries**: Do async\u002Ffallible sections have error boundaries?\n- [ ] **Suspense**: Are loading states handled with Suspense where appropriate?\n\n## Reading Order\n\n| Task | Files to Read |\n|------|---------------|\n| React component architecture | react.md |\n| Building a page layout | layout.md |\n| Designing a reusable UI component | react.md + components.md |\n| Styling text content | typography.md |\n| Choosing \u002F applying colors | color.md |\n| Making UI accessible | accessibility.md |\n| Supporting multiple screen sizes | responsive.md |\n| Full design review | This file + all references |\n\n## In This Reference\n\n| File | Purpose |\n|------|---------|\n| [react.md](.\u002Freferences\u002Freact.md) | React patterns, hooks, composition, state, meta-frameworks |\n| [components.md](.\u002Freferences\u002Fcomponents.md) | Common UI component design patterns |\n| [layout.md](.\u002Freferences\u002Flayout.md) | Spatial organization, grid, flexbox, spacing |\n| [typography.md](.\u002Freferences\u002Ftypography.md) | Type scale, font selection, readability |\n| [color.md](.\u002Freferences\u002Fcolor.md) | Color systems, contrast, theming, dark mode |\n| [accessibility.md](.\u002Freferences\u002Faccessibility.md) | WCAG compliance, keyboard, screen readers |\n| [responsive.md](.\u002Freferences\u002Fresponsive.md) | Breakpoints, mobile-first, fluid design |\n",{"name":5,"description":7},"main","171fbdd3085ba76dacd148aa292d0559e8d913eb",1,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills","https:\u002F\u002Fgithub.com\u002Froerohan","https:\u002F\u002Froerohan.com","Engineer at @cloudflare | Founding Engineer at @dyte-in | CTFs | Ex-Tech Head at @csivitu (2020-21).","2026-09-04 18:05:21",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add roerohan\u002Fskills --skill frontend-design",{"tool":38,"command":39},"bunx","bunx skills add roerohan\u002Fskills --skill frontend-design",{"tool":41,"command":42},"pnpm","pnpm dlx skills add roerohan\u002Fskills --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002FSKILL.md",true,[46,52,56,60,64,68,72],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Faccessibility.md","REFERENCE","参考文档",7023,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002Freferences\u002Faccessibility.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcolor.md",4600,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002Freferences\u002Fcolor.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcomponents.md",7447,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002Freferences\u002Fcomponents.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Flayout.md",5459,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002Freferences\u002Flayout.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Freact.md",6694,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002Freferences\u002Freact.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fresponsive.md",5330,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002Freferences\u002Fresponsive.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Ftypography.md",3744,"https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ffrontend-design\u002Freferences\u002Ftypography.md",[77,84,91,98,105,112],{"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":83,"publishedAt":19},"01M72V6EQGTE5K3AP5B5AWJARB","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M72V6B7459ZDJMS003D65S02","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M72V69RJ26MA6Q5RZ07XTG9V","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Funslop\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M72V66RS1KZVXMB9NGC4RDH1","tmux","Manage long-running commands in the user's current tmux session. Use when starting dev servers, watchers, background logs, or reading\u002Finteracting with named tmux panes.","https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ftmux\u002FSKILL.md",[],[],{"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":111,"publishedAt":19},"01M72V643VG4C97V3X764ZW12G","timesharing","Multiplexes one agent's attention across independent long-running external processes while preserving one reasoning context. Use for concurrent tests, builds, servers, watchers, REPLs, benchmarks, downloads, and other latency-bearing shell work; never use it to spawn or substitute subagents.","https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Ftimesharing\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M72V62CFDFD6SJDA331JEWQ9","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Froerohan\u002Fskills\u002Fblob\u002Fmain\u002Fteach\u002FSKILL.md",[],[]]