Starter

Define the smallest maintainable starter that proves the stack can become a real app. Keep this file as Markdown by default. Create a real starter/ directory only when a concrete pack has generated files worth preserving.

Starter Stance

Project Shape

Use a text block for the expected layout. Keep it small.

[app-name]/
├── [source-root]/
├── [test-root]/
├── [config-file]
├── [package-or-build-file]
└── README.md

Scaffold Command

Record the exact command only after verifying it against current docs.

[create command goes here]

If the command cannot be verified, write Unknown and explain which source must be checked.

Required Prerequisites

Keep In V1

The starter should include only the parts that prove the stack works:

• App shell or entry point.
• One route, screen, view, or command.
• One test that exercises the app entry point.
• One build or package command.
• Minimal configuration required by the stack.

Exclude From V1

Do not include these until a reference app proves they are needed:

• Authentication.
• Payment flows.
• Complex design systems.
• Multi-environment deployment automation.
• Unreviewed third-party UI kits or starter templates.
• Store submission automation.
• Production secrets or credentials.

Starter Validation

The starter is valid only when these commands have concrete entries in commands.md and pass their required gates in quality-gates.md: