[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79CJJKWM15YQKP9TF79ZP4V":3,"skill-same:01M79CJJKWM15YQKP9TF79ZP4V":48},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79CJJKWM15YQKP9TF79ZP4V","frontend-ui-engineering",null,"Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.","hamzabellouch\u002Fagent-skills","hamzabellouch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237856042?v=4","01M79BRYW7XAMK3YDWQEMTWGWS","Hamza Bellouch","01M79BRYWXQV3JK2TGVTX8GN2A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FDesign\u002FUI_UX_and_Design_Systems\u002Ffrontend-ui-engineering\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-ui-engineering\ndescription: Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.\n---\n\n# Frontend UI Engineering\n\n## Overview\n\nBuild production-quality user interfaces that are accessible, performant, and visually polished. The goal is UI that looks like it was built by a design-aware engineer at a top company — not like it was generated by an AI. This means real design system adherence, proper accessibility, thoughtful interaction patterns, and no generic \"AI aesthetic.\"\n\n## When to Use\n\n- Building new UI components or pages\n- Modifying existing user-facing interfaces\n- Implementing responsive layouts\n- Adding interactivity or state management\n- Fixing visual or UX issues\n\n## Component Architecture\n\n### File Structure\n\nColocate everything related to a component:\n\n```\nsrc\u002Fcomponents\u002F\n  TaskList\u002F\n    TaskList.tsx          # Component implementation\n    TaskList.test.tsx     # Tests\n    TaskList.stories.tsx  # Storybook stories (if using)\n    use-task-list.ts      # Custom hook (if complex state)\n    types.ts              # Component-specific types (if needed)\n```\n\n### Component Patterns\n\n**Prefer composition over configuration:**\n\n```tsx\n\u002F\u002F Good: Composable\n\u003CCard>\n  \u003CCardHeader>\n    \u003CCardTitle>Tasks\u003C\u002FCardTitle>\n  \u003C\u002FCardHeader>\n  \u003CCardBody>\n    \u003CTaskList tasks={tasks} \u002F>\n  \u003C\u002FCardBody>\n\u003C\u002FCard>\n\n\u002F\u002F Avoid: Over-configured\n\u003CCard\n  title=\"Tasks\"\n  headerVariant=\"large\"\n  bodyPadding=\"md\"\n  content={\u003CTaskList tasks={tasks} \u002F>}\n\u002F>\n```\n\n**Keep components focused:**\n\n```tsx\n\u002F\u002F Good: Does one thing\nexport function TaskItem({ task, onToggle, onDelete }: TaskItemProps) {\n  return (\n    \u003Cli className=\"flex items-center gap-3 p-3\">\n      \u003CCheckbox checked={task.done} onChange={() => onToggle(task.id)} \u002F>\n      \u003Cspan className={task.done ? 'line-through text-muted' : ''}>{task.title}\u003C\u002Fspan>\n      \u003CButton variant=\"ghost\" size=\"sm\" onClick={() => onDelete(task.id)}>\n        \u003CTrashIcon \u002F>\n      \u003C\u002FButton>\n    \u003C\u002Fli>\n  );\n}\n```\n\n**Separate data fetching from presentation:**\n\n```tsx\n\u002F\u002F Container: handles data\nexport function TaskListContainer() {\n  const { tasks, isLoading, error } = useTasks();\n\n  if (isLoading) return \u003CTaskListSkeleton \u002F>;\n  if (error) return \u003CErrorState message=\"Failed to load tasks\" retry={refetch} \u002F>;\n  if (tasks.length === 0) return \u003CEmptyState message=\"No tasks yet\" \u002F>;\n\n  return \u003CTaskList tasks={tasks} \u002F>;\n}\n\n\u002F\u002F Presentation: handles rendering\nexport function TaskList({ tasks }: { tasks: Task[] }) {\n  return (\n    \u003Cul role=\"list\" className=\"divide-y\">\n      {tasks.map(task => \u003CTaskItem key={task.id} task={task} \u002F>)}\n    \u003C\u002Ful>\n  );\n}\n```\n\n## State Management\n\n**Choose the simplest approach that works:**\n\n```\nLocal state (useState)           → Component-specific UI state\nLifted state                     → Shared between 2-3 sibling components\nContext                          → Theme, auth, locale (read-heavy, write-rare)\nURL state (searchParams)         → Filters, pagination, shareable UI state\nServer state (React Query, SWR)  → Remote data with caching\nGlobal store (Zustand, Redux)    → Complex client state shared app-wide\n```\n\n**Avoid prop drilling deeper than 3 levels.** If you're passing props through components that don't use them, introduce context or restructure the component tree.\n\n## Design System Adherence\n\n### Avoid the AI Aesthetic\n\nAI-generated UI has recognizable patterns. Avoid all of them:\n\n| AI Default | Why It Is a Problem | Production Quality |\n|---|---|---|\n| Purple\u002Findigo everything | Models default to visually \"safe\" palettes, making every app look identical | Use the project's actual color palette |\n| Excessive gradients | Gradients add visual noise and clash with most design systems | Flat or subtle gradients matching the design system |\n| Rounded everything (rounded-2xl) | Maximum rounding signals \"friendly\" but ignores the hierarchy of corner radii in real designs | Consistent border-radius from the design system |\n| Generic hero sections | Template-driven layout with no connection to the actual content or user need | Content-first layouts |\n| Lorem ipsum-style copy | Placeholder text hides layout problems that real content reveals (length, wrapping, overflow) | Realistic placeholder content |\n| Oversized padding everywhere | Equal generous padding destroys visual hierarchy and wastes screen space | Consistent spacing scale |\n| Stock card grids | Uniform grids are a layout shortcut that ignores information priority and scanning patterns | Purpose-driven layouts |\n| Shadow-heavy design | Layered shadows add depth that competes with content and slows rendering on low-end devices | Subtle or no shadows unless the design system specifies |\n\n### Spacing and Layout\n\nUse a consistent spacing scale. Don't invent values:\n\n```css\n\u002F* Use the scale: 0.25rem increments (or whatever the project uses) *\u002F\n\u002F* Good *\u002F  padding: 1rem;      \u002F* 16px *\u002F\n\u002F* Good *\u002F  gap: 0.75rem;       \u002F* 12px *\u002F\n\u002F* Bad *\u002F   padding: 13px;      \u002F* Not on any scale *\u002F\n\u002F* Bad *\u002F   margin-top: 2.3rem; \u002F* Not on any scale *\u002F\n```\n\n### Typography\n\nRespect the type hierarchy:\n\n```\nh1 → Page title (one per page)\nh2 → Section title\nh3 → Subsection title\nbody → Default text\nsmall → Secondary\u002Fhelper text\n```\n\nDon't skip heading levels. Don't use heading styles for non-heading content.\n\n### Color\n\n- Use semantic color tokens: `text-primary`, `bg-surface`, `border-default` — not raw hex values\n- Ensure sufficient contrast (4.5:1 for normal text, 3:1 for large text)\n- Don't rely solely on color to convey information (use icons, text, or patterns too)\n\n## Accessibility (WCAG 2.1 AA)\n\nEvery component must meet these standards:\n\n### Keyboard Navigation\n\n```tsx\n\u002F\u002F Every interactive element must be keyboard accessible\n\u003Cbutton onClick={handleClick}>Click me\u003C\u002Fbutton>        \u002F\u002F ✓ Focusable by default\n\u003Cdiv onClick={handleClick}>Click me\u003C\u002Fdiv>               \u002F\u002F ✗ Not focusable\n\u003Cdiv role=\"button\" tabIndex={0} onClick={handleClick}    \u002F\u002F ✓ But prefer \u003Cbutton>\n     onKeyDown={e => {\n       if (e.key === 'Enter') handleClick();\n       if (e.key === ' ') e.preventDefault();\n     }}\n     onKeyUp={e => {\n       if (e.key === ' ') handleClick();\n     }}>\n  Click me\n\u003C\u002Fdiv>\n```\n\n### ARIA Labels\n\n```tsx\n\u002F\u002F Label interactive elements that lack visible text\n\u003Cbutton aria-label=\"Close dialog\">\u003CXIcon \u002F>\u003C\u002Fbutton>\n\n\u002F\u002F Label form inputs\n\u003Clabel htmlFor=\"email\">Email\u003C\u002Flabel>\n\u003Cinput id=\"email\" type=\"email\" \u002F>\n\n\u002F\u002F Or use aria-label when no visible label exists\n\u003Cinput aria-label=\"Search tasks\" type=\"search\" \u002F>\n```\n\n### Focus Management\n\n```tsx\n\u002F\u002F Move focus when content changes\nfunction Dialog({ isOpen, onClose }: DialogProps) {\n  const closeRef = useRef\u003CHTMLButtonElement>(null);\n\n  useEffect(() => {\n    if (isOpen) closeRef.current?.focus();\n  }, [isOpen]);\n\n  \u002F\u002F Trap focus inside dialog when open\n  return (\n    \u003Cdialog open={isOpen}>\n      \u003Cbutton ref={closeRef} onClick={onClose}>Close\u003C\u002Fbutton>\n      {\u002F* dialog content *\u002F}\n    \u003C\u002Fdialog>\n  );\n}\n```\n\n### Meaningful Empty and Error States\n\n```tsx\n\u002F\u002F Don't show blank screens\nfunction TaskList({ tasks }: { tasks: Task[] }) {\n  if (tasks.length === 0) {\n    return (\n      \u003Cdiv role=\"status\" className=\"text-center py-12\">\n        \u003CTasksEmptyIcon className=\"mx-auto h-12 w-12 text-muted\" \u002F>\n        \u003Ch3 className=\"mt-2 text-sm font-medium\">No tasks\u003C\u002Fh3>\n        \u003Cp className=\"mt-1 text-sm text-muted\">Get started by creating a new task.\u003C\u002Fp>\n        \u003CButton className=\"mt-4\" onClick={onCreateTask}>Create Task\u003C\u002FButton>\n      \u003C\u002Fdiv>\n    );\n  }\n\n  return \u003Cul role=\"list\">...\u003C\u002Ful>;\n}\n```\n\n## Responsive Design\n\nDesign for mobile first, then expand:\n\n```tsx\n\u002F\u002F Tailwind: mobile-first responsive\n\u003Cdiv className=\"\n  grid grid-cols-1      \u002F* Mobile: single column *\u002F\n  sm:grid-cols-2        \u002F* Small: 2 columns *\u002F\n  lg:grid-cols-3        \u002F* Large: 3 columns *\u002F\n  gap-4\n\">\n```\n\nTest at these breakpoints: 320px, 768px, 1024px, 1440px.\n\n## Loading and Transitions\n\n```tsx\n\u002F\u002F Skeleton loading (not spinners for content)\nfunction TaskListSkeleton() {\n  return (\n    \u003Cdiv className=\"space-y-3\" aria-busy=\"true\" aria-label=\"Loading tasks\">\n      {Array.from({ length: 3 }).map((_, i) => (\n        \u003Cdiv key={i} className=\"h-12 bg-muted animate-pulse rounded\" \u002F>\n      ))}\n    \u003C\u002Fdiv>\n  );\n}\n\n\u002F\u002F Optimistic updates for perceived speed\nfunction useToggleTask() {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: toggleTask,\n    onMutate: async (taskId) => {\n      await queryClient.cancelQueries({ queryKey: ['tasks'] });\n      const previous = queryClient.getQueryData(['tasks']);\n\n      queryClient.setQueryData(['tasks'], (old: Task[]) =>\n        old.map(t => t.id === taskId ? { ...t, done: !t.done } : t)\n      );\n\n      return { previous };\n    },\n    onError: (_err, _taskId, context) => {\n      queryClient.setQueryData(['tasks'], context?.previous);\n    },\n  });\n}\n```\n\n## See Also\n\nFor detailed accessibility requirements and testing tools, see `references\u002Faccessibility-checklist.md`.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"Accessibility is a nice-to-have\" | It's a legal requirement in many jurisdictions and an engineering quality standard. |\n| \"We'll make it responsive later\" | Retrofitting responsive design is 3x harder than building it from the start. |\n| \"The design isn't final, so I'll skip styling\" | Use the design system defaults. Unstyled UI creates a broken first impression for reviewers. |\n| \"This is just a prototype\" | Prototypes become production code. Build the foundation right. |\n| \"The AI aesthetic is fine for now\" | It signals low quality. Use the project's actual design system from the start. |\n\n## Red Flags\n\n- Components with more than 200 lines (split them)\n- Inline styles or arbitrary pixel values\n- Missing error states, loading states, or empty states\n- No keyboard navigation testing\n- Color as the sole indicator of state (red\u002Fgreen without text or icons)\n- Generic \"AI look\" (purple gradients, oversized cards, stock layouts)\n\n## Verification\n\nAfter building UI:\n\n- [ ] Component renders without console errors\n- [ ] All interactive elements are keyboard accessible (Tab through the page)\n- [ ] Screen reader can convey the page's content and structure\n- [ ] Responsive: works at 320px, 768px, 1024px, 1440px\n- [ ] Loading, error, and empty states all handled\n- [ ] Follows the project's design system (spacing, colors, typography)\n- [ ] No accessibility warnings in dev tools or axe-core\n","# Frontend UI Engineering\n\n## Overview\n\nBuild production-quality user interfaces that are accessible, performant, and visually polished. The goal is UI that looks like it was built by a design-aware engineer at a top company — not like it was generated by an AI. This means real design system adherence, proper accessibility, thoughtful interaction patterns, and no generic \"AI aesthetic.\"\n\n## When to Use\n\n- Building new UI components or pages\n- Modifying existing user-facing interfaces\n- Implementing responsive layouts\n- Adding interactivity or state management\n- Fixing visual or UX issues\n\n## Component Architecture\n\n### File Structure\n\nColocate everything related to a component:\n\n```\nsrc\u002Fcomponents\u002F\n  TaskList\u002F\n    TaskList.tsx          # Component implementation\n    TaskList.test.tsx     # Tests\n    TaskList.stories.tsx  # Storybook stories (if using)\n    use-task-list.ts      # Custom hook (if complex state)\n    types.ts              # Component-specific types (if needed)\n```\n\n### Component Patterns\n\n**Prefer composition over configuration:**\n\n```tsx\n\u002F\u002F Good: Composable\n\u003CCard>\n  \u003CCardHeader>\n    \u003CCardTitle>Tasks\u003C\u002FCardTitle>\n  \u003C\u002FCardHeader>\n  \u003CCardBody>\n    \u003CTaskList tasks={tasks} \u002F>\n  \u003C\u002FCardBody>\n\u003C\u002FCard>\n\n\u002F\u002F Avoid: Over-configured\n\u003CCard\n  title=\"Tasks\"\n  headerVariant=\"large\"\n  bodyPadding=\"md\"\n  content={\u003CTaskList tasks={tasks} \u002F>}\n\u002F>\n```\n\n**Keep components focused:**\n\n```tsx\n\u002F\u002F Good: Does one thing\nexport function TaskItem({ task, onToggle, onDelete }: TaskItemProps) {\n  return (\n    \u003Cli className=\"flex items-center gap-3 p-3\">\n      \u003CCheckbox checked={task.done} onChange={() => onToggle(task.id)} \u002F>\n      \u003Cspan className={task.done ? 'line-through text-muted' : ''}>{task.title}\u003C\u002Fspan>\n      \u003CButton variant=\"ghost\" size=\"sm\" onClick={() => onDelete(task.id)}>\n        \u003CTrashIcon \u002F>\n      \u003C\u002FButton>\n    \u003C\u002Fli>\n  );\n}\n```\n\n**Separate data fetching from presentation:**\n\n```tsx\n\u002F\u002F Container: handles data\nexport function TaskListContainer() {\n  const { tasks, isLoading, error } = useTasks();\n\n  if (isLoading) return \u003CTaskListSkeleton \u002F>;\n  if (error) return \u003CErrorState message=\"Failed to load tasks\" retry={refetch} \u002F>;\n  if (tasks.length === 0) return \u003CEmptyState message=\"No tasks yet\" \u002F>;\n\n  return \u003CTaskList tasks={tasks} \u002F>;\n}\n\n\u002F\u002F Presentation: handles rendering\nexport function TaskList({ tasks }: { tasks: Task[] }) {\n  return (\n    \u003Cul role=\"list\" className=\"divide-y\">\n      {tasks.map(task => \u003CTaskItem key={task.id} task={task} \u002F>)}\n    \u003C\u002Ful>\n  );\n}\n```\n\n## State Management\n\n**Choose the simplest approach that works:**\n\n```\nLocal state (useState)           → Component-specific UI state\nLifted state                     → Shared between 2-3 sibling components\nContext                          → Theme, auth, locale (read-heavy, write-rare)\nURL state (searchParams)         → Filters, pagination, shareable UI state\nServer state (React Query, SWR)  → Remote data with caching\nGlobal store (Zustand, Redux)    → Complex client state shared app-wide\n```\n\n**Avoid prop drilling deeper than 3 levels.** If you're passing props through components that don't use them, introduce context or restructure the component tree.\n\n## Design System Adherence\n\n### Avoid the AI Aesthetic\n\nAI-generated UI has recognizable patterns. Avoid all of them:\n\n| AI Default | Why It Is a Problem | Production Quality |\n|---|---|---|\n| Purple\u002Findigo everything | Models default to visually \"safe\" palettes, making every app look identical | Use the project's actual color palette |\n| Excessive gradients | Gradients add visual noise and clash with most design systems | Flat or subtle gradients matching the design system |\n| Rounded everything (rounded-2xl) | Maximum rounding signals \"friendly\" but ignores the hierarchy of corner radii in real designs | Consistent border-radius from the design system |\n| Generic hero sections | Template-driven layout with no connection to the actual content or user need | Content-first layouts |\n| Lorem ipsum-style copy | Placeholder text hides layout problems that real content reveals (length, wrapping, overflow) | Realistic placeholder content |\n| Oversized padding everywhere | Equal generous padding destroys visual hierarchy and wastes screen space | Consistent spacing scale |\n| Stock card grids | Uniform grids are a layout shortcut that ignores information priority and scanning patterns | Purpose-driven layouts |\n| Shadow-heavy design | Layered shadows add depth that competes with content and slows rendering on low-end devices | Subtle or no shadows unless the design system specifies |\n\n### Spacing and Layout\n\nUse a consistent spacing scale. Don't invent values:\n\n```css\n\u002F* Use the scale: 0.25rem increments (or whatever the project uses) *\u002F\n\u002F* Good *\u002F  padding: 1rem;      \u002F* 16px *\u002F\n\u002F* Good *\u002F  gap: 0.75rem;       \u002F* 12px *\u002F\n\u002F* Bad *\u002F   padding: 13px;      \u002F* Not on any scale *\u002F\n\u002F* Bad *\u002F   margin-top: 2.3rem; \u002F* Not on any scale *\u002F\n```\n\n### Typography\n\nRespect the type hierarchy:\n\n```\nh1 → Page title (one per page)\nh2 → Section title\nh3 → Subsection title\nbody → Default text\nsmall → Secondary\u002Fhelper text\n```\n\nDon't skip heading levels. Don't use heading styles for non-heading content.\n\n### Color\n\n- Use semantic color tokens: `text-primary`, `bg-surface`, `border-default` — not raw hex values\n- Ensure sufficient contrast (4.5:1 for normal text, 3:1 for large text)\n- Don't rely solely on color to convey information (use icons, text, or patterns too)\n\n## Accessibility (WCAG 2.1 AA)\n\nEvery component must meet these standards:\n\n### Keyboard Navigation\n\n```tsx\n\u002F\u002F Every interactive element must be keyboard accessible\n\u003Cbutton onClick={handleClick}>Click me\u003C\u002Fbutton>        \u002F\u002F ✓ Focusable by default\n\u003Cdiv onClick={handleClick}>Click me\u003C\u002Fdiv>               \u002F\u002F ✗ Not focusable\n\u003Cdiv role=\"button\" tabIndex={0} onClick={handleClick}    \u002F\u002F ✓ But prefer \u003Cbutton>\n     onKeyDown={e => {\n       if (e.key === 'Enter') handleClick();\n       if (e.key === ' ') e.preventDefault();\n     }}\n     onKeyUp={e => {\n       if (e.key === ' ') handleClick();\n     }}>\n  Click me\n\u003C\u002Fdiv>\n```\n\n### ARIA Labels\n\n```tsx\n\u002F\u002F Label interactive elements that lack visible text\n\u003Cbutton aria-label=\"Close dialog\">\u003CXIcon \u002F>\u003C\u002Fbutton>\n\n\u002F\u002F Label form inputs\n\u003Clabel htmlFor=\"email\">Email\u003C\u002Flabel>\n\u003Cinput id=\"email\" type=\"email\" \u002F>\n\n\u002F\u002F Or use aria-label when no visible label exists\n\u003Cinput aria-label=\"Search tasks\" type=\"search\" \u002F>\n```\n\n### Focus Management\n\n```tsx\n\u002F\u002F Move focus when content changes\nfunction Dialog({ isOpen, onClose }: DialogProps) {\n  const closeRef = useRef\u003CHTMLButtonElement>(null);\n\n  useEffect(() => {\n    if (isOpen) closeRef.current?.focus();\n  }, [isOpen]);\n\n  \u002F\u002F Trap focus inside dialog when open\n  return (\n    \u003Cdialog open={isOpen}>\n      \u003Cbutton ref={closeRef} onClick={onClose}>Close\u003C\u002Fbutton>\n      {\u002F* dialog content *\u002F}\n    \u003C\u002Fdialog>\n  );\n}\n```\n\n### Meaningful Empty and Error States\n\n```tsx\n\u002F\u002F Don't show blank screens\nfunction TaskList({ tasks }: { tasks: Task[] }) {\n  if (tasks.length === 0) {\n    return (\n      \u003Cdiv role=\"status\" className=\"text-center py-12\">\n        \u003CTasksEmptyIcon className=\"mx-auto h-12 w-12 text-muted\" \u002F>\n        \u003Ch3 className=\"mt-2 text-sm font-medium\">No tasks\u003C\u002Fh3>\n        \u003Cp className=\"mt-1 text-sm text-muted\">Get started by creating a new task.\u003C\u002Fp>\n        \u003CButton className=\"mt-4\" onClick={onCreateTask}>Create Task\u003C\u002FButton>\n      \u003C\u002Fdiv>\n    );\n  }\n\n  return \u003Cul role=\"list\">...\u003C\u002Ful>;\n}\n```\n\n## Responsive Design\n\nDesign for mobile first, then expand:\n\n```tsx\n\u002F\u002F Tailwind: mobile-first responsive\n\u003Cdiv className=\"\n  grid grid-cols-1      \u002F* Mobile: single column *\u002F\n  sm:grid-cols-2        \u002F* Small: 2 columns *\u002F\n  lg:grid-cols-3        \u002F* Large: 3 columns *\u002F\n  gap-4\n\">\n```\n\nTest at these breakpoints: 320px, 768px, 1024px, 1440px.\n\n## Loading and Transitions\n\n```tsx\n\u002F\u002F Skeleton loading (not spinners for content)\nfunction TaskListSkeleton() {\n  return (\n    \u003Cdiv className=\"space-y-3\" aria-busy=\"true\" aria-label=\"Loading tasks\">\n      {Array.from({ length: 3 }).map((_, i) => (\n        \u003Cdiv key={i} className=\"h-12 bg-muted animate-pulse rounded\" \u002F>\n      ))}\n    \u003C\u002Fdiv>\n  );\n}\n\n\u002F\u002F Optimistic updates for perceived speed\nfunction useToggleTask() {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: toggleTask,\n    onMutate: async (taskId) => {\n      await queryClient.cancelQueries({ queryKey: ['tasks'] });\n      const previous = queryClient.getQueryData(['tasks']);\n\n      queryClient.setQueryData(['tasks'], (old: Task[]) =>\n        old.map(t => t.id === taskId ? { ...t, done: !t.done } : t)\n      );\n\n      return { previous };\n    },\n    onError: (_err, _taskId, context) => {\n      queryClient.setQueryData(['tasks'], context?.previous);\n    },\n  });\n}\n```\n\n## See Also\n\nFor detailed accessibility requirements and testing tools, see `references\u002Faccessibility-checklist.md`.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"Accessibility is a nice-to-have\" | It's a legal requirement in many jurisdictions and an engineering quality standard. |\n| \"We'll make it responsive later\" | Retrofitting responsive design is 3x harder than building it from the start. |\n| \"The design isn't final, so I'll skip styling\" | Use the design system defaults. Unstyled UI creates a broken first impression for reviewers. |\n| \"This is just a prototype\" | Prototypes become production code. Build the foundation right. |\n| \"The AI aesthetic is fine for now\" | It signals low quality. Use the project's actual design system from the start. |\n\n## Red Flags\n\n- Components with more than 200 lines (split them)\n- Inline styles or arbitrary pixel values\n- Missing error states, loading states, or empty states\n- No keyboard navigation testing\n- Color as the sole indicator of state (red\u002Fgreen without text or icons)\n- Generic \"AI look\" (purple gradients, oversized cards, stock layouts)\n\n## Verification\n\nAfter building UI:\n\n- [ ] Component renders without console errors\n- [ ] All interactive elements are keyboard accessible (Tab through the page)\n- [ ] Screen reader can convey the page's content and structure\n- [ ] Responsive: works at 320px, 768px, 1024px, 1440px\n- [ ] Loading, error, and empty states all handled\n- [ ] Follows the project's design system (spacing, colors, typography)\n- [ ] No accessibility warnings in dev tools or axe-core\n",{"name":5,"description":7},"main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Design\u002FUI_UX_and_Design_Systems\u002Ffrontend-ui-engineering",1,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills","https:\u002F\u002Fhamzabellouch.github.io\u002F","https:\u002F\u002Fgithub.com\u002Fhamzabellouch","hamzabellouch.github.io","CEO & Founder of @tknoglobal | Researcher in Technology & Applied Sciences.","2026-10-17 03:20:19",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add hamzabellouch\u002Fagent-skills --skill frontend-ui-engineering",{"tool":40,"command":41},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill frontend-ui-engineering",{"tool":43,"command":44},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill frontend-ui-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FDesign\u002FUI_UX_and_Design_Systems\u002Ffrontend-ui-engineering\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M79FHH2H815A9TAP6WNKH4Q8","security-audit","Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FSecurity_Audit_and_Code_Review\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79FHBGXVBY6VQ1X7ETAZMF1","malware-analysis-reversing","Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static\u002Fdynamic binary analysis, memory forensics, and YARA detection rule authoring.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fmalware-analysis-reversing\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79FH6EACDR801TZCE4R8SAC","application-security-pentesting","Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST\u002FDAST pipeline integration, secure code review, threat modeling, and defensive security posture.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fapplication-security-pentesting\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79FH0VKVT44FK923K520ZQA","oauth2-oidc-security-flows","Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Foauth2-oidc-security-flows\u002FSKILL.md",[],[],{"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},"01M79FGVVB3R4T88XXD8FRSV5B","jwt-session-management-hardening","Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256\u002FEdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Fjwt-session-management-hardening\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},"01M79FGNCPZ85CVEY0B3NE4H3B","soc2-compliance-automation","Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI\u002FCD security gates.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FGovernance_Compliance_and_Legal_Tech\u002Fsoc2-compliance-automation\u002FSKILL.md",[],[]]