Skip to content
Browse documentation
skills

Framework usage

Guide an agent through release selection, Starter adoption, package updates, and customer source customization.

Use the Framework through its owning tools

This concern covers acquiring a release, adopting a Starter, selecting packages, and customizing Framework source. Skills guide those workflows; the CLI controls explicit operations, native tools own installation/builds, and the application owns its product code. Read the Skills list for the current inventory, not a promise that every future lifecycle task already has a dedicated skill.

Give the agent the actual project or new destination, the source/bundle pair or authorized release-selection rule, and the allowed effects. Missing release access is a blocked prerequisite, not permission to substitute historical public packages or another customer's copy.

Setup and adoption

smoothie-setup guides one new independent application. Before an application exists, register the acquired source's complete skill through the host's mechanism or ask the agent to read its SKILL.md. After creation, use project-local installation. Starter selection and command steps stay in Choose a Starter and Create your first application.

text
Use smoothie-setup from the acquired release.
Create smoothie-starter at /absolute/my-product using
/absolute/release/source and /absolute/release/bundle.
Review and apply the creation plan without overwriting an existing directory.
Dependency downloads and local native/browser checks are authorized.
Install the retained skills for Codex after creation.
Do not deploy, provision services, or make live model calls.
Report the exact release, created files, checks, and next native dev command.

Replace the paths and Starter with the actual inputs. Interactive Agent's live model calls need spending authority; Durable Worker's database, Redis, and migrations need an explicitly authorized environment. Do not silently choose another Starter or migrate an unknown shared database to make setup finish.

Updates and customization

smoothie-framework-update guides package switching, restoration, and customer-built bundles without overlaying application source. Keep command steps and recovery limits in Updates and rollback, and custom build preparation in Customize Framework source. Recipe-derived code needs a reviewed merge, not a package update.

text
Use smoothie-framework-update in /absolute/my-product.
Verify the target pair at /absolute/release-b/source and /absolute/release-b/bundle.
Review and apply the package-selection plan; preserve unrelated dependencies and app source.
Native dependency downloads and affected local checks are authorized.
Retain the previous archives and review the native lockfile diff.
Do not replace installed skills, run migrations, or deploy.
Report before/after identities, package and lockfile changes, and restoration inputs.

Inspect an interrupted transaction's journal before choosing resume or rollback. Keep customer builds separately identified; do not edit the original release inventory to make them appear official. Package selection leaves installed instructions unchanged: follow skill version alignment separately.

Review lifecycle evidence

Expect the exact release/custom identity, application or changed dependency paths, native lockfile changes, actual check results, and retained restoration inputs. Created files or a successful install do not prove a running application. Service/browser skips and missing prerequisites must remain visible. Continue with Development for product behavior changes.