cfsa-antigravity 2.0.0 → 2.2.0

package/template/.agent/skills/workflow-automation/references/inngest.md

@@ -0,0 +1,88 @@
+# Inngest Workflow Patterns
+
+Ecosystem-specific patterns for the `workflow-automation` skill. Read `SKILL.md` first for universal methodology.
+
+---
+
+## Sequential Steps
+
+```typescript
+const syncUser = inngest.createFunction(
+  { id: "sync-user-data" },
+  { event: "user/signup.completed" },
+  async ({ event, step }) => {
+    const user = await step.run("create-db-record", async () => {
+      return db.users.create({ email: event.data.email });
+    });
+
+    const stripeCustomer = await step.run("create-stripe-customer", async () => {
+      return stripe.customers.create({ email: user.email });
+    });
+
+    await step.run("send-welcome-email", async () => {
+      return email.send({ to: user.email, template: "welcome" });
+    });
+  }
+);
+```
+
+## Fan-Out
+
+```typescript
+// Each function subscribes to the same event — runs independently
+const sendWelcome = inngest.createFunction(
+  { id: "send-welcome-email" },
+  { event: "user/signup.completed" },
+  async ({ event, step }) => {
+    await step.run("send", async () => {
+      await email.send({ to: event.data.email, template: "welcome" });
+    });
+  }
+);
+
+const startTrial = inngest.createFunction(
+  { id: "start-stripe-trial" },
+  { event: "user/signup.completed" },
+  async ({ event, step }) => {
+    await step.run("create-trial", async () => {
+      await stripe.subscriptions.create({
+        customer: event.data.stripeId,
+        trial_period_days: 14,
+      });
+    });
+  }
+);
+```
+
+## Idempotency
+
+```typescript
+const processPayment = inngest.createFunction(
+  {
+    id: "process-payment",
+    idempotency: "event.data.orderId", // Dedup within 24h
+  },
+  { event: "order/payment.requested" },
+  async ({ event, step }) => {
+    await step.run("charge", async () => {
+      return stripe.charges.create({
+        amount: event.data.amount,
+        idempotencyKey: event.data.orderId, // Stripe-level too
+      });
+    });
+  }
+);
+```
+
+## Scheduled/Recurring
+
+```typescript
+const dailyReport = inngest.createFunction(
+  { id: "daily-metrics-report" },
+  { cron: "0 9 * * *" }, // 9am daily
+  async ({ step }) => {
+    const metrics = await step.run("fetch-metrics", fetchDailyMetrics);
+    await step.run("send-report", async () => sendSlackReport(metrics));
+  }
+);
+```

package/template/.agent/skills/workflow-automation/references/temporal.md

@@ -0,0 +1,64 @@
+# Temporal Workflow Patterns
+
+Ecosystem-specific patterns for the `workflow-automation` skill. Read `SKILL.md` first for universal methodology.
+
+---
+
+## Sequential Steps (Activities)
+
+```typescript
+// activities.ts
+export async function createDbRecord(email: string): Promise<User> {
+  return db.users.create({ email });
+}
+
+export async function createStripeCustomer(email: string): Promise<Customer> {
+  return stripe.customers.create({ email });
+}
+
+// workflows.ts
+const { createDbRecord, createStripeCustomer } = proxyActivities<typeof activities>({
+  startToCloseTimeout: "30 seconds",
+  retry: { initialInterval: "1s", maximumAttempts: 3 },
+});
+
+export async function syncUserWorkflow(email: string): Promise<void> {
+  const user = await createDbRecord(email);
+  const customer = await createStripeCustomer(user.email);
+}
+```
+
+## Human-in-the-Loop (Signals)
+
+```typescript
+export const approvalSignal = defineSignal<[boolean]>("approval");
+
+export async function purchaseWorkflow(amount: number): Promise<string> {
+  if (amount > 10000) {
+    let approved: boolean | undefined;
+
+    setHandler(approvalSignal, (isApproved) => {
+      approved = isApproved;
+    });
+
+    // Workflow sleeps until signal or 72h timeout
+    const gotApproval = await condition(() => approved !== undefined, "72 hours");
+
+    if (!gotApproval || !approved) {
+      return "Purchase denied or timed out";
+    }
+  }
+
+  return "Purchase completed";
+}
+```
+
+## Critical Rule: Determinism
+
+Temporal workflows replay from the beginning on recovery. **Workflow code must be deterministic:**
+- ❌ No I/O (database, network, file system)
+- ❌ No `Math.random()` or `Date.now()`
+- ❌ No global mutable state
+- ✅ All I/O goes in activities
+- ✅ Use `workflow.now()` for timestamps
+- ✅ Use `workflow.random()` for randomness

