Full-stack app

gen_fullstack · slug full-stack-app · icon 🧱 · outputs fullstack-app

A working React + TypeScript front end and Node + TypeScript API from a description. The team writes the spec, designs the data model, builds the API with validation, builds the UI with real loading, empty and error states, and documents how to run it.

Inputs

Field	Type	Notes
App name	string	required, 1-60 chars
What the app does	text	required, 30-3000 chars — three to eight sentences give the best result
Core entities	text	optional, one per line with a few fields each
Users and sign-in	pick	Single user, no sign-in · Simple name-based sign-in · Email and password accounts
Storage	pick	SQLite (better-sqlite3) · JSON file on disk · In-memory (demo only)
Interface style	pick	Clean dashboard · Warm and friendly · Dense and keyboard-first · Minimal mobile-first
Extras	text	optional, advanced — integrations, exports, charts, roles

Pipeline

Step	Role	Skills	Tier	Depends on
spec	product	llm.generate	cheap	—
data_model	architect	llm.generate	cheap	spec
api	engineer	code.scaffold_react_node, files.write, files.read, files.list	standard	spec, data_model
ui	engineer	files.write, files.read, files.list	standard	spec, data_model, api
readme	writer	files.write, files.read, files.list	cheap	api, ui

This is the only generator with two standard-tier engineering steps in sequence — api scaffolds the whole monorepo (via code.scaffold_react_node), then ui reads that same output and extends/refines the interface on top of it, so the second engineer is genuinely editing real generated files rather than starting from a blank page.

Example run

{
  "generatorId": "gen_fullstack",
  "inputs": {
    "appName": "Ledgerly",
    "description": "A shared expense tracker for a household. People add expenses with a category and who paid; the app shows who owes whom and a monthly breakdown.",
    "entities": "Expense: amount, category, paidBy, date, note\nMember: name, colour",
    "users": "Simple name-based sign-in"
  }
}