Stack Selection

Purpose

Choose the simplest stack that can ship the requested product inside Subterranean.

Default recommendation

Use Vite React TypeScript for the frontend, Subterranean api/*.ts routes for local backend behavior, and Subterranean Data tables plus generated Functions for Postgres-backed CRUD.

Decision rules

• Use Vite React TypeScript for most interactive web apps and prototypes.
• Use Data tables first when the product needs persisted structured records.
• Use generated Functions for standard CRUD and table operations.
• Add custom api/*.ts routes when the product needs orchestration, validation, aggregation, external requests, or domain-specific backend behavior.
• Do not scaffold a literal Express server by default. Only propose a real Express app when the user explicitly needs a standalone Node server outside the current Vite/API route flow.

Stack explanation

When making a stack call, state:

• the chosen frontend scaffold,
• the data model,
• the backend integration path,
• why this is the smallest reliable option,
• what would justify changing it later.

Avoid

• Choosing a framework because it is popular rather than needed.
• Adding servers, queues, auth layers, or ORMs before the product needs them.
• Hiding uncertainty about platform limits.