Skip to main content

​
Usage

Prints agent-oriented workflow guidance: how an autonomous agent should author and use facets. For per-flag help, use facet <command> --help. The default topic is overview, which opens with an index generated from the CLI’s own topic list, so it always matches the topics the CLI serves.
Requires v0.24.0 or newer. If this reports “Unknown command”, run facet self-update.

​
Examples

​
Exit codes

​
Output

​
default
What facets are, the three artifact files, the two workflows, a command index, and a generated index of every topic.
​
topic
The facet.json structure, including top-level and per-skill supplementary files, plus the JSON Schema generated from the schema definition.
​
topic
Writing facets: scaffold, modify, verify, including README and supplementary-file authoring, MCP server declarations, and per-text-asset adapter configuration.
​
topic
Project management: adding, updating, and removing facets, the shape of facets.json, resolving a name collision without a TTY, approving or omitting MCP servers without a TTY, and installing adapter tooling.

​
Details

​
The manifest schema is generated

The manifest topic appends the facet.json JSON Schema generated at runtime, so it always matches the CLI you are running. Rules the schema cannot express, such as needing at least one asset and keeping skill and command names distinct, are described alongside it. Run facet build --verify to check a real facet.

​
See also