component
Skill52 starsChanged 49 days agoMITView on GitHub
Create a UI component. Triggers "create component", "new component", "add component", or naming a component to build (Button, Header, Card).
8 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/vscodetheir own version, first seen Nov 2, 2026
- vansh-nagar/Pixel-Perfecttheir own version, first seen Nov 1, 2026
- MohammadShehadeh/agent-skillstheir own version, first seen Nov 1, 2026
- gabriellst/codmtheir own version, first seen Aug 26, 2026
- asw101/ai-skillstheir own version, first seen Aug 21, 2026
- Maximepodgorski/agent-skillstheir own version, first seen May 3, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- microsoft/vscode★ 195ksame name
- vansh-nagar/Pixel-Perfect★ 748same name
- Maximepodgorski/agent-skills★ 21same name
- gabriellst/codm★ 4same name
- asw101/ai-skills★ 3same name
- MohammadShehadeh/agent-skills★ 2same name
- gauravv-g/claude-skills-collection★ 1same name
- silverkyoon-Rachel/claude-skills★ 0same 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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/AGENTS.mdAGENTS.md
- auditSkill
- autoresearchSkill
- buildSkill
- case-studySkill
- ccSkill
- codexSkill
- context-docSkill
- dr-initSkill
- dr-reviewSkill
- fixSkill
- freezeSkill
- handoffSkill
- harvestSkill
- hookSkill
- orchestrateSkill
- poke-holesSkill
- proof-of-workSkill
- refactorSkill
- retroSkill
- review-batchSkill
- share-learningSkill
- shipSkill
- storiesSkill
- triageSkill
- zero-tech-debtSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
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
- Very specific: line 9
Create a React component following Darkroom conventions.
- Distinctive: line 58
If this component wraps or uses an external library (Radix, Framer Motion, GSAP, etc.):
- Distinctive: line 62
Never implement against external library APIs from memory.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Create Darkroom Component
Create a React component following Darkroom conventions. Detect the stack first — satus (Next.js) and novus (React Router) have different conventions for client/server boundaries, image/link wrappers, and path aliases.
Step 1 — Detect stack
Read package.json:
dependencies.nextpresent → Next.js / satus conventionsdependencies["react-router"]ordevDependencies["@react-router/dev"]→ React Router / novus conventions- Neither → ask user, or assume satus if unclear
Step 2 — Resolve target paths
| Stack | Component path | CSS module path | Image wrapper | Link wrapper | Path alias |
| satus (Next.js) | components/<name>/index.tsx | components/<name>/<name>.module.css | import { Image } from '@/components/image' | import { Link } from '@/components/link' | @/ |
| novus (React Router) | components/<name>/index.tsx | components/<name>/<name>.module.css | Native <img> with explicit width/height/fetchPriority (or project's wrapper if it exists) | import { Link } from 'react-router' | ~/ |
Step 3 — Emit template
// components/<name>/index.tsx
// satus (Next.js): Server Component by default. Add 'use client' only if the
// component needs hooks, event handlers, or browser APIs (--client forces it).
// novus (React Router): components are isomorphic, never add 'use client'.
import s from './<name>.module.css'
interface <Name>Props {
children?: React.ReactNode
className?: string
}
export function <Name>({ children, className }: <Name>Props) {
return (
<div className={`${s.<name>} ${className ?? ''}`}>
{children}
</div>
)
}/* components/<name>/<name>.module.css */
.<name> {
/* Component styles */
}Before you start
If this component wraps or uses an external library (Radix, Framer Motion, GSAP, etc.):
- Fetch docs first — use Context7 MCP (
mcp__context7__resolve-library-id→get-library-docs) for the current API in Claude or when the user configured it in standalone Codex. Otherwise use official docs through native browsing or inspect the pinned local package. cc-settings does not auto-run unpinned registry MCP packages in Codex. - Check version — run
bun info <package>before installing.
Never implement against external library APIs from memory.
Conventions
- CSS Module as
s— always import assfor consistency. - Props interface — define explicitly, include
classNamefor composition. - Named export — use
export function, notexport default. - No memoization — React Compiler handles it.
Arguments
$ARGUMENTS— Component name (e.g., "Button", "Header")--clientflag (Next.js only) — Force client component
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

