Creating a Preset

A Preset is a declarative Capability set without executable Extension code or target lifecycle state.

1. Create the directory

Use only needed paths: package.json, README.md, AGENTS.md, skills/, commands/, rules/, agents/, hooks/, mcp.json, and tools/.

2. Write the manifest

json

{
  "name": "jue-preset-team",
  "version": "1.0.0",
  "ai": {
    "presets": ["base"],
    "capabilities": {}
  }
}

See Preset Manifest Reference.

3. Add capabilities

Use <type>/<id>.md for a simple command, rule, agent, or hook, and <type>/<id>/ when directory structure is needed. Use one mode per <id>.

Place owned capabilities directly in their directories. Use ai.capabilities for shared or third-party content. Put target-private configuration under tools/<target>/config.json. Runtime code belongs in a separate Jue Extension.

When the same Skill must appear under more than one Agent project root, follow cross-client-root discovery:

Preferred: jue apply materializes each Adapter Artifact.
bash
```
npx jue apply --adapter claude --adapter cursor
```
Secondary: copy the directory into each in-repo root and keep them in sync.
text
```
.claude/skills/review/
.agents/skills/review/
```
Last choice: an in-repo symlink plus a checkout script that restores links. Windows Git defaults to core.symlinks=false and turns those links into regular files, so the Agent cannot find SKILL.md.
text
```
.claude/skills/review -> ../../.agents/skills/review
```

jue inspect --diagnostics reports broken, degraded, in-repo, and out-of-repo links.

4. Validate and package

jue validate checks the consuming project's ai.config.js (presets array, preset installation, extends paths) — not the Preset itself. During local development, wire the Preset into a consuming project with a local path dependency first (see Developing a Preset Locally), then run:

bash

npx jue validate

Before publishing, use npm pack to preview the package contents:

bash

npm pack --dry-run

Validation covers manifests, Canonical directories, dependency cycles, path traversal, credentials, and sensitive data. Pack emits an explicit inventory.

5. Consume

export default {
  presets: ["team"],
  targets: {
    codex: { artifact: "plugin" },
    openclaw: { artifact: "compatible-bundle" }
  }
};

The Adapter selects and produces the target Artifact without duplicating Presets.

Creating a Preset ​

1. Create the directory ​

2. Write the manifest ​

3. Add capabilities ​

4. Validate and package ​

5. Consume ​