Next.js is a TypeScript workable choice for mobile app. GreatCTO auto-detects both — adds the mobile-app archetype overlay, wires mobile-app-specific gates, and runs 83 specialist agents around your existing Next.js workflow.
GreatCTO reads your package.json and detects nextjs + mobile-app archetype from signals: imports, file structure, env vars, README hints.
Attaches the mobile-app archetype overlay: IAP receipt validation, App Store / Play Store policy, push token security, privacy nutrition labels. Override if your specifics differ; the defaults are sensible for Next.js-style projects.
qa-engineer runs tsc --strict / eslint / vitest --coverage; security-officer checks for prototype pollution + XSS sinks; performance-engineer reviews bundle size + cold-start times.
Bugs you've hit before in other Next.js projects (connection-pool exhaustion, ORM N+1 queries, retry storms) — the agent's Step 0 includes the prior detection order. MTTR drops 94 % on second occurrence (methodology).
$ cd my-nextjs-app && npx great-cto init ✓ scanning manifests… found package.json ✓ stack: nextjs (TypeScript) ✓ archetype: mobile-app ⚠ archetype + stack combo is unusual — review overlay manually ✓ 83 agents ready $ /start "add in-app purchase verification" ▸ architect drafting ARCH-mobile-app.md… ▸ pm decomposing into beads tasks… ⚐ gate:plan — your approval needed
Approve → 3 senior-devs run in parallel worktrees → 5 reviewers fan out in parallel → gate:ship → deploy. One real run walked stage-by-stage: /proof.
This is the shape of what senior-dev drafts for "in-app purchase verification" — auth first, schema validation, and the audit line the mobile-app reviewer requires before gate:ship opens.
// app/api/mobile-app/route.ts — drafted by senior-dev, reviewed by 5 agents
import { NextResponse } from 'next/server';
import { requireAuth } from '@/lib/auth'; // security-officer: auth before handler
import { auditLog } from '@/lib/audit'; // gate:mobile-app: every decision logged
export async function POST(req: Request) {
const user = await requireAuth(req);
const body = await req.json(); // qa-engineer: zod schema enforced
const result = await handleMobileApp(body, user);
await auditLog({ who: user.id, what: 'in-app purchase verification', confidence: result.confidence });
return NextResponse.json(result);
}mobile-app overlay.Consumer apps with IAP receipt validation.
B2B field apps with offline-first sync.
Apps with push pipelines and privacy nutrition labels.
Next.js (TypeScript) is not a typical fit for mobile app. The archetype overlay still attaches, but you may want to override defaults more aggressively. Check the mobile-app archetype page for the typical stack list and decide if your case is the right tool / right archetype.
No black-box "AI does it all" loop. GreatCTO is a deterministic state machine — 8 stages, 22 nodes, 2 human gates. Every node maps to a real agent on GitHub. Inspect the state machine →
$ npx great-cto init
Free, MIT, runs locally. Built as a Claude Code plugin — install with one command.
Eight stages, two human gates, four memory layers. Why this exact shape, and what I tried that didn't work.
One run, one feature, from prompt to merged PR. Time, cost, and gate-by-gate breakdown — no marketing math.
Regex vs LLM-based archetype detection, the false-positive count, and why I keep rejecting the obvious fix.
The bottleneck in agentic SDLC isn't model quality — it's process governance. Here's the state machine that closes the gap.