Run this from an app that has already been initialized with shadcn.
Build with AI
Give your tool the rules before it builds. The AI kit brings 0nlyType's intent, design system and component contracts into your project.
Install the kit
npx shadcn@latest add https://If you already have an AGENTS.md, keep it. The installer asks before replacing a file; it does not merge Markdown. Use the prompt below to add a pointer to docs/0nlytype/AGENTS.md.
Files and tools
Short instructions are discovered by your tool. The complete references stay available for the task at hand. Ask the tool to confirm what it loaded.
| File | Read by | What it is for |
|---|---|---|
AGENTS.md | Codex and compatible agents | Short rules, reference pointers and a completion checklist. |
docs/0nlytype/AGENTS.md | Any tool, when asked | A namespaced copy to reference from your existing project instructions. |
docs/0nlytype/INTENT.mddocs/0nlytype/DESIGN-core.md | Any tool, when asked | The intent, principles, conventions, tokens and general motion rules. |
docs/0nlytype/DESIGN.md | Any tool, as a reference | The complete design system. Read the relevant sections as needed. |
docs/0nlytype/components/<item>.md | Any tool, for the task at hand | The component contract, motion and design reference. |
.cursor/rules/0nlytype.mdc | Cursor Agent | Short rules, always applied. |
.claude/rules/0nlytype.md | Claude Code | A short entry point with references to read as needed. |
.github/instructions/0nlytype.instructions.md | GitHub Copilot | Rules for TSX and CSS files. Support varies by feature. |
.devin/rules/0nlytype.md | Windsurf / Cascade | Always-on rules. Older versions use .windsurf/rules/. |
.agents/skills/0nlytype-component/SKILL.md.claude/skills/0nlytype-component/SKILL.md | Codex / Claude Code | A workflow: inspect, choose a precedent, implement, verify. |
docs/0nlytype/manifest.json | You and your tool | The kit version and hashes of its sources and contents. |
Prompts
Build a component
Read docs
/0nlytype /AGENTS.md, docs /0nlytype /INTENT.md, docs /0nlytype /DESIGN-core.md and the relevant component contracts. Confirm which paths you loaded. Build [component] for [behavior]. Use an installed 0nlyType component as precedent. Run the completion checklist and report evidence.
Keep your project instructions
Preserve my existing project instructions. Add a short 0nlyType section pointing to docs
/0nlytype /AGENTS.md.
Refresh the kit
Refresh the 0nlyType AI kit. Preserve my existing project instructions and local changes. Compare the installed docs
/0nlytype /manifest.json with the latest kit, review the differences and update the generated references. Confirm which paths you loaded and report what changed.
Keep it current
The installed files are copies. To refresh them, run the install command again and review the changes before replacing files. Keep your project instructions and local edits.
docs/0nlytype/manifest.json records the kit version and source hashes. Ask your tool to compare it and reload the updated references.
Downloads
For tools that read URLs or attachments, download the references or give the tool their links.
- AGENTS.md: the short rules and completion checklist.
- INTENT.md: what 0nlyType is for, and what it refuses.
- DESIGN-core.md: principles, conventions, tokens and motion.
- DESIGN.md: the complete design reference.
- llms.txt: a small index for browsing assistants.
A file being available does not mean a tool has read it. Ask it to confirm the loaded paths before it starts.