delimit_generate_scaffold
Creates a new project tree with framework-conformant skeleton for Next.js, APIs, or libraries. Writes standard directory structure, package.json, lint config, and entry-point files in one call.
Instructions
Lay out a fresh project tree with framework-conformant skeleton.
When to use: at project zero, when starting a new Next.js app, API service, or library and you want the standard directory tree, package.json/pyproject.toml, lint config, and entry-point files all written in one call. Typical follow-up is delimit_init to set up governance scaffolding in the new project root. When NOT to use: to add files to an existing project (use delimit_generate_template for single-file scaffolds), to duplicate an existing project (use the shell), or to add a package to an existing project (use the project's own package manager directly).
Sibling contrast: delimit_generate_template writes a single
file into an existing project; this writes a NEW project tree.
Compared to create-next-app / cookiecutter, this routes the
scaffold through the Delimit bridge so the resulting project
can later be wired into delimit_init governance with no manual
cleanup.
Side effects: writes MANY new files and directories under a new
name/ root via backends.generate_bridge.scaffold. packages
is coerced from a comma string to a list via _coerce_list_arg
(malformed values short-circuit). No license gate. No ledger
write, no notification. The backend determines collision
behaviour if name/ already exists — call against a fresh
target.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_type | Yes | Project flavour, e.g. "nextjs", "api", "library". Required. | |
| name | Yes | Project name (becomes the root directory). Required. | |
| packages | No | Packages to include — either a comma string or list. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||