scaffold-component
Skill38 starsChanged 9 months agoMITView on GitHub
Scaffold a new React component with test file for the catalog UI.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- TarasTsavolyk/claude-code-frontendtheir own version, first seen Aug 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- TarasTsavolyk/claude-code-frontend★ 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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- crawl-apisSkill
- crawl-dataSkill
- dashboardSkill
- deploySkill
- enterprise-platform-archiSkill
- new-entrySkill
- validateSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
If no argument is provided, ask the user for a component name.
- Distinctive: line 30
Ask the user if unclear.
- Very specific: line 33
Read models/registry-mapping.yaml if the component will render registry data.
- Distinctive: line 34
Read an existing similar component in the target directory for pattern reference.
- Very specific: line 35
Read catalog-ui/src/lib/types.ts for TypeScript interfaces.
- Distinctive: line 43
If rendering registry data: drive all behavior from schema properties (graph_rank, layer, icon), never from type name strings
- Distinctive: line 88
Follow the vocab-agnostic principle for core registry rendering (no type-name conditionals).
- Distinctive: line 90
No hardcoded display data — all data from props, config files, or data imports.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Scaffold Component
Scaffold a new React component in catalog-ui/src/components/ with a co-located test file.
Arguments
$ARGUMENTS should be a PascalCase component name (e.g., CapabilityHeatmap, DomainSummaryCard).
If no argument is provided, ask the user for a component name.
Workflow
- Parse component name from
$ARGUMENTS. Ensure PascalCase. - Determine target directory based on component purpose:
- Graph/visualization component →
catalog-ui/src/components/graphs/ - Diagram viewer →
catalog-ui/src/components/ - Layout/navigation →
catalog-ui/src/components/(or subdirectory if pattern exists) - General →
catalog-ui/src/components/ - Ask the user if unclear.
- Graph/visualization component →
- Read existing context:
- Read
models/registry-mapping.yamlif the component will render registry data. - Read an existing similar component in the target directory for pattern reference.
- Read
catalog-ui/src/lib/types.tsfor TypeScript interfaces.
- Read
- Create component file (
ComponentName.tsx):- Export Props interface:
export interface ComponentNameProps { ... } - Named export (not default):
export const ComponentName: React.FC<ComponentNameProps> = ... - CSS via
--ec-*variables (never inline styles) - Semantic HTML (nav, main, section, article — not div for everything)
- Accessible: aria labels on interactive elements
- If rendering registry data: drive all behavior from schema properties (graph_rank, layer, icon), never from type name strings
- Export Props interface:
- Create test file (
ComponentName.test.tsxin same directory or__tests__/):- At minimum: one render/smoke test + one behavioral test
- Use Vitest (
import { describe, it, expect } from 'vitest') - Mock external dependencies (ReactFlow, data loaders) if needed
- Verify types:
cd catalog-ui && npx tsc --noEmit
Template Pattern
// ComponentName.tsx
import type React from 'react';
export interface ComponentNameProps {
// Define props here
}
export const ComponentName: React.FC<ComponentNameProps> = (props) => {
return (
<section aria-label="Component description">
{/* Component content */}
</section>
);
};// ComponentName.test.tsx
import { describe, it, expect } from 'vitest';
describe('ComponentName', () => {
it('should render without crashing', () => {
// Render test
});
it('should handle user interaction', () => {
// Behavioral test
});
});Rules
- Follow the vocab-agnostic principle for core registry rendering (no type-name conditionals).
- Map views (event, heatmap) are intentionally type-aware — that's fine.
- No hardcoded display data — all data from props, config files, or data imports.
- No
!importantin CSS unless overriding third-party styles.
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.