package/template/.agent/workflows/bootstrap-agents-fill.md

@@ -1,5 +1,5 @@
 ---
-description: Receive template values and fill instruction/rule/AGENTS.md templates for the bootstrap-agents workflow
+description: Receive template values and fill surface stack map + instruction/rule/AGENTS.md templates for the bootstrap-agents workflow
 parent: bootstrap-agents
 shard: fill
 standalone: true
@@ -17,153 +17,104 @@ pipeline:
 
 # Bootstrap Agents — Fill Templates
 
-Receive template values from the calling workflow and fill `{{PLACEHOLDER}}` values across all instruction, rule, skill, and root-level templates.
+Receive template values from the calling workflow and fill the surface stack map in `tech-stack.md`, plus global/structural/infrastructure values across instruction, rule, and root-level templates.
 
 **Prerequisite**: If invoked standalone, the caller must provide at least one template key-value pair. If no values are provided, there is nothing to fill — report and exit.
 
 > [!IMPORTANT]
-> This workflow fills template-level placeholders (project name, description, tech stack summary, architecture doc path). It does **NOT** fill workflow command placeholders (`{{VALIDATION_COMMAND}}`, `{{TEST_COMMAND}}`, `{{LINT_COMMAND}}`, etc.) or skill path placeholders (`{{DATABASE_SKILLS}}`, `{{AUTH_SKILL}}`, etc.). Those are filled exclusively by `.agent/workflows/bootstrap-agents-provision.md` during the `/create-prd` stage. Running this workflow standalone will leave those placeholders unfilled with no indication — they require the provision step.
+> This workflow fills the surface stack map and global template values. It does **NOT** provision skills from the library — that is handled exclusively by `.agent/workflows/bootstrap-agents-provision.md`. Running this workflow standalone will populate map cells but not install the corresponding skill directories.
 
 ---
 
