agentleFS
ea-toolkitea-toolkit/architecture-catalog/.claude/skills/scaffold-component/SKILL.md

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

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    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.

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
  1. Distinctive:

    If no argument is provided, ask the user for a component name.

    line 19
  2. Distinctive:

    Ask the user if unclear.

    line 30
  3. Very specific:

    Read models/registry-mapping.yaml if the component will render registry data.

    line 33
  4. Distinctive:

    Read an existing similar component in the target directory for pattern reference.

    line 34
  5. Very specific:

    Read catalog-ui/src/lib/types.ts for TypeScript interfaces.

    line 35
  6. Distinctive:

    If rendering registry data: drive all behavior from schema properties (graph_rank, layer, icon), never from type name strings

    line 43
  7. Distinctive:

    Follow the vocab-agnostic principle for core registry rendering (no type-name conditionals).

    line 88
  8. Distinctive:

    No hardcoded display data — all data from props, config files, or data imports.

    line 90

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

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

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

  1. Parse component name from $ARGUMENTS. Ensure PascalCase.
  2. 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.
  3. Read existing context:
    • Read models/registry-mapping.yaml if the component will render registry data.
    • Read an existing similar component in the target directory for pattern reference.
    • Read catalog-ui/src/lib/types.ts for TypeScript interfaces.
  4. 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
  5. Create test file (ComponentName.test.tsx in 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
  6. 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 !important in CSS unless overriding third-party styles.

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.