Workflows
Install agent skills
Give your coding agent package-specific guidance for using @hulla/* in your application.
On this page
Install the skills for the packages your application uses. Each skill gives a coding agent guidance on architecture, public APIs, and common mistakes, with links to focused documentation.
The skills live in hulladev/skills, a small repository containing instructions and references. Installing them does not require downloading the package source repositories.
Run the following from your application directory. The external skills CLI lets you choose skills and a supported agent, including Codex, Claude Code, or Cursor:
bunx --bun skills add hulladev/skillsnpx skills add hulladev/skillspnpm dlx skills add hulladev/skillsyarn dlx skills add hulladev/skillsThis command belongs to the skills CLI; it is separate from the hulla CLI. Follow the installer’s runtime requirements and review the selected destination before installing. Project installation makes the guidance available to agents working in that application.
For example, select only the API skill for Codex:
bunx --bun skills add hulladev/skills --skill api -a codexnpx skills add hulladev/skills --skill api -a codexpnpm dlx skills add hulladev/skills --skill api -a codexyarn dlx skills add hulladev/skills --skill api -a codexAfter installation, ask the agent to use the selected skill for a relevant task, such as adding a route while keeping its server implementation out of the browser bundle. Discovery and activation depend on the agent and its configured skill locations; installing an npm package alone does not activate this guidance.
Skill IDs use the package’s unscoped name: api for @hulla/api, ui for @hulla/ui, and so on. The Agent Skills format does not allow @ or / in IDs.
| Package | Skill | Guidance |
|---|---|---|
@hulla/api | api | Shared contracts, server implementations, clients, and adapters. |
@hulla/ui | ui | Installed source components, composition, themes, and native interactions. |
@hulla/db and framework bindings | db | Schemas, transactions, restricted handlers, live clients, and authentication. |
@hulla/style and @hulla/style-native | style | Shared helpers, variant inference, merging, and native style objects. |
@hulla/control | control | Result branches, exception boundaries, and asynchronous payloads. |
@hulla/args | args | Argument declarations, omission, validation, and command execution. |
@hulla/gittar | gittar | Snapshot downloads, subpath copying, cache isolation, and freshness. |
Use ui when composing application components, rather than when developing a registry generator. Add the relevant parent skill for an adapter or framework binding; you do not need a separate skill for every integration.
Each skill records the package version and source revision it was reviewed against. Compare that compatibility information with your application’s installed version before updating. Skills describe intended usage; they do not replace installed declarations, component source, runtime validation, or application tests.
If you installed an earlier hulla--prefixed skill, install its short-name replacement and review the old entry before removing it with your installer. Older tagged snapshots retain their original names.
For a reproducible setup, install from a reviewed tag or commit using the source formats described in the skills repository. Retain the chosen skills and installer lockfile with your project, and review changes before updating them.
You can also copy an entire skill directory, including its references and license, into your agent’s supported project location. For Codex, that is .agents/skills/<skill-name>/. Copying only SKILL.md can omit guidance loaded for native components, database handlers, or migrations.
Agents that retrieve documentation can start with llms.txt and follow the relevant Markdown pages. Use skills for the workflow and architecture guidance, then consult the matching package documentation for the specific API you are changing.