agentleFS
Sign inStart free
irwebtoolsirwebtools/Product-Skills/skills/optional/component-design/SKILL.md

component-design

Skill0 starsChanged 2 months agoMITView on GitHub

Design React components with clear FSD ownership and public APIs.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when splitting UI into reusable React components inside an FSD slice.

    line 10
  2. Distinctive:

    Keep components owned by the correct layer and avoid cross-feature dumping.

    line 14
  3. Distinctive:

    Place business UI in the owning feature/entity slice.

    line 24
  4. Distinctive:

    Prefer composition over global utility helpers for business logic.

    line 27
  5. Distinctive:

    Keep TypeScript props explicit and stable.

    line 28
  6. Very specific:

    No business feature dumped into src/components.

    line 39
  7. Distinctive:

    Do not create global component warehouses for business features.

    line 45
  8. Distinctive:

    Do not bypass architecture decision for "faster demo".

    line 46

≈ “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

component-design

When to use

Use when splitting UI into reusable React components inside an FSD slice.

Purpose

Keep components owned by the correct layer and avoid cross-feature dumping.

Input

  • UX flow states and interactions
  • Architecture Decision Record
  • Existing shared UI primitives (if any)

Process

  1. Place business UI in the owning feature/entity slice.
  2. Extract truly shared primitives to shared/ui only when reused.
  3. Expose public API through the slice index/public file.
  4. Prefer composition over global utility helpers for business logic.
  5. Keep TypeScript props explicit and stable.

Output

  • Component ownership map
  • Public API notes
  • Reuse decisions

Verification

  • Components live under ADR locations.
  • No business feature dumped into src/components.
  • Shared extraction is justified by reuse, not convenience.

Restrictions

  • React + TypeScript + FSD only.
  • Do not create global component warehouses for business features.
  • Do not bypass architecture decision for "faster demo".

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