Getting Started

Nexus turns a Figma export, a text description, or an existing codebase into production-ready code — automatically.

Overview

Nexus is an enterprise dev toolkit with two modes of use:

Mode	How	Best for
`nexus` CLI	Terminal — install via one-liner	Local development, standalone use, sharing with friends
MCP server	Add to Claude Code, n8n, or Claude Desktop	AI agent workflows, automation pipelines

Both modes share the same pipeline:

Step	What happens
`ingest`	Reads your Figma ZIP, prompt, or codebase and builds a manifest
`remap`	Seeds the golden path boilerplate and queues components for the LLM
`transform`	Claude rewrites each component to production standards
`validate`	Static analysis — checks imports, missing files, bad patterns
`package`	Zips everything up, ready to unzip and run

The MCP server also exposes nexus_search and nexus_read — hybrid web search and doc-optimised reading tools for AI agents. These are MCP-only and not available in the CLI.

Prerequisites

Python 3.10+

Check if you have it: python3 --version

If not installed:

# macOS (via Homebrew)
$ brew install python

# or download from python.org

uv (recommended)

The installer prefers uv over pip for fast, isolated installs.

$ curl -LsSf https://astral.sh/uv/install.sh | sh

Claude Code CLI

Required for the LLM transform step. Needs an active Claude subscription (Pro or above).

# Install Claude Code
$ npm install -g @anthropic-ai/claude-code

# Authenticate
$ claude login

# Verify
$ claude --version

The nexus transform and nexus run commands call the claude CLI automatically with --dangerously-skip-permissions so the pipeline runs non-interactively. Make sure it's installed and authenticated before running the pipeline.

Installation

One-liner (recommended)

$ curl -fsSL https://nexus.coderstudio.co/install.sh | bash

pip / uv

$ pip install nexus-toolkit
# or
$ uv tool install nexus-toolkit

Quick Start

The fastest way to try Nexus — generate a full Next.js app from a text description:

$ nexus run prompt "A SaaS dashboard with sidebar, stats cards, and a data table" \
    -g nextjs-fullstack \
    -p my-dashboard

Nexus will ingest → remap → transform (via Claude) → validate → package — then output a ZIP ready to run.

$ unzip /tmp/nexus-my-dashboard/my-dashboard.zip
$ cd my-dashboard
$ pnpm install && pnpm dev

From a text prompt

No Figma? No problem. Describe what you want to build:

$ nexus run prompt "A landing page with hero, features grid, pricing, and footer" \
    --golden-path nextjs-static \
    --project-name my-landing \
    --output-dir ~/Desktop/

From a Figma ZIP

Export your project from Figma Make, then run:

$ nexus run zip ~/Downloads/figma-export.zip \
    --golden-path nextjs-fullstack \
    --project-name my-app \
    --output-dir ~/Desktop/

From an existing codebase

Migrate an existing React/Next.js project to a golden path convention:

$ nexus run codebase ~/Projects/old-react-app \
    --golden-path nextjs-fullstack \
    --project-name migrated-app \
    --output-dir ~/Desktop/

Golden Paths

A golden path is the target stack and conventions Nexus generates code for.

Golden Path	Stack
`nextjs-fullstack`	Next.js 16, React 19, Tailwind v4, tRPC v11, Prisma v7, NextAuth v5
`nextjs-static`	Next.js 16, React 19, Tailwind v4, static export
`t3-stack`	T3 conventions, tRPC + Prisma + NextAuth + Zustand, Tailwind v4
`vite-spa`	Vite 6, React 19, Tailwind v4, React Router v7, TanStack Query
`monorepo`	Turborepo, apps/web + apps/marketing, shared packages
`full-stack-rn`	Next.js web + Expo 54 mobile (NativeWind), shared packages
`full-stack-flutter`	Next.js web + Flutter 3.32 mobile (Riverpod + go_router)

All Commands

Command	Description
`nexus run prompt "<desc>"`	Full pipeline from a text description
`nexus run zip <file.zip>`	Full pipeline from a Figma Make ZIP
`nexus run codebase <dir>`	Full pipeline from an existing project
`nexus ingest prompt "<desc>"`	Ingest step only
`nexus ingest zip <file.zip>`	Ingest step only
`nexus ingest codebase <dir>`	Ingest step only
`nexus remap <project>`	Seed boilerplate + write transform queue
`nexus transform <project>`	LLM transform step (calls claude CLI)
`nexus validate <project>`	Validate generated files
`nexus package <project>`	Package output into ZIP
`nexus --help`	Show all commands and options

Options

Flag	Short	Default	Description
`--golden-path`	`-g`	required	Target stack (see golden paths table)
`--project-name`	`-p`	`my-app`	Output project slug
`--output-dir`	`-o`	`/tmp/`	Copy final ZIP here
`--model`	`-m`	`claude-sonnet-4-6`	Claude model for transform
`--claude-path`	—	auto-detect	Explicit path to claude CLI binary

You can also set CLAUDE_PATH as an environment variable instead of using --claude-path.

built by CoderStudio Labs · requires Claude Code