cli-tool/components/ as {type}/{category}/{name}. Fork the repository, add yours, and open a pull request.
Where each type goes
Names are kebab-case and match the file or folder name. Pick an existing category when one fits.
Rules
- Only commit your component. Never run
scripts/generate_components_json.pyor commitdocs/components.jsonor anything underdashboard/public/. They are regenerated after merge, and thegenerated-files-guardcheck fails a pull request that touches them. - No secrets. API keys go in placeholders (
<your-api-key>) or environment variables, never in the file. - Relative paths only. Use
.claude/hooks/,.claude/scripts/; never a home directory or absolute path. - One component, or one small related set, per pull request.
- A clear
descriptionthat says what it does and when to use it. Claude reads it to decide.
Test it before opening the PR
The CLI installs frommain, so it cannot install your branch yet. Copy the files where Claude Code reads them and try them in a real session: an agent into .claude/agents/, a skill folder into .claude/skills/, a hook into .claude/settings.local.json. Then run Claude Code’s validator on it:
What reviews your pull request
Hooks with scripts, mods and anything that runs code or sends data off the machine always get a maintainer’s manual review.
Sponsored placements on aitmpl.com never change review, ranking or search.