-## 1. Receive template values
-
-The calling workflow provides these values (all optional — fill only what's provided, leave others as `{{PLACEHOLDER}}`):
-
-### Command & Tool Values
-
-| Key | Example |
-|-----|---------|
-| `PACKAGE_MANAGER` | pnpm |
-| `DEV_COMMAND` | pnpm dev |
-| `TEST_COMMAND` | pnpm test |
-| `TEST_WATCH_COMMAND` | pnpm test:watch |
-| `TEST_COVERAGE_COMMAND` | pnpm test:coverage |
-| `LINT_COMMAND` | pnpm lint |
-| `LINT_FIX_COMMAND` | pnpm lint:fix |
-| `FORMAT_COMMAND` | pnpm format |
-| `TYPE_CHECK_COMMAND` | pnpm type-check |
-| `BUILD_COMMAND` | pnpm build |
-| `PREVIEW_COMMAND` | pnpm preview |
-| `VALIDATION_COMMAND` | pnpm test && pnpm lint && pnpm type-check && pnpm build |
-
-### Project Identity
-
-| Key | Example |
-|-----|---------|
-| `PROJECT_NAME` | My Project |
-| `DESCRIPTION` | One-line description |
-| `TECH_STACK_SUMMARY` | Astro + React + SurrealDB + Firebase Auth |
-
-### Architecture & Structure
-
-| Key | Example |
-|-----|---------|
-| `FRAMEWORK_PATTERNS` | Framework-specific patterns block |
-| `PROJECT_STRUCTURE` | Directory layout block |
-| `ARCHITECTURE_TABLE` | Concern/Location/Runtime table rows |
-| `ARCHITECTURE_DOC` | docs/plans/2026-02-10-architecture-design.md |
-| `CONTRACTS_DIR` | src/contracts/ |
-| `BUILD_OUTPUT_DIR` | dist/ |
-
-### Stack Values (trigger skill provisioning)
-
-| Key | Example |
-|-----|---------|
-| `DATABASE` | SurrealDB (self-hosted) |
-| `DATABASE_PRIMARY` | PostgreSQL |
-| `DATABASE_VECTOR` | Qdrant |
-| `DATABASE_GRAPH` | Neo4j |
-| `DATABASE_CACHE` | Redis |
-| `DATABASE_TIMESERIES` | TimescaleDB |
-| `FRONTEND_FRAMEWORK` | Astro + React Islands |
-| `BACKEND_FRAMEWORK` | Hono |
-| `API_LAYER` | tRPC |
-| `BACKEND_RUNTIME` | Cloudflare Workers |
-| `ORM` | Drizzle |
-| `CSS_FRAMEWORK` | Tailwind CSS v4 |
-| `UI_LIBRARY` | shadcn/ui |
-| `AUTH_PROVIDER` | Firebase Auth |
-| `PAYMENTS` | Stripe |
-| `AI_SDK` | Vercel AI SDK |
-| `STATE_MANAGEMENT` | TanStack Query |
-| `E2E_TESTING` | Playwright |
-| `UNIT_TESTING` | Vitest |
-| `HOSTING` | Cloudflare Pages + Workers |
-| `CDN_ASSETS` | Cloudflare R2 |
-| `MONITORING` | Sentry |
-| `OBSERVABILITY` | OpenTelemetry |
-| `ANALYTICS` | Google Analytics |
-| `EMAIL` | Resend |
-| `QUEUE` | Inngest |
-| `REALTIME` | Socket.io |
-| `SEARCH` | Meilisearch |
-| `CMS` | Payload CMS |
-| `STORAGE` | AWS S3 |
-| `CI_CD` | GitHub Actions |
-| `MOBILE_FRAMEWORK` | Expo |
-| `LANGUAGE` | TypeScript |
-| `3D_FRAMEWORK` | Three.js / R3F |
-| `DESKTOP_FRAMEWORK` | Tauri |
-| `GAME_ENGINE` | Godot |
-| `SECURITY` | OWASP |
-| `TEST_RUNNER` | Vitest |
-| `LINTER` | ESLint |
-| `TYPE_CHECKER` | TypeScript (tsc) |
-| `CONTRACT_LIBRARY` | Zod |
-
-> **Note**: `DATABASE` is an alias for `DATABASE_PRIMARY` — it triggers the same MANIFEST match. When multiple `DATABASE_*` sub-keys are present, the `DATABASE` row in `tech-stack.md` should expand to show sub-rows (`DATABASE_PRIMARY`, `DATABASE_VECTOR`, etc.) rather than a single combined string. Bootstrap fills each sub-row individually as the user confirms each store.
-
-### Infrastructure Values
-
-| Key | Example |
-|-----|---------|
-| `SSH_HOST` | my-vps |
-| `DB_PORT` | 19000 |
-| `CREDENTIAL_TOOL` | agent-auth ssh-add |
-| `SECRET_MANAGEMENT` | wrangler secret |
-| `DEPLOY_COMMAND` | wrangler deploy |
-
-### Surface Types
-
-| Key | Example |
-|-----|---------|
-| `SURFACES` | web, api |
-
-**Pipeline Context**
-
-| Key | Example | Purpose |
-|-----|---------|---------|
-| `PIPELINE_STAGE` | `create-prd`, `write-be-spec`, `write-fe-spec`, `implement-slice` | Context of this invocation — used to validate correct keys are being passed |
-| `SKILL_BUNDLE` | `database-schema-design,migration-management,error-handling-patterns` | When provided, bootstrap loads all listed skills in one invocation |
-
-If any values are missing, leave those `{{PLACEHOLDER}}`s in place — they'll be filled on a future invocation.
+## 1. Receive values
+
+Accept values in the categories defined in `.agent/skills/bootstrap-agents/SKILL.md` (Section 1):
+- **Surface-keyed values** → Per-Surface Skills table
+- **Cross-cutting values** → Cross-Cutting Skills table
+- **Global values** → Global Settings table + root configs
+- **Structural values** → instruction templates
+- **Infrastructure values** → instruction templates
+- **Pipeline context** → `PIPELINE_STAGE` for validation
+
+If any values are missing, leave those cells/placeholders in place — they'll be filled on a future invocation.
 
 ---
 
-## 2. Fill instruction templates
+## 2. Fill the surface stack map
+
+Open `.agent/instructions/tech-stack.md`.
+
+### 2a. Per-Surface Skills table
+
+For each `SURFACE=<name>` received:
+
+1. **Row exists** → update only the cells for provided column keys. Do NOT overwrite cells that already have values unless the caller explicitly re-provides a value.
+2. **Row doesn't exist** → add a new row. Fill provided columns, use `—` for all unprovided columns.
+3. **Appending to existing cells** → if a column already has a value and the caller provides additional values, append with comma separation. Example: existing `supabase` + new `surrealdb` → `supabase, surrealdb`. Skip duplicates.
+
+### 2b. Cross-Cutting Skills table
+
+For each cross-cutting key received:
+1. **Category exists with value** → append to comma-separated list (skip duplicates)
+2. **Category exists, empty** → set the value
+3. **Accumulated values** (e.g., `DATABASE_*` sub-keys like `DATABASE_PRIMARY`, `DATABASE_VECTOR`) → each sub-key appends to the Databases column of the relevant surface AND to the cross-cutting Databases row if applicable
+
+### 2c. Global Settings table
+
+Fill `PROJECT_NAME`, `DESCRIPTION`, `TECH_STACK_SUMMARY`, `SURFACES`, `ARCHITECTURE_DOC` as provided.
+
+---
+
+## 3. Fill instruction templates
 
 ### `.agent/instructions/commands.md`
-Replace: `{{PACKAGE_MANAGER}}`, `{{DEV_COMMAND}}`, `{{TEST_COMMAND}}`, `{{TEST_WATCH_COMMAND}}`, `{{TEST_COVERAGE_COMMAND}}`, `{{LINT_COMMAND}}`, `{{LINT_FIX_COMMAND}}`, `{{FORMAT_COMMAND}}`, `{{TYPE_CHECK_COMMAND}}`, `{{BUILD_COMMAND}}`, `{{PREVIEW_COMMAND}}`, `{{VALIDATION_COMMAND}}`
+
+Write per-surface command sections. For each surface in the map:
+
+```markdown
+## <Surface> Commands
+
+| Command | Value |
+|---------|-------|
+| Package Manager | <from map> |
+| Dev | <from map> |
+| Test | <from map> |
+| Lint | <from map> |
+| Build | <from map> |
+| Validation | <from map> |
+```
+
+If single-surface, omit the surface header — just write a flat commands table.
 
 ### `.agent/instructions/workflow.md`
-Replace: `{{VALIDATION_COMMAND}}`
+Fill `{{VALIDATION_COMMAND}}` with the primary surface's validation command (first non-`shared` row in the map, or `shared` if only one row exists).
 
 ### `.agent/instructions/patterns.md`
-Replace: `{{FRAMEWORK_PATTERNS}}` if provided
+Replace `{{FRAMEWORK_PATTERNS}}` if provided.
 
 ### `.agent/instructions/structure.md`
-Replace: `{{PROJECT_STRUCTURE}}`, `{{ARCHITECTURE_TABLE}}` if provided
+Replace `{{PROJECT_STRUCTURE}}`, `{{ARCHITECTURE_TABLE}}` if provided.
 
-### `.agent/instructions/tech-stack.md`
-Replace: `{{TECH_STACK_SUMMARY}}`, `{{FRONTEND_FRAMEWORK}}`, `{{BACKEND_RUNTIME}}`, `{{DATABASE}}`, `{{AUTH_PROVIDER}}`, `{{HOSTING}}`, `{{CDN_ASSETS}}`, `{{CICD}}`, `{{MONITORING}}`, `{{PACKAGE_MANAGER}}`, `{{TEST_RUNNER}}`, `{{LINTER}}`, `{{TYPE_CHECKER}}`, `{{INSTALLED_SKILLS}}`, `{{ARCHITECTURE_DOC}}`
-Replace: `{{ARCHITECTURE_DOC}}` with the dated architecture design filename (e.g., `docs/plans/YYYY-MM-DD-architecture-design.md`)
+---
+
+## 4. Fill root agent config files (AGENTS.md and GEMINI.md)
+
+Replace in **both** `AGENTS.md` and `GEMINI.md`:
+- `{{PROJECT_NAME}}`
+- `{{DESCRIPTION}}`
+- `{{TECH_STACK_SUMMARY}}`
+- `{{VALIDATION_COMMAND}}` — primary surface's validation command
+- `{{ARCHITECTURE_DOC}}`
+- `{{CONTRACT_LIBRARY}}`
+- `{{INSTALLED_SKILLS}}` (if provided at this invocation; otherwise leave for `bootstrap-agents-provision` Step 8)
+
+> **Note**: Both files serve as root agent config. Both must be kept in sync.
 
 ---
 
-## 3. Fill default operational skill templates
+## 5. Fill operational skill and rule templates
 
-Scan all `.agent/skills/*/SKILL.md` files for `{{PLACEHOLDER}}` values and fill any that match the provided template values:
+Scan all `.agent/skills/*/SKILL.md` files for `{{PLACEHOLDER}}` values and fill any that match:
 
 - `{{VALIDATION_COMMAND}}` — in `fix-bug`, `main-workflow`, `deploy`, `refactor`
 - `{{PACKAGE_MANAGER}}` — in `refactor`, `security-audit`
@@ -175,27 +126,18 @@ Scan all `.agent/skills/*/SKILL.md` files for `{{PLACEHOLDER}}` values and fill
 - `{{DB_PORT}}` — in `setup-session`
 - `{{CREDENTIAL_TOOL}}` — in `setup-session`
 
-Also scan all `.agent/rules/*.md` files for `{{PLACEHOLDER}}` values and fill any that match the provided template values. Currently applicable: `{{CONTRACT_LIBRARY}}` in `tdd-contract-first.md`.
+Also scan `.agent/rules/*.md`: `{{CONTRACT_LIBRARY}}` in `tdd-contract-first.md`.
 
 ---
 
-## 4. Fill root agent config files (AGENTS.md and GEMINI.md)
-
-Replace in **both** `AGENTS.md` and `GEMINI.md`:
-- `{{PROJECT_NAME}}`
-- `{{DESCRIPTION}}`
-- `{{TECH_STACK_SUMMARY}}`
-- `{{VALIDATION_COMMAND}}`
-- `{{ARCHITECTURE_DOC}}`
-- `{{INSTALLED_SKILLS}}` (if provided at this invocation; otherwise leave for `bootstrap-agents-provision` Step 8 to fill after skill provisioning)
-
-> **Note**: Both files serve as root agent config for their respective agents (`AGENTS.md` for Claude Code / Antigravity, `GEMINI.md` for Gemini CLI). Both must be kept in sync — any placeholder filled in one must be filled in the other.
-
-### Report and proceed
-
-Report which `{{PLACEHOLDER}}`s were filled and their values, which remain unfilled, and any errors encountered.
+## 6. Report and proceed
 
-If invoked standalone, the next step is `/bootstrap-agents-provision` to provision skills from the library based on the stack values just filled.
+Report:
+- Which map cells were filled (and their values)
+- Which map cells remain empty
+- Which instruction template placeholders were filled
+- Any errors encountered
 
-If invoked by another workflow (e.g., `/create-prd`), return this report to the calling workflow — the caller will invoke `/bootstrap-agents-provision` automatically.
+If invoked standalone, the next step is `/bootstrap-agents-provision` to provision skills using the 4-tier resolution chain.
 
+If invoked by another workflow (e.g., `/create-prd`), return this report to the calling workflow.