Skip to main content
Workflow packs install read-only workflows and UIs under .smithers/packs/<name>: visible to workflow list, runnable by unqualified id or <pack>:<workflow>.

​
Eject a workflow

Copy a pack workflow into the local .smithers/ tree to edit it:
Copies the workflow plus its relative UI, prompt, library, stylesheet, and other imported assets; refuses if any destination exists. The local copy shadows the pack copy: workflow run kanban runs the ejected workflow, workflow run kanban-suite:kanban still runs the pack version.

​
Update packs

Pack updates are separate from the installation update command:
First form refreshes one locked pack; bare form refreshes all. Updates replace pack contents only; ejected files in local .smithers/workflows, .smithers/ui, .smithers/prompts, .smithers/lib are untouched. Rest of the lifecycle:

​
Share a pack

Any initialized .smithers/ directory can publish as a pack: set repository in smithers.toon, then preview the awesome-smithers entry:
The normal command uses authenticated gh to fork the registry, update its Packs section, push a branch, and open a pull request (--repo owner/registry overrides the registry repo); the seeded share-pack workflow handles validation and repo prep first.