Tooling

The plumekit CLI provides Plume's templating commands for checking, formatting, compiling, and editor integration.

For the full command list (including serve, dev, migrate, deploy, and generate) and the plumekit.toml reference, see The CLI. If you need to install the CLI first, see Start.

Commands

Check templates:

$plumekit check$plumekit check theme$plumekit check theme/home.plume

Compile templates to Embedded-Swift render functions (the compiling back-end):

$plumekit compile Views/                 # print generated Swift to stdout$plumekit compile Views/ -o Generated/   # write one .swift per template

See Compiling templates for the renderable subset and the build-time-only features it rejects.

Format templates:

$plumekit format theme$plumekit format --check theme

Formatting also canonicalises alias spellings to one Swift-spelled name per transform (for example upcase → uppercased, startsWith → hasPrefix, null → nil, and @slot(name: x) → @slot(x)). Both spellings keep parsing; the formatter rewrites to the canonical one. String-literal contents are left untouched.

Format stdin for editor integrations:

$cat template.plume | plumekit format --stdin

Run the language server:

$plumekit language-server

Print the version:

$plumekit version

Feedback

While writing templates, run check when you want diagnostics and format when you want the file rewritten:

$plumekit check theme$plumekit format theme

In CI, use format --check so the build fails when committed templates are not formatted:

$plumekit format --check theme

Checks

plumekit check validates:

• Template syntax.
• Component calls and component arguments.
• Named slot content placement.
• Inline Plume client scripts.
• Static style and script file references.
• Static asset and image references the host can see.

Editors

VS Code and Nova extensions are packaged with each PlumeKit release.

They provide:

• Syntax highlighting.
• Snippets.
• Diagnostics.
• Formatting.
• Directive and context completions.
• Document symbols.

The extensions use the plumekit command on PATH.

Troubleshooting

If diagnostics or formatting do not appear:

• Confirm plumekit language-server runs in a terminal.
• Run plumekit check path/to/file.plume to separate editor setup issues from template errors.
• Make sure the editor extension can see the plumekit command on PATH.