component
Create UI component / widget / reusable piece. Triggers "create component", "new component", "add component", or naming a component (Button, Header, Card).
适合你,如果你经常需要创建新的UI组件或修改现有组件。
npx oh-my-skill add darkroomengineering/cc-settings/componentcurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- darkroomengineering/cc-settings/componentnpx oh-my-skill verify darkroomengineering/cc-settings/component怎么用
商店整理自技能原文 · 版本 fa04efc · 表述以原文为准装好后,当你说出创建组件的指令时,Claude会先检测项目类型(Next.js或React Router),然后自动生成符合Darkroom约定的React组件文件,包括组件代码、CSS模块和正确的导入路径。
当你提到“创建组件”、“新组件”、“添加组件”,或者直接说出组件名称(如Button、Header)时触发。也可以使用参数指定组件名和--client标志(仅Next.js)强制创建客户端组件。
技能原文 SKILL.md
Create Darkroom Component
Create a React component following Darkroom conventions. Detect the stack first — satus (Next.js) and novus (React Router) have different conventions for client/server boundaries, image/link wrappers, and path aliases.
Step 1 — Detect stack
Read package.json:
dependencies.nextpresent → Next.js / satus conventionsdependencies["react-router"]ordevDependencies["@react-router/dev"]→ React Router / novus conventions- Neither → ask user, or assume satus if unclear
Step 2 — Resolve target paths
| Stack | Component path | CSS module path | Image wrapper | Link wrapper | Path alias | |---|---|---|---|---|---| | satus (Next.js) | components/<name>/index.tsx | components/<name>/<name>.module.css | import { Image } from '@/components/image' | import { Link } from '@/components/link' | @/ | | novus (React Router) | components/<name>/index.tsx | components/<name>/<name>.module.css | Native <img> (or project's wrapper if it exists) | import { Link } from 'react-router' | ~/ |
Step 3 — Emit template
satus / Next.js
// components/<name>/index.tsx
// 'use client' — only add if component needs:
// - useState, useEffect, or other hooks
// - Event handlers (onClick, onChange, etc.)
// - Browser APIs (window, document, etc.)
import s from './<name>.module.css'
interface <Name>Props {
children?: React.ReactNode
className?: string
}
export function <Name>({ children, className }: <Name>Props) {
return (
<div className={`${s.<name>} ${className ?? ''}`}>
{children}
</div>
)
}
novus / React Router
// components/<name>/index.tsx
// React Router components are isomorphic — no directive needed.
// They run on server during SSR and on client after hydration.
import s from './<name>.module.css'
interface <Name>Props {
children?: React.ReactNode
className?: string
}
export function <Name>({ children, className }: <Name>Props) {
return (
<div className={`${s.<name>} ${className ?? ''}`}>
{children}
</div>
)
}
CSS module (both stacks)
.<name> {
/* Component styles */
}
Before you start
If this component wraps or uses an external library (Radix, Framer Motion, GSAP, etc.):
- Fetch docs first — use Context7 MCP (
mcp__context7__resolve-library-id→get-library-docs) for the current API. - Check version — run
bun info <package>before installing.
Never implement against external library APIs from memory.
Conventions (both stacks)
- CSS Module as
s— always import assfor consistency. - Props interface — define explicitly, include
classNamefor composition. - Named export — use
export function, notexport default. - No memoization — React Compiler handles it.
Conventions (satus only)
- Server Component by default — only add
'use client'if needed. - Image wrapper —
import { Image } from '@/components/image'. - Link wrapper —
import { Link } from '@/components/link'.
Conventions (novus only)
- Components are isomorphic — no
'use client'directive. - Path alias is
~/, not@/. - Link —
import { Link } from 'react-router'(declarative routing). - Images — native
<img>with explicitwidth/height/fetchPriority. No project-level wrapper unless the project added one.
Arguments
$ARGUMENTS— Component name (e.g., "Button", "Header")--clientflag (Next.js only) — Force client component
Example
User: "create a Button component" → detect stack → satus → creates components/button/index.tsx + button.module.css with @/-aliased imports User: "create a Button component" (in novus repo) → detect stack → novus → creates same files but with ~/-aliased imports and no 'use client' directive