Next.js project starter

Next.js project starter

Start a Next.js application with a working landing page, three languages, a health endpoint and production-server checks. Extend the supplied source into your own web application.

What you get

This is runnable application source: a landing page in English, Hungarian and German, language switching, a root redirect and a health endpoint. It contains no authentication, database, customer records or ready-made business workflow.

Create the project

Review the package in Orqestria and choose a new project folder. Installation writes the source, creates the first Git commit and assigns the included agents and skills. It does not install dependencies, run application scripts or start a server.

Prerequisites

• Orqestria installed on your computer.
• A writable location where Orqestria can create a new project folder.
• Node.js 20.9 or newer and npm with lockfile version 3 support.
• Network access for the explicit dependency-install command; the application itself runs locally.

Pinned dependencies

Next.js 16.4.3 · React 19.3.1

The included lockfile fixes the dependency versions used for this starter. Review dependency and license changes before upgrading; a successful starter check is not a security audit.

First local run

Open a terminal in the new project folder, review the commands below, then run them. They install dependencies and prepare only this local copy. Keep generated environment files and dependencies out of Git.

The development server listens only on your computer. The lockfile is used by npm ci; no global framework installation is needed.

npm ci
npm run dev

http://127.0.0.1:3000

http://127.0.0.1:3000/health

Verify the starter

Open the local application, switch between all three languages and check the health endpoint. Run the supplied checks before extending the source and again after dependency upgrades.

Build before running the tests. The test script starts its own production server on a free local port and stops it when finished.

npm run build
npm test

Production build

These commands verify a local production build. Publishing, authentication, access control, persistence, backups and monitoring still need a plan for your application.

npm run build
npm start

Make it your application

Choose one business workflow, its users and an observable success criterion first. Adapt the page and add only the data storage, permissions and integrations that workflow needs. Keep the existing checks as a starting point and add tests for the new behavior.

Included team

Orion, Quinn, Aria, and Atlas are assigned to this project with their existing skills. If an agent is already installed, Orqestria reuses that agent and preserves your edits. Model-based work requires your configured provider and the relevant skills to be usable.

Plan for later work

Budget for framework and dependency upgrades, hosting, operational ownership and migration as the application grows. Decide how data can be exported before adding storage. The starter does not include a deployment service or a maintenance commitment.

Choose a business foundation

For a business-specific starting point, compare the planning packs and repository collections before building a large custom system.

Browse business foundations

Framework documentation