component-architecture
Skill0 starsChanged 6 months agoMITView on GitHub
Designs reusable frontend component architectures.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- bfernandois059/dev-workflow-skillstheir own version, first seen Oct 20, 2026
- yogvidwankhede/vishwakarmatheir own version, first seen Sep 26, 2026
- nahid-sparktales/agent-dispatchertheir own version, first seen Sep 21, 2026
- batur/ts-baseline-docstheir own version, first seen Jul 29, 2026
- sanky369/vibe-building-skillstheir own version, first seen Jul 2, 2026
- Deepak-Dhungel/claude-code-skillstheir own version, first seen Jun 4, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- nahid-sparktales/agent-dispatcher★ 59same name
- sanky369/vibe-building-skills★ 30same name
- batur/ts-baseline-docs★ 1same name
- bfernandois059/dev-workflow-skills★ 1same name
- Deepak-Dhungel/claude-code-skills★ 1same name
- yogvidwankhede/vishwakarma★ 1same 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 repository10 other files it gives its agents.
- .claude/skills/react-patterns/AGENTS.mdAGENTS.md
- accessibilitySkill
- clarify-requirementsSkill
- code-review-processSkill
- frontend-patternsSkill
- frontend-performanceSkill
- react-patternsSkill
- responsive-designSkill
- systematic-debuggingSkill
- typescriptSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 8
Use this skill when designing reusable UI components or reviewing component-library structure.
- Distinctive: line 19
Prefer composition over prop explosion.
- Distinctive: line 20
Keep components accessible by default.
- Distinctive: line 29
Test accessibility and state behavior before polishing abstractions.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Component Architecture
Use this skill when designing reusable UI components or reviewing component-library structure.
When to Use
- shaping a component API
- choosing between compound components, slots, render props, or headless primitives
- standardizing styling approach across a component layer
- refactoring large UI components into smaller reusable pieces
Core Rules
- Prefer composition over prop explosion.
- Keep components accessible by default.
- Separate structure, state, and styling responsibilities clearly.
- Choose a styling approach that matches the repo instead of mixing paradigms casually.
Core Workflow
- Define the public API and usage shape first.
- Pick the composition pattern that matches the interaction model.
- Decide how styling is applied and overridden.
- Test accessibility and state behavior before polishing abstractions.
References
- references/component-patterns.md
- references/css-styling-approaches.md
- references/accessibility-patterns.md
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
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.