Scaffold Studio — Nexis documentation

Generate locally in the browser

Scaffold Studio creates the archive in the current browser. A project name and generated source files are not submitted to an archive service. The downloaded project remains an ordinary Nexis source tree that you own and can inspect before installation.

Pick the narrowest starting boundary

Minimal contains a static HTML-first route. Interactive adds a focused resumable counter boundary. Secure Node adds an explicit Node configuration with reviewable security headers. TypeScript and JavaScript output use matching route extensions; Tailwind setup is optional.

Inspect and run before extending

Every archive includes package.json, the Nexis HTML shell, public styles, a route, a README, and a GitHub Packages scope file. Secure Node adds nexis.config; Tailwind adds the Vite configuration, source CSS, and editor recommendations. Inspect package versions and never place a registry token in the archive or repository.

ExampleTypeScript

unzip my-nexis-app.zip
cd my-nexis-app
pnpm install
pnpm dev

pnpm typecheck
pnpm check
pnpm build

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

Generate and inspect a local starter

Shell

unzip my-nexis-app.zip
cd my-nexis-app
pnpm install
pnpm typecheck
pnpm check
pnpm build

OUTPUT: The downloaded project becomes an ordinary inspectable Nexis source tree.
BOUNDARY: The browser archive does not carry registry credentials; configure access in your own environment.
PROVE IT: Confirm the selected preset files and current package set in package.json.

VERIFICATION

Prove the contract.

Open package.json and confirm the selected preset files are present, then run the verification commands. The published v1.3.3 Starter pins the coordinated v1.3.3 package set, including Router and SEO.