create-component

create-component is a skill for Claude Code, Codex, Cursor from leboncoin/spark-web. It costs 44 tokens per session (714 once invoked), scanned A, original, MIT.

A recipe for creating a Spark UI component with its code, styling, tests, Storybook examples, exports, and documentation. It follows the project's TypeScript, accessibility, and styling conventions.

In plain words
What is it for?
It is for adding a new component or implementing one from a design, including its styles, unit tests, stories, and user-facing documentation.
Why use it?
It removes the need to remember the design system's required files and implementation rules when adding a component.

Skill for Claude CodeCodexCursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/leboncoin/spark-web/create-component
Any agent
npx skills add leboncoin/spark-web --skill create-component
Clone the repo
git clone --depth 1 https://github.com/leboncoin/spark-web

Made for: Claude Code, Codex, Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-component

README.md
[![agentmods](https://agentmods.dev/badge/skills/leboncoin/spark-web/create-component.svg)](https://agentmods.dev/skills/leboncoin/spark-web/create-component)
Your own site
<a href="https://agentmods.dev/skills/leboncoin/spark-web/create-component"><img src="https://agentmods.dev/badge/skills/leboncoin/spark-web/create-component.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 714 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00714
Opus 5 $0.00022 $0.00357
Sonnet 5 $0.00009 $0.00143
Haiku 4.5 $0.00004 $0.00071

Measured today against content hash 880d935955e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-component scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/skills/create-component/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Component

Create a new Spark UI component following the project's standards and file structure.

When to Use

  • User wants to create a new component
  • User mentions "new component", "add component", or "create component"
  • User is implementing a component from a design

Instructions

  1. Determine component location: Components go in packages/components/src/<component-name>/

  2. Create the file structure:

    component-name/
    ├── ComponentName.tsx           # Main component
    ├── ComponentName.styles.tsx    # Styling with CVA
    ├── ComponentName.test.tsx      # Unit tests
    ├── ComponentName.stories.tsx   # Storybook stories
    ├── ComponentName.doc.mdx       # Documentation
    ├── index.ts                    # Exports
    └── variants/                   # Style variants (if applicable)
    
  3. Component Implementation:

    • Use TypeScript with strict typing
    • Implement polymorphic behavior with asChild prop if needed
    • Use CVA (Class Variance Authority) for styling variants
    • Include data-spark-component attribute
    • Ensure WCAG 2.1 AA compliance
    • Use proper ARIA attributes
  4. Styling:

    • Create ComponentName.styles.tsx with CVA
    • Define variants (size, variant, etc.)
    • Use TailwindCSS classes
  5. Tests:

    • Create ComponentName.test.tsx with Vitest + React Testing Library
    • Test rendering, props, variants, and accessibility
    • Test user interactions
  6. Stories:

    • Create ComponentName.stories.tsx following Storybook CSF format
    • Use Components/* meta structure
    • Create stories for: Default, Uncontrolled, Controlled, and other variants
    • One story per prop/feature
  7. Documentation:

    • Create ComponentName.doc.mdx with sections in this order:
      • Title (H1)
      • Meta (link to stories)
      • Install
      • Import
      • Props table (using ArgTypes component)
      • Usage (Default, Uncontrolled, Controlled, others alphabetically)
      • Advanced Usage
      • Accessibility

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 88 lines · 44 tokens per session scan A 880d935955e4

Subscribe to this mod's changes

create-component is a skill published in the GitHub repository leboncoin/spark-web (93 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 714 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.

Related

Other skills, from other repositories

material-ui-review

Review the current diff for regressions, correctness bugs, tests, simplifications, and docs issues, scaling depth to a low/medium/high/xhigh/max effort level. Use ONLY when explicitly requested by name: the user runs /material-ui-review, writes $material-ui-review, or asks for "the Material UI review skill". Do NOT…

mui/material-ui · 137 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

chakra-ui-migrate

Migrate Chakra UI projects from v2 to v3, covering package changes, codemods, provider setup, color mode, prop renaming, compound components, theming, recipes, and Next.js updates. Use this skill whenever a user is upgrading Chakra UI versions, encountering breaking changes after an upgrade, converting old v2 patterns…

chakra-ui/chakra-ui · 137 tokens

chakra-ui-refactor

Review, convert, and improve UI code using Chakra UI v3. Use this skill whenever a user wants to review Chakra UI code for issues, convert plain HTML/CSS, Tailwind, CSS Modules, or styled-components to Chakra UI, clean up messy Chakra components, fix layout structure or token usage, or asks anything like "is this…

chakra-ui/chakra-ui · 139 tokens

material-ui-nextjs

Integrates Material UI with Next.js App and Pages routers using @mui/material-nextjs, Emotion cache providers, next/font, CSS layers with Tailwind/CSS Modules, Link component prop patterns, CSS theme variables SSR notes, and App Router useSearchParams + Suspense. Use when setting up or debugging MUI in a Next.js app.

mui/material-ui · 76 tokens

material-ui-styling

Chooses the right Material UI styling approach (sx, styled, theme overrides, global CSS) from official MUI guidance. Use when styling @mui/material components, customizing themes, overriding slots, or comparing sx vs styled.

mui/material-ui · 52 tokens