Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

react-component-engineering

Build and review accessible, responsive, design-system-aligned React components and screens. Use for JSX/TSX, semantic HTML, Tailwind, shadcn/ui, component APIs, forms, dialogs, tables, responsive layouts, loading/error/empty states, or frontend design review.

Taimoor Khan · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add Taimoorkhan1122/boring-react --skill react-component-engineering

About this skill


name: react-component-engineering description: Build and review accessible, responsive, design-system-aligned React components and screens. Use for JSX/TSX, semantic HTML, Tailwind, shadcn/ui, component APIs, forms, dialogs, tables, responsive layouts, loading/error/empty states, or frontend design review. license: MIT compatibility: React projects; applies across Next.js, Vite, and component libraries. metadata: author: Taimoor Khan version: "1.0.0"

React Component Engineering

Build interfaces that remain understandable to users, assistive technologies, future maintainers, and different viewport/input modes.

Apply react-production-engineering for architecture/state/data decisions.

Workflow

  1. Identify the user task and the semantic structure before styling.
  2. Reuse the existing design system before creating primitives.
  3. Define the component API and all meaningful states.
  4. Implement mobile/narrow behavior first enough to prove reflow, then widen intentionally.
  5. Add keyboard/focus behavior and accessible names/descriptions.
  6. Add loading, empty, error, disabled, pending, and permission states that apply.
  7. Add motion only when it communicates state or spatial relationship.
  8. Verify keyboard, zoom/reflow, long content, and representative viewports.

Non-negotiable rules

  • Use native semantic elements first. Actions are buttons; navigation is links; tabular relationships use tables.
  • ARIA supplements native semantics; it does not repair avoidable div-based controls.
  • WCAG 2.2 AA is the baseline for product UI.
  • Every interactive control must be keyboard operable with visible focus.
  • Do not use placeholder text as the only label.
  • Do not encode meaning by color alone.
  • Respect reduced-motion preferences.
  • Reuse product/design-system primitives before cloning a near-duplicate.
  • Avoid boolean-prop explosions and component APIs that expose internal implementation details.
  • Do not make desktop layouts merely “shrink”; design the narrow state deliberately.

Design-system precedence

  1. existing product design system;
  2. existing shared component library;
  3. shadcn/ui primitives already present;
  4. add an appropriate shadcn/ui primitive when the repository intentionally uses it;
  5. create a new primitive only when no suitable existing primitive exists.

When to load references

  • Accessibility/semantics/focus: references/accessibility.md
  • Responsive design/content stress: references/responsive-design.md
  • Component API/composition: references/component-api-design.md
  • shadcn/ui/Tailwind design-system work: references/shadcn.md
  • Forms: references/forms.md
  • Tables/data-dense UI: references/tables.md
  • UI/design review output: references/design-review.md

Activate react-quality-engineering when implementation requires test strategy, Playwright, axe, or visual regression.

Review output

For UI reviews, prioritize: verdict, blockers, major issues, accessibility, responsive behavior, design-system compliance, then minor polish. User impact outranks personal aesthetic preference.