Agent skill

Creating Components

A skill your agent uses when creating new UI components in packages/ui.

AGPL-3.0Auto-check passedFrontend & Design

Install Creating Components

skills CLI

$ npx skills add nukeop/nuclear --skill creating-components -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nukeop/nuclear creating-components --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nukeop/nuclear.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/creating-components .claude/skills/creating-components && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "creating-components" agent skill from https://github.com/nukeop/nuclear/tree/master/.agents/skills/creating-components into .claude/skills/creating-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-components", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nukeop/nuclear/tree/master/.agents/skills/creating-components

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nukeop/nuclear --skill creating-components -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nukeop/nuclear creating-components --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nukeop/nuclear.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/creating-components .agents/skills/creating-components && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "creating-components" agent skill from https://github.com/nukeop/nuclear/tree/master/.agents/skills/creating-components into .agents/skills/creating-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-components", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nukeop/nuclear --skill creating-components -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nukeop/nuclear creating-components --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nukeop/nuclear.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/creating-components .cursor/skills/creating-components && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "creating-components" agent skill from https://github.com/nukeop/nuclear/tree/master/.agents/skills/creating-components into .cursor/skills/creating-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-components", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nukeop/nuclear.git --path .agents/skills/creating-components

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nukeop/nuclear --skill creating-components -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nukeop/nuclear creating-components --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nukeop/nuclear.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/creating-components .gemini/skills/creating-components && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "creating-components" agent skill from https://github.com/nukeop/nuclear/tree/master/.agents/skills/creating-components into .gemini/skills/creating-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-components", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nukeop/nuclear creating-components

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nukeop/nuclear --skill creating-components -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nukeop/nuclear.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/creating-components .github/skills/creating-components && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "creating-components" agent skill from https://github.com/nukeop/nuclear/tree/master/.agents/skills/creating-components into .github/skills/creating-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-components", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nukeop/nuclear --skill creating-components -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nukeop/nuclear creating-components --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nukeop/nuclear.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/creating-components .opencode/skills/creating-components && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "creating-components" agent skill from https://github.com/nukeop/nuclear/tree/master/.agents/skills/creating-components into .opencode/skills/creating-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-components", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: creating-components
GitHub stars: 19k
Token cost: ~1k tokens
SKILL.md length: 323 words
Files: 1
Skills in repo: 5
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

A skill your agent uses when creating new UI components in packages/ui.

Creating new UI components in packages/ui
SKILL.md covers Component Structure, Implementation Pattern, Tests and Stories, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Creating Components is an agent skill from nukeop/nuclear. Use when creating new UI components in packages/ui. Covers component structure, tests, stories, and what to avoid.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design. It works with TypeScript and Model Context Protocol. The repository describes itself as: Streaming music player that finds free music for you. The licence is AGPL-3.0.

When your agent uses it

Creating new UI components in packages/ui

Example prompts

“/creating-components”

What it can do on your machine

Read from SKILL.md and the folder at commit 27904e9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Creating Components loads about 1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 323 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~34
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nukeop/nuclear at commit 27904e9, republished under its AGPL-3.0 licence (© nukeop). 323 words, ~1,029 tokens.

