JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 521
  • Score
    100M100P100Q116148F
  • License MIT

Decantr CLI — scaffold, audit, and maintain Decantr projects from the terminal

Package Exports

  • @decantr/cli
  • @decantr/cli/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@decantr/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@decantr/cli

Support status: core-supported
Release channel: stable

Decantr’s main local operator surface for scaffolding, auditing, inspecting, and maintaining Decantr projects.

Install

npm install -D @decantr/cli

Or run it without installing:

npx @decantr/cli init --blueprint=agent-marketplace --yes

What It Does

  • scaffolds Decantr projects from blueprints, archetypes, or prompts
  • generates execution-pack context files for AI coding assistants
  • audits projects against Decantr contracts
  • searches the registry and showcase benchmark corpus
  • validates, refreshes, and maintains decantr.essence.json

Common Commands

decantr init --blueprint=agent-marketplace
decantr magic "AI-native analytics workspace"
decantr audit
decantr check
decantr registry summary --namespace @official --json
decantr showcase verification --json

Offline blueprint scaffolding expects a real local content source:

DECANTR_CONTENT_DIR=/path/to/decantr-content decantr init --blueprint=agent-marketplace --offline --yes

If a requested offline blueprint, archetype, or theme cannot be resolved from local cache/custom content or DECANTR_CONTENT_DIR, the CLI now stops explicitly instead of silently falling back to the default scaffold.

Generated Context

Scaffolded projects include compiled execution packs under .decantr/context/, including:

  • scaffold-pack.md / scaffold-pack.json
  • section-*-pack.md / section-*-pack.json
  • page-*-pack.md / page-*-pack.json
  • review-pack.md / review-pack.json
  • pack-manifest.json

Those files are the compact task contracts meant for AI assistants and downstream tooling.

Recommended read order for AI-assisted scaffolding:

  1. DECANTR.md for the design spec, CSS approach, and guard rules
  2. .decantr/context/scaffold-pack.md as the primary compiled shell, theme, feature, and route contract
  3. .decantr/context/scaffold.md as the broader app overview and topology guide
  4. matching section-*-pack.md and section-*.md files before section work
  5. matching page-*-pack.md files before route work

Treat the compiled execution packs as the source of truth. Use the narrative docs as secondary explanation, start with the shell and route structure first, and run decantr check plus decantr audit after implementation.

For cold-start harness or certification runs, use only the scaffolded workspace files as the contract. If local scaffold files disagree, stop and report the mismatch rather than relying on repo-global Decantr assumptions.

  • @decantr/essence-spec for schema and guard validation
  • @decantr/registry for registry contracts and API access
  • @decantr/verifier for audit and critique

Docs

License

MIT