Consumer skills
Install the Systhema skills that guide agents through design, components, Payload and maintenance.
On this page
Consumer skills describe how to build and maintain client projects. They are separate from monorepo contributor skills and separate from the documentation MCP connection.
Install for the projectLink to this section
systhema skills install --agent claude,codex,cursor --scope projectFor one shared cross-agent location:
systhema skills install --agent agents --scope projectThe agents target writes .agents/skills/. Named targets write .<agent>/skills/. User scope writes under the user's home directory.
Available consumer skillsLink to this section
| Skill | Use it for |
|---|---|
systhema | Entry point, project detection, package map, static introspection and version-matched docs |
systhema:building-sites | Scaffold-to-launch sequence, project boundaries, layouts and CMS composition |
systhema:cli | Registry setup, create, setup, sync, upgrade and command recovery |
systhema:configuring-projects | Package selection, Tailwind wiring and systhema.config options |
systhema:understanding-tokens | TOON references, token names, utility derivation and responsive sizing |
systhema:using-react-components | Component catalog, named variants, themes and composition rules |
systhema:creating-wireframes | Structure and hierarchy with default tokens before brand decisions |
systhema:frontend-development | Brand tone, typography, palette and composition when no Figma design exists |
systhema:from-figma-to-code | Exported DTCG tokens, frame mapping and Figma-to-component implementation |
systhema:design | Design CLI sessions, brand-book inputs, exports, imports and apply |
systhema:payload-as-backend | Content model, editor tiers, custom blocks, access, forms and Posts |
systhema:discovering-runtime-cookies | Cookies created by third-party scripts beyond the static scanner |
Start with systhema; read the relevant specialist before that kind of work. These instructions apply only when the project uses Systhema, except explicit new Systhema project or design creation.
Installation flagsLink to this section
| Flag | Purpose |
|---|---|
--scope project,user | One or several comma-separated scopes |
--agent claude,codex,cursor | One or several target agents |
--all-agents | Install for every supported target |
--name <name> | Install one named skill |
--mcp | Also connect the systhema-docs MCP for the selected targets |
--json | Report the installation as JSON |
systhema skills install --name systhema:design --agent codex --scope user
systhema skills list --scope project --agent claude,codex,cursor
systhema skills list --jsonWith no flags in an interactive terminal, the CLI asks for scope and agents. In non-interactive use, defaults are project scope when a project is detected, otherwise user scope, and the agents target.
Supported named targets include Claude Code, Codex, Cursor, Gemini, Copilot, VS Code, OpenCode, Roo, Windsurf, Cline, Continue and Goose. Installation does not prove a specific client version supports every skill discovery convention; confirm that your agent sees the installed skill.
Refresh installed skillsLink to this section
systhema skills refresh --dry-run
systhema skills refreshUpgrade refreshes already-installed skills unless you use --no-skills. Keep the bundled CLI version aligned with the project's maintenance needs and review skill changes with the upgrade.
Do not edit bundled copies to change the project's token facts. Express project guidance in the project's agent instructions, and regenerate references after design changes.
VerifyLink to this section
Run systhema skills list for the intended scope and agent. Ask the agent to read the entry skill and identify the installed core version. Connect systhema-docs separately for API lookup, or pass --mcp during installation. In interactive installation the CLI can offer this connection after the skill choices; it is not enabled silently.