Download SKILL.mdSave it as .claude/skills/creating-components/SKILL.md (or your agent's skills folder).

name: creating-components
description: Use when creating new UI components in packages/ui. Covers component structure, tests, stories, and what to avoid.

Creating UI Components

Component Structure

packages/ui/src/components/MyComponent/
├── MyComponent.tsx      # Implementation
├── MyComponent.test.tsx # Tests
├── index.ts             # Re-exports
└── __snapshots__/       # Vitest snapshots (auto-generated)

After creating, export from packages/ui/src/components/index.ts.

Implementation Pattern

tsx

import { cva, VariantProps } from 'class-variance-authority';
import { ComponentProps, FC } from 'react';
import { cn } from '../../utils';

const variants = cva('base-classes', {
  variants: { /* ... */ },
  defaultVariants: { /* ... */ },
});

type MyComponentProps = ComponentProps<'div'> & VariantProps<typeof variants>;

export const MyComponent: FC<MyComponentProps> = ({
  className,
  variant,
  ...props
}) => (
  <div className={cn(variants({ variant, className }))} {...props} />
);

Tests

What to test:

Snapshots (1-2 covering key variants)
User interactions
Behavior (callbacks called with correct args)

What NOT to test:

CSS classes, attributes (use snapshots instead)
Internal state
Things TypeScript already enforces

Consolidate tests. One test can cover multiple related assertions. An exception to that is snapshot tests - one snapshot per variant/state.

Stories

Create packages/storybook/src/MyComponent.stories.tsx.

One story can show multiple related variants. For example, it's wasteful to create a story for each variant of a button. Put them all together in one place. Don't create separate stories for each variant:

tsx

import { Meta, StoryObj } from '@storybook/react-vite';
import { useState } from 'react';
import { MyComponent } from '@nuclearplayer/ui';

const meta = {
  title: 'Components/MyComponent',
  component: MyComponent,
  tags: ['autodocs'],
} satisfies Meta<typeof MyComponent>;

export default meta;
type Story = StoryObj<typeof MyComponent>;

export const AllVariants: Story = {
  render: () => {
    const [state, setState] = useState(initialState);
    return (
      <div className="flex flex-col gap-4">
        {/* Show all variants, states, interactions */}
      </div>
    );
  },
};

This isn't an iron rule, sometimes it will make more sense to have separate stories.

Don't run storybook build checks.

Avoiding Duplication

Before creating a new component, check if an existing one can be extended.

Pattern: Discriminated unions for mode variants

Example: Instead of creating SingleSelect and MultiSelect components:

tsx

type Props = 
  | { multiple?: false; selected: string; onChange: (id: string) => void }
  | { multiple: true; selected: string[]; onChange: (ids: string[]) => void };

TypeScript enforces correct types based on the multiple prop.

Classes for customization

Where it's likely that a component will need custom styling, expose a className prop.

If there are many parts that may need styling, consider exposing a classes prop with specific class names for each part. Define a type for the classes prop. Refer to packages/ui/src/components/TrackTable/types.ts for an example.

Strings

All user-facing strings go through i18n - no hardcoded UI text. If a new component in the ui package needs labels and other kinds of localized text, it should accept a labels prop with the relevant strings. The prop should have its own type defined. Refer to packages/ui/src/components/QueueItem/types.ts for an example.

Accessibility

We don't care about that. If there's an opportunity to handle that easily, do it, but don't go out of your way.

Checklist

Component in packages/ui/src/components/MyComponent/
Exported from packages/ui/src/components/index.ts
Tests cover behavior, not implementation
Tests consolidated (not one per variant)
One story showing all variants
No CSS class assertions in tests
No duplicate component when extending existing one works

Files

Just SKILL.md in .agents/skills/creating-components of nukeop/nuclear.

Open the folder on GitHubat commit 27904e9

Compare with similar skills

Creating Components next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Creating Components compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Creating Components this skillnukeop/nuclear	19k	—	~1k	Automated safety check: Pass	AGPL-3.0	yesterday
Create Docsvictorgarciaesgi/nuxt-typed-router	413	2 repos	~2.8k	Automated safety check: Pass	MIT	yesterday
Jarvis Setupethanplusai/jarvis	838	—	~2.5k	Automated safety check: Notes	Custom licence	27 days ago
Wonder BlocksKhan/wonder-blocks	163	—	~3.2k	Automated safety check: Pass	MIT	today
Loora Design Guidelassejlv/loora	140	—	~2.4k	Automated safety check: Pass	AGPL-3.0	10 days ago
Mastra Honojwynia/agent-skills	165	—	~2.9k	Automated safety check: Pass	MIT	7 mo ago

Similar skills

Create Docs
victorgarciaesgi/nuxt-typed-router
Create complete documentation sites for projects. An agent skill from victorgarciaesgi/nuxt-typed-router.
413 GitHub starsUsed in 2 repos~2.8k tokens
Frontend & DesignAuto-check passed
Jarvis Setup
ethanplusai/jarvis
A skill your agent uses when helping someone install, configure, or debug a fresh clone of JARVIS (this repo) — especially "the mic doesn't work", "JARVIS says his language systems are down", any…
838 GitHub stars~2.5k tokensUpdated 27 days ago
Frontend & DesignAuto-check: notes
Wonder Blocks
Khan/wonder-blocks
Implements user interfaces using the Wonder Blocks (WB) design system — Khan Academy's React component library.
163 GitHub stars~3.2k tokensUpdated today
Frontend & DesignAuto-check passed
Loora Design Guide
lassejlv/loora
Build, edit, refine, troubleshoot, and review polished responsive product interfaces through the Loora MCP server and its structured Canvas schemas.
140 GitHub stars~2.4k tokensUpdated 10 days ago
Frontend & DesignAuto-check passed
Mastra Hono
jwynia/agent-skills
Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.
165 GitHub stars~2.9k tokensUpdated 7 mo ago
Frontend & DesignAuto-check passed
Frontend Dev
nteract/nteract
Frontend development for nteract UI/product surfaces, Elements fixtures, hot reload, dev daemon setup, MCP server workflow, TypeScript bindings via ts-rs, and reactive state work that touches RxJS…
178 GitHub stars~5.4k tokensUpdated today
Frontend & DesignAuto-check passed

Questions about Creating Components

What does Creating Components do?

A skill your agent uses when creating new UI components in packages/ui. Creating Components is an agent skill from nukeop/nuclear. Use when creating new UI components in packages/ui.

When should I use Creating Components?

Creating Components fits situations like: creating new UI components in packages/ui.

How do I install Creating Components in Claude Code?

Run `npx skills add nukeop/nuclear --skill creating-components -a claude-code`. Or copy the skill folder (.agents/skills/creating-components in nukeop/nuclear) into .claude/skills/creating-components in your project. Claude Code loads it when a task matches its description.

How do I install Creating Components in Codex?

Run `npx skills add nukeop/nuclear --skill creating-components -a codex`. Or copy the skill folder (.agents/skills/creating-components in nukeop/nuclear) into .agents/skills/creating-components in your project. Codex loads it when a task matches its description.

Can I use Creating Components in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nukeop/nuclear --skill creating-components -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-components, .gemini/skills/creating-components, .github/skills/creating-components and .opencode/skills/creating-components in your project.

What does Creating Components need to run?

SKILL.md names no scripts, command-line tools or credentials: Creating Components is instructions for the agent only.

Does Creating Components access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Creating Components safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Creating Components use?

Creating Components is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Creating Components use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Creating Components?

Skills that share tags, products or a category with Creating Components: Create Docs (victorgarciaesgi/nuxt-typed-router, 413 stars), Jarvis Setup (ethanplusai/jarvis, 838 stars), Wonder Blocks (Khan/wonder-blocks, 163 stars) and Loora Design Guide (lassejlv/loora, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Creating Components?

nukeop (a GitHub user) maintains it in nukeop/nuclear, which has 18,611 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.

Source: nukeop/nuclear on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Creating Components

Install Creating Components

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Creating UI Components

Component Structure

Implementation Pattern

Tests

Stories

Avoiding Duplication

Classes for customization

Strings

Accessibility

Checklist

Files

Compare with similar skills

Similar skills

Create Docs

Jarvis Setup

Wonder Blocks

Loora Design Guide

Mastra Hono

Frontend Dev

More from nukeop/nuclear

Making Demo Videos

Host Pattern

Writing Docs

Writing Plugins

Questions about Creating Components

Install Creating Components

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Creating UI Components

Component Structure

Implementation Pattern

Tests

Stories

Avoiding Duplication

Classes for customization

Strings

Accessibility

Checklist

Files

Compare with similar skills

Similar skills

More from nukeop/nuclear

Related

Questions about Creating Components