Skip to Content
DocumentationSkills

unitone-css skills

Shared skills for unitone-css.

These skills are written as portable Markdown-first instructions so they can be distributed to multiple agent environments with minimal changes.

Included skills

  • unitone-css-router
  • unitone-css-add-layout-primitive
  • unitone-css-add-behavior
  • unitone-css-doc-sync
  • unitone-css-coding-assistant
  • unitone-css-vision-to-code

Source of truth

The source of truth is this packages/skills/ directory.

If you want to install the same skills into Codex, Claude Code, Cursor, or VS Code / Copilot, use the scripts under packages/skills/bin/.

Quick start

Install into your repository

node packages/skills/bin/skillpack-install.mjs --dest=../your-project --targets=codex,vscode,claude,cursor

This copies skills into:

  • .codex/skills/ for Codex
  • .github/skills/ for VS Code / GitHub Copilot
  • .claude/skills/ for Claude Code
  • .cursor/skills/ for Cursor

Install globally for Claude Code

node packages/skills/bin/skillpack-install.mjs --targets=claude-global

This installs skills to ~/.claude/skills/.

Install globally for Cursor

node packages/skills/bin/skillpack-install.mjs --targets=cursor-global

This installs skills to ~/.cursor/skills/.

Available options

skillpack-install.mjs

# Preview installation without writing files
node packages/skills/bin/skillpack-install.mjs --dest=../your-project --targets=codex,claude --dry-run
 
# Install selected skills and their required dependencies
node packages/skills/bin/skillpack-install.mjs --dest=../your-project --targets=codex,claude --skills=unitone-css-router
 
# Merge into an existing skills directory instead of replacing target skill folders
node packages/skills/bin/skillpack-install.mjs --dest=../your-project --targets=codex,claude --mode=merge

Supported install targets:

  • codex
  • vscode
  • claude
  • claude-global
  • cursor
  • cursor-global

Supported install modes:

  • replace
  • merge

Invalid modes, unknown skill names, and empty --skills or --targets lists fail before any destination files are changed. Omitting --skills installs all skills.

The source directory is resolved relative to the installer, so the script can be invoked by its absolute path from any working directory. Relative --dest paths are resolved from the current working directory.

Skill dependencies

The installer includes required skills automatically, using dependencies.json:

  • unitone-css-coding-assistant can be installed on its own and contains the shared primitive-selection and token-approximation references.
  • unitone-css-vision-to-code includes unitone-css-coding-assistant for those references and implementation rules.
  • unitone-css-add-layout-primitive includes unitone-css-add-behavior and unitone-css-doc-sync for behavior and documentation changes.
  • unitone-css-add-behavior includes unitone-css-doc-sync.
  • unitone-css-router includes all skills it can route to.
  • unitone-css-doc-sync can be installed on its own.

--dry-run lists the complete selection, including dependencies. The chosen replace or merge mode applies to every skill in that selection.

Manual installation

If you do not want to use the scripts, copy any skill directory from packages/skills/ into the agent-specific skills directory you use.

Also copy its dependencies listed above into the same parent directory, including each skill’s references/ files. Preserve the skill directory names so relative links resolve correctly.

Examples:

  • Codex: .codex/skills/
  • Claude Code: .claude/skills/
  • Cursor: .cursor/skills/
  • VS Code / GitHub Copilot: .github/skills/

How it works

Each skill directory contains:

packages/skills/unitone-css-add-layout-primitive/
├── SKILL.md

The install script copies skills directly from packages/skills/ into the target repository or global directory.

Run node --test tests/skillpack-install.test.mjs from the repository root to verify selection, dependencies, argument validation, and installation modes in temporary directories.

Design rules

  • Keep SKILL.md procedural and short.
  • Push deep reference material into references/ only when needed.
  • Prefer deterministic helpers or MCP tools over free-form inference.
  • Ignore dist.

For screenshot-to-code skills, local references/ files are recommended when they help make primitive selection or token approximation more deterministic.

Last updated on
MCP