React Component Craft Skill for Codex

Craft polished React components for websites and apps. Use for reusable sections, UI primitives, composition, props, state, responsive behavior, interaction states, accessibility, and avoiding monolithic or brittle frontend implementations.

1k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

115

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/TheGoat395/Codex-Skills --skill react-component-craft

What comes with it

2 064 bytes besides the instruction

agents/openai.yaml

references/react-component-craft-guide.md

The instruction itself

5 sections, as written by the author

React Component Craft

Overview

Build components that are reusable without becoming abstract sludge. Good components express local design patterns and keep the page easy to revise.

Website Nonnegotiables

Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands.
Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix.
Use existing project conventions first. Explain major new dependencies before adding them.
Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes.
Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again.
Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly.
Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

Workflow

Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability.
Inspect the project before editing when code exists.
Apply this skill's specific rules from references/react-component-craft-guide.md.
Explain planned files before major changes unless the user has clearly said to proceed.
Build, inspect, polish, and verify before final delivery.

Reference

Read references/react-component-craft-guide.md when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

Other skills for the same job

different authors, same section of the catalogue

Use Dom

by openai

vendor ×3

Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.

3k tokens

Frontend Dev Guidelines

by mrgoonie

×2

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

33k tokens

Next Cache Components

by vercel-labs

vendor ×2

Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag

| Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid. "shopify theme", "liquid template", "polaris", "shopify graphql", "shopify webhook", "shopify billing", "app subscription", "metafields", "shopify functions"

Build Gradio web UIs and demos in Python. Use when creating or editing Gradio apps, components, event listeners, layouts, or chatbots.

10k tokens

Figma Generate Diagram

by openai

vendor ×1

MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).

Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.

Algorithmic philosophies are computational aesthetic movements that are then expressed through code. Output .md files (philosophy), .html files (interactive viewer), and .js files (generative algorithms).

15k tokens scripts

How to use it

Copy the folder

Take thegoat395/react-component-craft from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.