TOOLING · PUBLIC NPM PACKAGES

Give agents less context and better constraints

Coordiation turns project structure, literal utilities, component choices, and delivery rules into a compact machine-readable contract. An agent can start with the exact task context instead of repeatedly reading the complete repository and documentation.

The compact manifest for the Coordiation workspace is currently about 631 estimated tokens. This is a context-size estimate, not a guaranteed monetary saving; cost improvements must be measured with repeatable agent evaluations.

ONE DETERMINISTIC FLOW

Inspect, narrow, build, verify

Every phase produces data that another tool or agent can inspect.

01
Inspect: identify the framework, package manager, installed Coordiation packages, literal candidates, and actionable warnings.
02
Narrow: select a task pack such as pricing, form, or dashboard.
03
Build: reuse registered components and emit literal co-* classes under explicit contracts.
04
Verify: run the pack's accessibility, responsive, content, and build checks.

Install and inspect the current project

Terminal

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

npx @coordiation/cli inspect
npx @coordiation/cli inspect --write

The first command prints a short human summary. The second writes .coordiation/agent-manifest.json, which can be committed so humans, CI, and agents can track changes to the project contract.

Read the compact manifest first

.coordiation/agent-manifest.json

{
  "schemaVersion": "1.0",
  "kind": "coordiation-agent-manifest",
  "project": {
    "framework": "nextjs",
    "packageManager": "pnpm"
  },
  "coordiation": {
    "prefix": "co-",
    "browserRuntime": 0,
    "utilityCount": 147
  },
  "warnings": [],
  "contextBudget": {
    "mode": "compact",
    "estimatedTokens": 631
  }
}

Compact mode excludes file-by-file detail. Use inspect --full only for a task that genuinely needs the source file list and complete utility inventory.

Request only the task context

Terminal

npx @coordiation/cli context pricing --json

Context pack

{
  "topic": "pricing",
  "components": ["badge", "button", "card", "separator"],
  "utilityHints": [
    "co-grid",
    "md:co-grid-cols-3",
    "co-gap-5",
    "co-border",
    "co-ring-2"
  ],
  "checks": [
    "comparable features",
    "recommended label",
    "CTA contrast",
    "maximum three-line titles"
  ]
}

Available packs are page, navigation, form, dashboard, pricing, component, and theme. Each pack inherits the project's active contracts and known literal utilities.

Give the agent an executable brief

Agent instruction

1. Read .coordiation/agent-manifest.json.
2. Request the context pack for this task.
3. Reuse the listed Coordiation components.
4. Keep every co-* candidate literal.
5. Respect responsive, accessibility, icon, motion, and copyright rules.
6. Run the project build and report failed checks.

The manifest does not replace source inspection. It decides where inspection is necessary and prevents broad, repetitive context loading before the agent understands the task.

AGENT CONTRACTS

Make generated work easy to audit

These constraints stay stable across frameworks and task packs.

Use literal static class candidates; report dynamic interpolation instead of guessing its runtime values.
Prefer Coordiation components and icon packages before adding another UI dependency.
Preserve zero browser runtime for the CSS utility engine.
Respect responsive layouts, keyboard access, contrast, and reduced-motion preferences.
Use Coordiation copyright in every installable application theme.
Keep warnings visible in the manifest until their cause is resolved.

RELEASE STATUS

Available publicly from npm

The first usable agent-context slice is documented, tested, and versioned.

@coordiation/agent@0.1.0 contains the schema, project inspector, and task context packs.
@coordiation/cli@0.2.0 exposes inspect and context.
Both packages are public under the official @coordiation npm scope.
Framework-by-framework evaluations will continue measuring context size, task success, latency, and actual token usage.

Previous← IntelliSense & LSP Track releaseRelease Check →