Obtain a Framework release
Download a matching source and package release with your Framework access, or verify artifacts you already have.
Confirm release access
Install the Smoothie CLI and the GitHub CLI, gh, first. Smoothie downloads private releases through your authenticated gh session; it has no separate login and stores no GitHub token. Your GitHub account needs access to SmoothieOrg/framework-standard; installing Smoothie does not grant it.
gh auth login
gh auth status
smoothie framework releasesgh auth status should show the account that received the repository invitation. framework releases lists the available Framework 0.1.0 release tags. Each tag identifies one exact release. These commands contact GitHub.
GitHub reports a private repository you cannot access as not found (404), not as denied. Check that gh is signed in to the invited account and that the invitation was accepted. If access still fails after accepting the invitation and signing in to the correct account, contact us.
Download into your project
Create the project directory first, then select an exact tag from framework releases:
mkdir my-product
cd my-product
smoothie framework acquire --version <exact-release-tag>
smoothie recipe list
smoothie recipe show smoothie-starterAcquisition verifies matching source and packages and records the selected release in .smoothie/framework/selected.json. Downloads are stored under .smoothie/framework/releases/. To use another existing directory, pass --project /path/to/my-product. This does not install dependencies or update application code.
Each cached release contains source/ and bundle/. Its Figma library is source/framework/design/whisk-ui-0.1.0.fig; import that file into Figma separately. Keep the selected.json file in Git. Only /.smoothie/framework/releases/ is added to .gitignore, so the downloaded cache stays out of your commits.
After cloning the project or deleting its cache, run smoothie framework acquire from the project directory. With no version, it restores the exact saved selection; it does not select the latest release. GitHub access is required to download missing files.
Next, create the application using the selected release.
Download to a separate folder
Use --output if you want to store the release outside your project or use an older CLI without project-local acquisition. Pass these source and bundle paths explicitly when creating an application or updating packages.
smoothie framework acquire --output ./release-downloadRun this in the directory that will contain your application, not inside it. The CLI picks the most recently published complete release it can read, including pre-releases, and records its exact tag and revisions. It creates release-download/ with source/ and bundle/, and checks that the two belong together before publishing the directory. It does not install packages or change any application.
To download a specific release, pass a tag from framework releases. The output directory must not exist yet; existing downloads are never overwritten.
smoothie framework acquire <exact-tag> --output ./release-pinnedIf your approved channel already supplied a matching source/ and bundle/, skip acquisition and use their paths in the following commands. Verification and application creation work offline.
Verify the release
smoothie framework verify ./release-download/bundle --source ./release-download/source
smoothie recipe list --from ./release-download/source
smoothie recipe show smoothie-starter --from ./release-download/sourceVerify checks that the source and packages are a matching pair, that every declared dependency is present, and that file and archive fingerprints match their records. Acquisition already ran the same check; run verify for artifacts from another channel, or before reusing a download you have stored. Recipe list and show read the source only.
If verification fails, keep the diagnostic and obtain a complete matching pair; do not edit receipts or rebuild missing archives. A passing integrity check confirms that files match their release records; it does not prove who published them or that the release is production-ready.
Store the release
Keep downloaded releases, with their notices and license, in private storage. Each application keeps its own copy of the package archives it uses, so already-created applications keep working without repository access. Keep the source/ directory too if you intend to modify Framework code. You need continued access only for new downloads; public third-party dependencies may still need their registries.
Next, choose a Starter or go straight to Create your first application.