@dotc/pi-chakra-v2-docs
Offline Chakra UI v2 documentation skills for Pi
Package details
Install @dotc/pi-chakra-v2-docs from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@dotc/pi-chakra-v2-docs- Package
@dotc/pi-chakra-v2-docs- Version
0.1.0- Published
- Oct 28, 2026
- Downloads
- 326/mo · 326/wk
- Author
- chrischow
- License
- MIT
- Types
- skill
- Size
- 1.9 MB
- Dependencies
- 0 dependencies · 2 peers
Pi manifest JSON
{
"skills": [
"./skills"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@dotc/pi-chakra-v2-docs
Offline Chakra UI v2 documentation for the Pi coding agent.
The chakra-v2-components, chakra-v2-hooks, and chakra-v2-styling skills guide agents to the relevant local documentation on demand—no network or explicit slash command needed. They use the same Chakra UI 2.10.10 snapshot. The package includes 231 MDX pages and the upstream MIT license.
Installation
pi install npm:@dotc/pi-chakra-v2-docsSkills
Ask Pi a Chakra UI v2 question. Pi sees each skill's name and description and reads its instructions only when the task calls for it; the full documentation corpus is not loaded into every prompt.
| Skill | Use for |
|---|---|
chakra-v2-components |
Component composition, examples, accessibility, theming |
chakra-v2-hooks |
Hooks, state, responsive behavior, custom controls |
chakra-v2-styling |
Style props, color mode, tokens, variants, theme overrides |
For example, ask “How do I show a loading state on a Chakra UI v2 Button?” or “How do I customize the v2 theme using this project's semantic tokens?” The agent reads the relevant local MDX page and can cite its pinned source. /skill:chakra-v2-components is available if you want to force a skill, but is not required.
The bundled pages are raw MDX: generated prop tables and imported Sandpack examples are not rendered. Some tutorial pages are placeholders; the skills prioritize usable guides and examples. See documentation provenance and limits.
Development
For checked-out source loading and package testing, see local development. For the pinned source, licensing, and refresh procedure, see provenance and updating the revision.