DIXI Spec Kit documentation Español · Source on GitHub

Extensions and presets

Purpose

Show how to write an extension or a preset from an empty folder and install it. An extension adds operations of your own next to the kit's; a preset replaces the text of kit operations or templates with your team's version. Both are local folders that hold only data: DIXI copies text, it never runs anything from them and it uses no network.

Which one you need

You want toUseIt installs
Add an operation the kit does not haveAn extensionA new command named dixi-<id>-<operation>
Change how a kit operation or template readsA presetYour text in place of the kit's, in the same file

An extension needs a project created with an agent: with --agent none there are no command files to add, and dixi extension add is refused. A preset is accepted in any project; with --agent none there are no operation files to replace, so only its templates can apply.

Writing an extension

A folder with a manifest and one text per operation and language. The repository has this one in examples/extension-minimal:

extension-minimal/
├── extension.json
└── operations/
    ├── en/deploy-check.md
    └── es/deploy-check.md

extension.json:

{"id": "acme", "version": "1.0.0", "operations": ["deploy-check"]}

Install it from the project root:

dixi extension add ../examples/extension-minimal
dixi extension list

The operation is now available as dixi-acme-deploy-check: /dixi-acme-deploy-check in Claude Code, $dixi-acme-deploy-check in Codex and the dixi-acme-deploy-check skill in an Agent Skills compatible agent. The prefix means that an extension can never take the name of a kit operation. If a file with that name already exists, nothing is written.

To take it out:

dixi extension remove acme

It deletes only the files it installed and that you did not edit; edited ones are kept and listed.

Writing a preset

A folder with a manifest and the texts it replaces. The repository has this one in examples/preset-minimal, which gives the handoff the team's own headings:

preset-minimal/
├── preset.json
└── operations/
    ├── en/handoff.md
    └── es/handoff.md

preset.json:

{"id": "team", "version": "1.0.0", "priority": 50}

Install it from the project root:

dixi preset add ../examples/preset-minimal
dixi preset list

A file is replaced only when all of this is true:

  1. It is a kit file installed in this project.
  2. You have not edited it: it still has the kit's text, or the text of a preset with lower priority.
  3. There is no file for it in .dixi/overrides/. That folder holds the project's own versions and always wins over any preset.

Files that do not meet this are kept and listed, so a preset never overwrites your work. dixi upgrade does not overwrite a file that a preset replaced either.

To take it out:

dixi preset remove team

It puts the kit's text back in the files that still have the preset's text and keeps the ones you edited afterwards.

What neither of them does