一个高性能Next.js 16.4.2（应用路由器）Turborepo monorepo，面向任务型组织，包含三个应用（apps/admin、apps/donor]）和共享工作区包（packages/*）。

快速开始

对于可选的六代理 GitHub issue-to-develop 工作流程，请使用 Samson Codex Cloud 指南。 node scripts/factory/setup-cloud.mjs 安装冻结依赖和原生 个人指令;--verify-only检查现有设置，无需修复。 协调者控制本地切换;设置不会启动问题试验。

1. 安装前置条件： Node.js 24.22.1、Bun 1.4.3 和 Git，安装在你的 PATH。
2. 选择你的设置路径。

无需凭证的任务控制沙盒

用这条路径做一个新的克隆、一次性代理环境，或者第一次运行时 你还没有Supabase的凭证：

然后打开 http://localhost:3030。设置命令创建 gitignored .env.local 默认，安装依赖，并运行冻结锁文件 bun run skills:verify。

托管的Supabase应用开发

当你有 Supabase 项目 URL 和匿名公钥时，可以使用这条路径：

1. 运行设置（创建’.env.’

Asymmetric.al - Kingdom Impact Platform

A high-performance Next.js 16.4.2 (App Router) Turborepo monorepo for mission-focused organizations, with three apps (apps/admin, apps/donor, apps/missionary) and shared workspace packages (packages/*).

Quickstart

For the optional six-agent GitHub issue-to-develop workflow, use the Samson Codex Cloud guide. node scripts/factory/setup-cloud.mjs installs frozen dependencies and native personal instructions; --verify-only checks existing setup without repair. The coordinator controls native handoffs; setup does not start an issue trial.

1. Install prerequisites: Node.js 24.22.1, Bun 1.4.3, and Git on your PATH.
2. Choose your setup path.

Credential-free Mission Control sandbox

Use this path for a fresh clone, disposable agent environment, or first run when you do not have Supabase credentials yet:

bun run setup:mission-control:cloud
bun run dev:mission-control

Then open http://localhost:3030. The setup command creates gitignored .env.local defaults, installs dependencies with the frozen lockfile, and runs bun run skills:verify.

Hosted Supabase app development

Use this path when you have a Supabase project URL and anon public key:

1. Run setup (creates .env.local on first run if needed, installs dependencies, checks that committed skill mirrors match docs/ai/skills/, then runs repo setup checks):
   • macOS / Linux / Git Bash: bun run setup
   • Windows PowerShell: see Windows below (.\scripts\setup.ps1).
2. Fill required Supabase values in .env.local if the first run stopped with “missing required env vars”, then run setup again.
3. Start dev: bun run dev (or an app-specific script from package.json). For a single surface, bun run dev:donor is typical (donor on port 3000).
4. Optional smoke check: bun run verify (implemented in scripts/verify/index.mjs). Set VERIFY_HTTP=1 and VERIFY_BASE_URL= when you also want HTTP route checks.

After git pull when skill files changed: run bun run skills:verify. If it reports drift between docs/ai/skills/ and the mirrors under .agents/skills/, .cursor/skills/, and .claude/skills/, run bun run skills:sync and commit the updated mirror files so CI and teammates stay aligned.

Required for hosted Supabase app development: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY

Optional: Other entries in .env.example (Stripe, demo accounts, etc.)

bun run dev runs all apps via Turbo (turbo run dev). Default HTTP checks in bun run verify use http://localhost:3000 (VERIFY_BASE_URL), so use bun run dev:donor (or point VERIFY_BASE_URL at the app you are running).

Per-app dev commands (from root package.json):

• bun run dev:donor → donor app, port 3000
• bun run dev:admin → admin app, port 3030