Supported stack

Every project is a standard Next.js application. There is nothing proprietary in the generated code.

Versions

Conventions the model follows

• App Router with server components by default; client components only where interaction needs them.
• Route handlers under app/api/* for JSON endpoints; server actions are used where a form posts to the same page.
• Plain SQL through the pg pool in lib/db.ts, tables created if missing.
• Tailwind utility classes, no CSS-in-JS.
• Environment variables read from process.env, server-side unless prefixed NEXT_PUBLIC_.

Adding libraries

Ask for them. The model adds the dependency to package.json and uses it; the preview installs it on the next start. Anything on npm that runs on Node 22 without native compilation works out of the box. Native modules can work but may need alternatives — see Preview won't start.

Frameworks other than Next.js

Not today. Every project starts from the Next.js template; the model is told to stay within it. If you need something else, tell us.

Running the code yourself

The repository from GitHub sync runs anywhere Node 22 and Postgres are available: your laptop, Vercel, a VPS. Set DATABASE_URL and go.