Skip to main content
Canonical terms used throughout the specification. Implementations SHOULD use the same terms in user-facing interfaces and documentation. Each entry links to the section that owns the full definition — the sentence here is a pointer, not a second specification.

Core concepts

Facet

A named, versioned collection of text assets defined by a manifest. What the author creates, what gets published, and what gets installed.

Project manifest

facets.json — the versioned file in a consuming project that declares which facets are installed and how it wants their assets materialized. Distinct from the facet manifest.

Facet manifest

facet.json — the source of truth for a facet’s identity and the text assets it contains.

Facet archive

The self-contained two-layer .facet artifact the author’s CLI builds and the registry stores. The transport form between publish and install.

Adapter

An AI coding tool abstraction (OpenCode, Claude Code, Codex). The layer between facet assets and the tool’s storage and configuration conventions.

Registry

The service that stores published facet archives, serves version metadata, and publishes both integrity hashes per version.

Asset types

Skill

A directory asset following the Agent Skills format; a SKILL.md plus optional companion files.

skills/<name>/SKILL.md

Agent

A single-file agent definition.

agents/<name>.md

Command

A user-invokable prompt.

commands/<name>.md

Identity & versioning

Integrity

Install pipeline

Authoring & publishing