메뉴
Add a reusable Oriant component to the horisont-components GitHub-backed shadcn registry. Use when extracting, registering, documenting, or validating a component for `shadcn add 4ug-aug/horisont-components/<item>`.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/4ug-aug/horisont-components --skill add-registry-component명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | add-registry-component |
| description | Add a reusable Oriant component to the horisont-components GitHub-backed shadcn registry. Use when extracting, registering, documenting, or validating a component for `shadcn add 4ug-aug/horisont-components/<item>`. |
Use this repository as the canonical source for published components. Extract only presentational, reusable code; leave product data fetching, routes, copy tied to Oriant, and credentials in Oriant.
Inspect registry.json and each included registry before editing. Every include and every declared file must exist; repair stale scaffold entries as part of the change when they block validation.
Check the Oriant source and every caller. Preserve accessibility, reduced-motion handling, cleanup, and real dependency requirements. Do not copy upstream shadcn primitives that users can install directly.
Put the source beside its registry file. UI components belong in components/ui/<name>.tsx; add its item to components/ui/registry.json. Paths in that file are relative to components/ui/registry.json.
Keep the public API small. Use standard shadcn imports such as @/lib/utils, never Oriant aliases such as #/. Add 'use client' when the component uses hooks or browser APIs.
Declare the complete item: name, type, title, description, and files. List shadcn items in registryDependencies and npm packages in dependencies; include every source file needed by the item. Do not add a target unless the default shadcn destination is wrong.
Add the install command and requirements to README.md when publishing a new public item:
pnpm dlx shadcn@latest add 4ug-aug/horisont-components/<item>
Before push, parse every edited JSON file and confirm each registry path exists. After the change is pushed to the public repository, run:
pnpm dlx shadcn@latest registry validate 4ug-aug/horisont-components
pnpm dlx shadcn@latest view 4ug-aug/horisont-components/<item>
pnpm dlx shadcn@latest add 4ug-aug/horisont-components/<item> --dry-run
Report the exact install command and any required package/theme assumptions. Do not create a registry server or generated registry output: GitHub is the distribution channel.