agentleFS
Sign inStart free
Taimoorkhan1122Taimoorkhan1122/boring-react/skills/react-component-engineering/SKILL.md

react-component-engineering

Skill1 starsChanged 3 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. manish1803/nextjs-fullstack-skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add keyboard/focus behavior and accessible names/descriptions.

    line 23
  2. Distinctive:

    Add loading, empty, error, disabled, pending, and permission states that apply.

    line 24
  3. Distinctive:

    Add motion only when it communicates state or spatial relationship.

    line 25
  4. Distinctive:

    Verify keyboard, zoom/reflow, long content, and representative viewports.

    line 26
  5. Distinctive:

    Use native semantic elements first.

    line 30
  6. Distinctive:

    Every interactive control must be keyboard operable with visible focus.

    line 33
  7. Distinctive:

    Do not use placeholder text as the only label.

    line 34
  8. Distinctive:

    Do not encode meaning by color alone.

    line 35
  9. Distinctive:

    Avoid boolean-prop explosions and component APIs that expose internal implementation details.

    line 38
  10. Distinctive:

    Do not make desktop layouts merely “shrink”.

    line 39
  11. Distinctive:

    add an appropriate shadcn/ui primitive when the repository intentionally uses it.

    line 46
  12. Distinctive:

    create a new primitive only when no suitable existing primitive exists.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free