Preset Author Commands

The CLI exposes create-preset, validate, and format for Preset authors:

jue create-preset <name>
jue validate
jue format

Command	Behavior
create-preset <name>	Scaffolds an ordinary npm package (jue-preset-<name>) and minimal Canonical directories
validate	Validates the current project config: presets array, preset installation, and extends paths
format	Migrates AI tool configs to the .ai directory

Query Preset inventories with jue list presets. Existing package managers own installation, upgrades, version comparison, publishing, and removal.

Planned author namespace

The target shape of these commands is a jue preset author namespace (planned, not yet implemented; not to be treated as available):

jue preset create <name> [--dir <path>] [--extends <preset>...]
jue preset validate <path-or-package>
jue preset pack <path> [--out <dir>]

• create: scaffolds an ordinary npm package and minimal Canonical directories.
• validate: checks package.json#ai, paths, references, sensitive data, and packability. Unlike today's jue validate (which only reads the consuming project's ai.config.js), the target is to self-check <path-or-package> directly, without first wiring it into a consuming project — motivating scenarios in Developing a Preset Locally §5.
• pack: follows npm pack semantics without running package scripts and emits content hashes.