원클릭으로 Manus에서 모든 스킬 실행

시작하기

create-hook

스타5

포크0

업데이트2026년 3월 23일 23:39

Scaffold a new UI hook with the correct naming, tests, and docblocks

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

olavoasantos

olavoasantos/cliui

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Create Hook

When creating a new UI hook in this project, follow these conventions exactly.

File Placement

src/ui-hooks/
├── useMyHook.ts
└── specs/
    └── useMyHook.unit.tsx

Conventions

Naming: camelCase with use prefix. Filename matches the hook name.
Export: Single named export per file. No default exports.
Docblocks: The hook and its parameters/return type must have JSDoc/TSDoc comments.
Tests: Every hook must have a corresponding *.unit.tsx file.

Checklist

Create src/ui-hooks/use<HookName>.ts with a single named export
Add JSDoc/TSDoc to the hook function
Create src/ui-hooks/specs/use<HookName>.unit.tsx with unit tests
Export from src/index.ts if the hook is part of the public API
Run pnpm run check to verify

이 저장소의 다른 Skills

같은 저장소

create-changeset

olavoasantos/cliui

Create a changeset entry describing changes to workspace packages

2026-04-175

create-component

olavoasantos/cliui

Scaffold a new UI component with the correct folder structure, styles, tests, and docblocks

2026-03-265

create-class

olavoasantos/cliui

Scaffold a new class with the correct file structure, naming, tests, and docblocks

2026-03-255

create-guard

olavoasantos/cliui

Scaffold a new runtime type guard with the correct naming and docblocks

2026-03-255

create-utility

olavoasantos/cliui

Scaffold a new utility function with the correct naming, tests, and docblocks

2026-03-255

write-tests

olavoasantos/cliui

Write tests following this project's testing conventions, file patterns, and placement rules

2026-03-255

name	create-hook
description	Scaffold a new UI hook with the correct naming, tests, and docblocks
user-invocable	false

Create Hook

When creating a new UI hook in this project, follow these conventions exactly.

File Placement

src/ui-hooks/
├── useMyHook.ts
└── specs/
    └── useMyHook.unit.tsx

Conventions

Naming: camelCase with use prefix. Filename matches the hook name.
Export: Single named export per file. No default exports.
Docblocks: The hook and its parameters/return type must have JSDoc/TSDoc comments.
Tests: Every hook must have a corresponding *.unit.tsx file.

Checklist

Create src/ui-hooks/use<HookName>.ts with a single named export
Add JSDoc/TSDoc to the hook function
Create src/ui-hooks/specs/use<HookName>.unit.tsx with unit tests
Export from src/index.ts if the hook is part of the public API
Run pnpm run check to verify