ワンクリックで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