Lattice Project Builder turns one product brief into your PROJECT_GUIDE.md, version-locked stack, AI guardrails, CI/CD workflows, and a custom setup command so Cursor, Claude Code, GitHub Copilot, or Codex can build against the same plan.
Turn one product brief into a project plan instead of re-explaining your app in every new AI chat.
Cursor, Claude Code, GitHub Copilot, and Codex get project-specific rules so they follow your architecture and stack.
Get the stack, CI/CD, verification, and the setup command in one package instead of a weekend of setup work.
Project Builder does not stop at a plan. It creates the files each AI editor actually reads, so your prompts, project structure, and code decisions stay aligned even if you switch tools mid-build.
Cursor gets both markdown and structured rules, so it stops improvising versions, folders, and architecture decisions.
Claude Code gets project instructions plus permission and hook scaffolding that match the plan you approved.
GitHub Copilot gets both repo-wide and path-aware instructions, so chat, agent mode, and inline coding stay aligned with the same project blueprint.
Codex gets a clear entrypoint and workflow rules, so it can work inside the same blueprint instead of starting cold.
From idea to a stack your AI can actually follow in under 5 minutes.
Fill out one form: what you're building, project type (web/mobile/API), key decisions (auth, database, UI style), and planning mode.
Takes 2-3 minutes. The form guides you through the important choices.
Lattice AI creates your PROJECT_GUIDE.md, stack plan, AI rules, CI/CD workflows, verification, and editor-specific guardrails.
Supported stack combinations also get scaffolded setup files. If a provider is not wired yet, Lattice keeps your requested stack visible and adds setup notes instead of silently swapping it.
Project Builder outputs a single npx command customized for your exact project configuration.
Copy this command. It applies the guide, guardrails, config, and any scaffolded files included for your stack.
Paste the command in your terminal. Lattice writes the repo plan, guardrails, and generated setup package automatically.
Supported combinations open with scaffolded app files. Unsupported providers still come with setup notes, so your assistant starts from the right blueprint.
One brief becomes the plan, the guardrails, and a provider-aware setup package your AI can use immediately.
A shared blueprint you and your AI can return to instead of starting every new chat from scratch.
GitHub Actions run verify on every push so AI-generated drift gets caught before it lands on main.
One paste applies the guide, rules, config, and generated files for supported stack combinations.
Supported combinations get scaffolded repo files. When a provider is not wired yet, Lattice keeps it explicit and adds support notes instead of faking the stack.
Cursor, Claude Code, GitHub Copilot, and Codex each get the files they actually read: .cursor rules, CLAUDE.md, .github Copilot instructions, AGENTS.md, and docs/rules/codex.md.
Lattice writes reusable prompts plus lint, typecheck, test, build, and verify defaults to keep human and AI changes honest from day one.
Purple = Project Builder-only features |Green = Includes Lattice Core
Supported web app combinations can start from a scaffold like this. If a provider needs manual setup, Project Builder still generates the guide, rules, CI, and support notes.
my-saas/ |-- .cursor/rules.md # AI guardrails for Cursor |-- .cursor/rules/ | |-- lattice-core.mdc # Structured Cursor rules |-- .claude/ | |-- settings.json # Claude Code permissions + hooks | |-- hooks/ # Hook templates for policy checks |-- .mcp.json # MCP server template config |-- .github/ | |-- copilot-instructions.md # Repo-wide GitHub Copilot instructions | |-- instructions/ | | |-- lattice-core.instructions.md # Path-aware Copilot instructions | |-- workflows/ci.yml # CI/CD pipeline | |-- PULL_REQUEST_TEMPLATE.md # PR template |-- .gitmessage # Commit message template |-- .lattice/ | |-- config.json # Lattice config | |-- prompts/ # 6 prompt templates | | |-- 01-feature.md | | |-- 02-bugfix.md | | |-- 03-refactor.md | | |-- 04-test.md | | |-- 05-polish.md | | |-- 06-security.md |-- AGENTS.md # Codex entrypoint + shared execution policy |-- docs/ | |-- rules/ | | |-- codex.md # Codex-specific workflow rules |-- CLAUDE.md # AI guardrails for Claude Code |-- PROJECT_GUIDE.md # Architecture and milestones | |-- app/ | |-- (auth)/ # PHASE 1: WORKING AUTH | | |-- layout.tsx | | |-- login/page.tsx # Login with email/password | | |-- signup/page.tsx # Signup with email confirmation | | |-- forgot-password/page.tsx # Password reset | |-- (dashboard)/ # Protected routes | | |-- layout.tsx # Dashboard layout with nav | | |-- dashboard/page.tsx # Dashboard home | |-- api/ # PHASE 4: API ROUTES | | |-- health/route.ts # Health check | | |-- user/route.ts # User profile CRUD | | |-- example/ | | | |-- route.ts # List/Create | | | |-- [id]/route.ts # Get/Update/Delete | |-- auth/ | | |-- callback/route.ts # OAuth callback | | |-- signout/route.ts # Sign out | |-- layout.tsx # Root layout | |-- page.tsx # Landing page | |-- globals.css # CSS with theme variables | |-- components/ | |-- ui/ # PHASE 3: UI COMPONENTS | | |-- button.tsx | | |-- input.tsx | | |-- card.tsx | | |-- spinner.tsx | | |-- index.ts | |-- lib/ | |-- supabase/ # PHASE 1: AUTH CLIENTS | | |-- client.ts # Browser client | | |-- server.ts # Server client | |-- utils.ts # cn() utility | |-- supabase/ | |-- migrations/ # PHASE 2: DATABASE | | |-- 001_initial_schema.sql # Profiles table + RLS | |-- types/ | |-- database.types.ts # Database types | |-- proxy.ts # Route protection |-- package.json # Full dependencies |-- tsconfig.json # TypeScript config |-- next.config.ts # Next.js config |-- eslint.config.mjs # ESLint flat config |-- jest.config.js # Jest config |-- jest.setup.js # Testing setup |-- next-env.d.ts # Next.js types |-- .env.example # Environment template |-- .env.local # Local env (placeholder) |-- .gitignore # Git ignore |-- README.md # Full documentation
You've felt it. The AI writes fast, but you spend days fixing what it built wrong.
Without clear specs, AI makes assumptions. Wrong assumptions compound into wasted days.
You build, realize it's wrong, tear it down, rebuild. The loop never ends.
AI suggests packages that don't exist, versions that conflict, patterns that are outdated.
Features get bolted on. The codebase becomes unmaintainable. You consider starting over.
Choose the depth that matches your project complexity.
Fast single-pass generation for straightforward projects. Get your custom command quickly.
Multi-model deliberation for complex projects. Multiple AI models debate and refine your setup.
If you want to add guardrails to an existing project, Lattice Core is what you need. One command adds AGENTS.md, Cursor rules, Claude settings, Copilot instructions, verification, and drift workflows. Free forever.
Get Lattice CoreBasic Planning uses a fast, single-pass AI engine, perfect for most projects. Pro Planning uses multiple AI models that debate and refine your setup, catching edge cases and producing deeper architecture analysis. Both are included at every paid tier.
Basic Planning takes 15-30 seconds. Pro Planning takes 60-90 seconds due to multi-model deliberation. After generation, you get your custom command instantly and can start coding in under 5 minutes total.
Each project gives you PROJECT_GUIDE.md, a compatible stack plan, CI/CD workflows, a custom setup command, verification commands, reusable prompt templates, and editor-specific rules for Cursor, Claude Code, GitHub Copilot, and Codex. Supported stack combinations also get scaffolded app files; unsupported pieces come with setup notes instead of silent substitutions.
Yes. Project Builder generates the files each tool actually reads: .cursor/rules.md and lattice-core.mdc for Cursor, CLAUDE.md plus .claude/settings.json for Claude Code, .github/copilot-instructions.md plus .github/instructions/lattice-core.instructions.md for GitHub Copilot, and AGENTS.md plus docs/rules/codex.md for Codex.
Project Builder is designed for new projects. It always generates the planning and guardrails pack for a new build, and supported stack combinations also get scaffolded app files. If you already have a repo, use Lattice Core (free) to add guardrails instead.
You can upgrade your plan at any time to get more projects. Unused projects don't roll over, but you can always upgrade mid-month to access higher quotas immediately.
Start with one-time PAYG builds (Basic or Pro), or choose a subscription if you plan to generate regularly.
Turn one product brief into a build-ready repo for Cursor, Claude Code, GitHub Copilot, or Codex and skip the 4-6 hour setup spiral.
PAYG starts at $9 per build. Subscriptions start at $29/month.