INSTALLATION · FULLSTACK ALPHA

Install Coordiation Fullstack

HTML-first pages and backend APIs in one application, with guided delivery tools and no required React or Next.js runtime.

Published alpha · 0.1.0-alpha.1

Start with a disposable application. APIs may change, and this is not a production-certified replacement for Next.js. Existing Coordiation CSS integrations remain separate and supported.

View the npm package →

Create an empty project

Use Node.js 22.18.0 or newer. This is a standalone application, not the CSS integration for an existing React or Next.js project.

Terminal

mkdir my-coordiation-app
cd my-coordiation-app
npm init -y

Set up the application scripts

Replace the initial package.json with this manifest. The module setting enables JavaScript server files; the private flag protects your own application from accidental npm publication.

package.json

{
  "name": "my-coordiation-app",
  "version": "0.0.0",
  "private": true,
  "type": "module",
  "scripts": {
    "dev": "coordiation-app dev --host 127.0.0.1 --port 3100",
    "build": "coordiation-app build",
    "start": "coordiation-app start --host 127.0.0.1 --port 3100"
  }
}

Install the published alpha

These exact versions match this guide. The runtime installs its matching agent and CSS dependencies. The companion CLI provides the guided delivery modes. Keep the generated lockfile.

Terminal

npm install @coordiation/fullstack@0.1.0-alpha.1 @coordiation/cli@1.0.0-rc.2

Configure the site origin

The origin is used for canonical URLs and discovery metadata. Keep it aligned with the local port, and change it to your HTTPS domain before a public production build.

coordiation.config.json

{
  "origin": "http://127.0.0.1:3100",
  "metadata": {
    "title": "My first Coordiation app",
    "description": "An HTML-first page and a JSON API.",
    "lang": "en"
  }
}

Add a page and an API

Create the directories shown in these filenames. The .coord template becomes server-rendered HTML; the server file exports an HTTP method returning a standard Response. No React or Next.js installation is needed.

src/routes/page.coord

<main>
  <h1>Hello from Coordiation</h1>
  <p>This page is rendered on the server.</p>
  <a href="/api/health">Check the API</a>
</main>

src/routes/api/health/route.server.js

export function GET() {
  return Response.json({ ok: true });
}

Run the application

Open http://127.0.0.1:3100/ and /api/health. Expect the heading and a JSON response containing ok: true. Editing source rebuilds the server; reload the browser to see the update. Browser HMR is not included in this alpha.

Terminal

npm run dev

Build for production

Stop the dev process with Ctrl+C first, then build and start. This runs a production build locally; it does not deploy a remote server. If another project already uses port 3100, choose an unused port in both scripts and the configured origin.

Terminal

npm run build
npm start

Start with a requirements interview

This command reads the local mode context and returns questions. It does not call an AI provider or consume API credits. Save your answers before continuing; proposals and execution require review, and downstream modes depend on accepted upstream artifacts.

Terminal

node node_modules/@coordiation/cli/bin/coordiation.js mode cospecs --json

Eight modes, one connected workflow

cospecs — Clarify requirements and acceptance criteria for a PRD.
coux — Define information architecture, sitemap, screens and flows.
coui — Specify design tokens, UI components and responsive states.
coprototype — Describe and review runnable prototype scenarios.
codevelop — Review frontend/backend source, data contracts and checks.
coqa — Plan and run approved visual, logic and system checks.
codevops — Plan the environment, configuration, health checks and recovery.
corelease — Prepare source-bound release evidence and local artifact staging.

These are guided workflows, not a promise of autonomous application generation. Mode output, applied source and accepted QA are separate steps. Codevops planning can begin early; release depends on both QA and environment readiness.

Before you use it for real data

Authentication and SQLite modules are optional. Review access control, backups and recovery for your application; MFA and account recovery are not included.
Large sitemaps under load and Node 26 SQLite backup delays remain known limitations.
Release tooling stages and selects local artifacts. It does not automatically configure remote servers or roll back your database.
Public metadata, sitemap and OpenAPI support discovery, but do not guarantee search rankings or AI citations.
End-to-end token savings have not been measured. Local mode commands do not automatically invoke an AI assistant.

The installed package includes README.md, QUICKSTART.md, AUTH-DATABASE.md, SEO.md and RELEASE-NOTES.md. JavaScript works without TypeScript; semantic checks require the optional TypeScript 5.9.3 peer.

Back toAll installation guides ExploreAI agent context →