START HERE. Lists every Packkit generator (a language target — e.g. javascript, python, go) with its maturity and protocol capabilities. Pick the generator whose language matches what the user wants, then call list_presets and get_generator_schema for it before generating.

List the presets a generator offers (e.g. ts-lib, react-lib, node-service for javascript; py-lib, py-cli for python), each with a description and maturity. Experimental presets are hidden unless includeExperimental is true. Choose a preset that matches the shape the user wants instead of guessing.

Return a generator's full option schema — every option, its choices and defaults — as JSON. Read this before passing a config to generate_project so the options you set are valid for that generator.

Generate a project with a generator. By default it PREVIEWS (returns the file tree, stack summary and deployment contract without touching disk); pass write: true to scaffold the files under /. Existing files are never overwritten unless force is set. Call list_presets / get_generator_schema first.

Plan a re-scaffold of an existing project against the current templates: a three-way diff (baseline vs on-disk vs freshly generated) that separates template changes from the user's own edits, so nothing is clobbered. Reports the plan only — it writes nothing. Requires a generator that supports baseline-upgrade.

Compose two projects — a static frontend and an HTTP service backend, from ANY generators — into one fullstack repo (apps/web + apps/server) with a fullstack deployment contract and a docker-compose. Language-neutral: e.g. a "javascript" react-app frontend + a "python" py-service (or "go" go-service) backend. By default PREVIEWS; pass write: true to scaffold under /.