Skip to content
Browse documentation
cli

Recipe commands

Find a Recipe in your release and turn it into an editable application.

1. Find a Recipe

A Recipe gives you editable source to build on. Run from the project where you acquired the Framework. List the Recipes in the selected release, then inspect one:

bash
smoothie recipe list --format json
smoothie recipe show smoothie-starter --format json

These commands only read files; they do not run Recipe code. The release determines what is available. Check the Recipe's README for required services and hosting options.

2. Create an editable app

InputsPass the Recipe ID. The CLI uses the project's selected release and creates the app in the current directory; --project selects another directory.
Preview and applyPreview with --dry-run. Apply unchanged inputs with --expect-plan <planId>, not --run.
Source ownershipOne Recipe becomes your app's source. Existing projects are never overwritten.
Native installationAdd --install to run Bun with install scripts disabled. If installation fails, the created app remains.
Later updatesPackage updates leave your app code alone. Merge Recipe source changes yourself.

Use the project's selected release

After project-local acquisition, omit the source and bundle paths. Review the dry-run result before replacing data.planId in the apply command.

smoothie recipe list
smoothie recipe show smoothie-starter
smoothie recipe create smoothie-starter --dry-run --format json
smoothie recipe create smoothie-starter --expect-plan <data.planId>

Run from the project directory or pass --project /path/to/my-product. Creation allows .smoothie/, .git/ and .gitignore in the destination, but refuses other existing files. It preserves those settings and merges ignore rules. list and show verify the selected source and bundle before reading Recipes.

For a release stored elsewhere, add --from /path/to/release/source to list or show. For create, also pass a new destination after the Recipe ID and --bundle /path/to/release/bundle.

Next steps

The current Starter comparison lives in Choose a Starter; the complete creation procedure lives in Create your first application. Use Framework usage skills to delegate that workflow. Deployment, migrations, and model spending still need separate approval.