CoordiationCSS
⌘ K
Menu
Docs/Installation/Using npm

INSTALLATION · PUBLIC NPM PACKAGES

Install from npm

Every released Coordiation package is public under the @coordiation scope. Install only the compiler and integrations your project needs.

✓

Release candidate 1.0.0-rc.1 is available through the next tag. The latest tag remains on 0.1.0, or 0.2.0 for the CLI, until stable promotion is approved.

01

Start with the release candidate

For a Vite project, install the compiler and adapter from the coordinated next release train.

Terminal
npm install -D @coordiation/css@next @coordiation/vite@next vite

Continue with the complete configuration, CSS entry, scanning, and hot-update guide.

Read the RC notes →Open the Vite guide →
02

Choose additional packages

Packages are independently versioned so applications and AI agents can declare an exact, auditable toolchain.

@coordiation/css

Compiler, scanner, utility registry, preflight, and the coordiation-css binary.

@coordiation/vite

Recommended Vite integration with virtual CSS and hot updates.

@coordiation/postcss

PostCSS 8 adapter for existing CSS pipelines.

@coordiation/cli

Open-code installer for Coordiation components and themes.

@coordiation/agent

Compact project manifests and task-specific context packs for AI agents.

@coordiation/ui

Versioned snapshots of the official component registry.

@coordiation/icons

Solar Linear and Iconsax Line Oval icon components.

@coordiation/themes

Versioned application-theme registry and complete template payloads.

@coordiation/formatter

Canonical class sorting for source files and automation.

@coordiation/language-server

Completion, hover, diagnostics, and editor inspection.

@coordiation/upgrade

Safe migration plans and source codemods.

@coordiation/oxide

Optional native scanner with a portable JavaScript fallback.

03

Add icons, themes, or registry source

Install the matching RC registry snapshots when your build or AI workflow needs the source locally.

Terminal
npm install @coordiation/icons@next @coordiation/themes@next @coordiation/ui@next

The recommended open-code workflow uses the CLI to copy a selected component or theme into your repository.

Terminal
npx @coordiation/cli@next add component button
npx @coordiation/cli@next add theme editorial-advisor
04

Build without Vite

The compiler package includes a standalone binary. Use the PostCSS adapter when an existing pipeline already owns CSS processing.

Terminal
npx coordiation-css \
  --input src/coordiation.css \
  --output dist/coordiation.css \
  --content src
Open the CLI guide →Open the PostCSS guide →
05

Prepare compact context for AI agents

Install the public agent package and CLI to create a small, deterministic manifest instead of sending the entire repository to an agent.

Terminal
npm install -D @coordiation/agent@next @coordiation/cli@next

npx @coordiation/cli@next inspect --write
npx @coordiation/cli@next context pricing
Open the AI agent context guide →

AI INSTALLATION CONTRACT

Keep dependencies traceable

Agents should select packages from the published catalog instead of inventing package names or copying registry payloads manually.

  • Use the exact @coordiation/* package names listed above.
  • Read /llms.txt and /api/capabilities before generating framework code.
  • Use literal co-* classes so scanning and diagnostics remain reliable.
  • Prefer the CLI for open-code components and themes.
  • Pin versions in CI and automated agent environments.
Previous← InstallationNextUsing Vite →