Writes trilingual Astro MDX documentation pages for React hooks and regenerates the hook registry.
npx skills add https://github.com/childrentime/reactuse --skill hook-docs
Please help me install this Agent Skill. Skill: hook-docs Source: https://github.com/childrentime/reactuse/tree/main/.claude/skills/hook-docs Command: npx skills add https://github.com/childrentime/reactuse --skill hook-docs
Writing documentation for a new ReactUse hook requires creating three locale-specific MDX files (English, Simplified Chinese, Traditional Chinese) that follow a strict content schema, live-demo convention, and category-based routing, plus regenerating the hook registry — a repetitive, error-prone manual process.
packages/website-astro content folders, with proper frontmatter (title, description, sidebar_label).tsx live code block for an editable demo and preserves the %%API%% placeholder that the build replaces with the generated API table.scripts/generate-hook-registry.sh to rebuild scripts/hook-registry.json so blog and doc links resolve with the correct category and lowercase URL.useX hook, ask the assistant to document it — it creates all three locale files under the right category folder (browser, effect, element, state, integrations) and updates the registry.Ask the assistant to document the new useX hook following the ReactUse docs convention and regenerate the hook registry.
High-intent search queries and answers about installing and using this skill.
Create one MDX file per locale under packages/website-astro/src/content/docs, docs-zh-hans, and docs-zh-hant, inside a category folder such as browser or state. Include frontmatter with title and description, an inline tsx live demo, and the %%API%% placeholder, then run scripts/generate-hook-registry.sh.
Use a fenced code block with the tsx live language tag and write the demo component inline in the MDX file. The site renders it as an editable live example; it is not imported from the hook's source code.
No. The sidebar and routes are built automatically from file paths in the content folders. The folder you place the MDX file in determines the category, registry entry, and canonical lowercase URL.
Mirror the English structure and translate prose and frontmatter, but do not rely on pure character conversion. Terms differ, for example 状态 becomes 狀態, 默认 becomes 預設, and 组件 becomes 組件, while the code demo stays identical.
The hook registry was not regenerated after adding the docs. Run bash scripts/generate-hook-registry.sh, which walks the English docs folder and rewrites scripts/hook-registry.json with each hook's category and lowercase URL.
open-circleDocument Formisch source code with consistent JSDoc and inline comments.
DirtybitGamesConvert a Markdown source document into an HTML demo page and deploy it to the gh-pages branch.
forktruckaVerify Homebridge SoundTouch plugin release readiness with build, test, lint, and commit checks.
wredzioGenerate Storybook component documentation with autodocs, MDX, and JSDoc annotations.