Skip to content
SyntaxisSyntaxisSyntaxis

scaffold

Creates the application for Next.js, React with Vite, SvelteKit, ASP.NET Core, Flutter, Expo, Ionic, Electron, or Tauri — then records the real commands it produced.

Invocation

Section titled “Invocation”
/scaffold             ask which stack
/scaffold nextjs      name the stack
/scaffold dotnet      add a second stack to an existing project

From an empty directory you can also scaffold and install in one step:

Terminal window
npx create-syntaxis@latest --scaffold

The problem it solves

Section titled “The problem it solves”

Framework generators refuse to run in a directory that already has files, and a Syntaxis project always has files. /scaffold scaffolds into a temporary directory and merges the result, so a stack can be added after installation.

Stacks with genuine in-place support — flutter create ., dotnet new — use it directly.

Merge rules

Section titled “Merge rules”
  • Syntaxis-managed paths are never overwritten.
  • The generator’s .git/ is never copied.
  • Installed dependency trees are never copied; dependencies install at the destination.
  • .gitignore is merged, not replaced.
  • Your README.md and LICENSE are kept.
  • Any other collision stops the merge and asks you.

What it guarantees

Section titled “What it guarantees”
  • It runs the stack’s official generator, never a hand-written skeleton.
  • Nothing runs until you approve the exact command.
  • It never installs a system toolchain or switches your package manager.
  • It proves the scaffold by installing, building, and starting the app. A generator exiting zero is not proof.
  • One application per invocation.

See Scaffolding a Stack.