cfsa-antigravity 1.0.0

package/template/.agent/skills/tdd-workflow/SKILL.md

@@ -0,0 +1,409 @@
+---
+name: tdd-workflow
+description: Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
+---
+
+# Test-Driven Development Workflow
+
+This skill ensures all code development follows TDD principles with comprehensive test coverage.
+
+## When to Activate
+
+- Writing new features or functionality
+- Fixing bugs or issues
+- Refactoring existing code
+- Adding API endpoints
+- Creating new components
+
+## Core Principles
+
+### 1. Tests BEFORE Code
+ALWAYS write tests first, then implement code to make tests pass.
+
+### 2. Coverage Requirements
+- Minimum 80% coverage (unit + integration + E2E)
+- All edge cases covered
+- Error scenarios tested
+- Boundary conditions verified
+
+### 3. Test Types
+
+#### Unit Tests
+- Individual functions and utilities
+- Component logic
+- Pure functions
+- Helpers and utilities
+
+#### Integration Tests
+- API endpoints
+- Database operations
+- Service interactions
+- External API calls
+
+#### E2E Tests (Playwright)
+- Critical user flows
+- Complete workflows
+- Browser automation
+- UI interactions
+
+## TDD Workflow Steps
+
+### Step 1: Write User Journeys
+```
+As a [role], I want to [action], so that [benefit]
+
+Example:
+As a user, I want to search for markets semantically,
+so that I can find relevant markets even without exact keywords.
+```
+
+### Step 2: Generate Test Cases
+For each user journey, create comprehensive test cases:
+
+```typescript
+describe('Semantic Search', () => {
+  it('returns relevant markets for query', async () => {
+    // Test implementation
+  })
+
+  it('handles empty query gracefully', async () => {
+    // Test edge case
+  })
+
+  it('falls back to substring search when Redis unavailable', async () => {
+    // Test fallback behavior
+  })
+
+  it('sorts results by similarity score', async () => {
+    // Test sorting logic
+  })
+})
+```
+
+### Step 3: Run Tests (They Should Fail)
+```bash
+npm test
+# Tests should fail - we haven't implemented yet
+```
+
+### Step 4: Implement Code
+Write minimal code to make tests pass:
+
+```typescript
+// Implementation guided by tests
+export async function searchMarkets(query: string) {
+  // Implementation here
+}
+```
+
+### Step 5: Run Tests Again
+```bash
+npm test
+# Tests should now pass
+```
+
+### Step 6: Refactor
+Improve code quality while keeping tests green:
+- Remove duplication
+- Improve naming
+- Optimize performance
+- Enhance readability
+
+### Step 7: Verify Coverage
+```bash
+npm run test:coverage
+# Verify 80%+ coverage achieved
+```
+
+## Testing Patterns
+
+### Unit Test Pattern (Jest/Vitest)
+```typescript
+import { render, screen, fireEvent } from '@testing-library/react'
+import { Button } from './Button'
+
+describe('Button Component', () => {
+  it('renders with correct text', () => {
+    render(<Button>Click me</Button>)
+    expect(screen.getByText('Click me')).toBeInTheDocument()
+  })
+
+  it('calls onClick when clicked', () => {
+    const handleClick = jest.fn()
+    render(<Button onClick={handleClick}>Click</Button>)
+
+    fireEvent.click(screen.getByRole('button'))
+
+    expect(handleClick).toHaveBeenCalledTimes(1)
+  })
+
+  it('is disabled when disabled prop is true', () => {
+    render(<Button disabled>Click</Button>)
+    expect(screen.getByRole('button')).toBeDisabled()
+  })
+})
+```
+
+### API Integration Test Pattern
+```typescript
+import { NextRequest } from 'next/server'
+import { GET } from './route'
+
+describe('GET /api/markets', () => {
+  it('returns markets successfully', async () => {
+    const request = new NextRequest('http://localhost/api/markets')
+    const response = await GET(request)
+    const data = await response.json()
+
+    expect(response.status).toBe(200)
+    expect(data.success).toBe(true)
+    expect(Array.isArray(data.data)).toBe(true)
+  })
+
+  it('validates query parameters', async () => {
+    const request = new NextRequest('http://localhost/api/markets?limit=invalid')
+    const response = await GET(request)
+
+    expect(response.status).toBe(400)
+  })
+
+  it('handles database errors gracefully', async () => {
+    // Mock database failure
+    const request = new NextRequest('http://localhost/api/markets')
+    // Test error handling
+  })
+})
+```
+
+### E2E Test Pattern (Playwright)
+```typescript
+import { test, expect } from '@playwright/test'
+
+test('user can search and filter markets', async ({ page }) => {
+  // Navigate to markets page
+  await page.goto('/')
+  await page.click('a[href="/markets"]')
+
+  // Verify page loaded
+  await expect(page.locator('h1')).toContainText('Markets')
+
+  // Search for markets
+  await page.fill('input[placeholder="Search markets"]', 'election')
+
+  // Wait for debounce and results
+  await page.waitForTimeout(600)
+
+  // Verify search results displayed
+  const results = page.locator('[data-testid="market-card"]')
+  await expect(results).toHaveCount(5, { timeout: 5000 })
+
+  // Verify results contain search term
+  const firstResult = results.first()
+  await expect(firstResult).toContainText('election', { ignoreCase: true })
+
+  // Filter by status
+  await page.click('button:has-text("Active")')
+
+  // Verify filtered results
+  await expect(results).toHaveCount(3)
+})
+
+test('user can create a new market', async ({ page }) => {
+  // Login first
+  await page.goto('/creator-dashboard')
+
+  // Fill market creation form
+  await page.fill('input[name="name"]', 'Test Market')
+  await page.fill('textarea[name="description"]', 'Test description')
+  await page.fill('input[name="endDate"]', '2025-12-31')
+
+  // Submit form
+  await page.click('button[type="submit"]')
+
+  // Verify success message
+  await expect(page.locator('text=Market created successfully')).toBeVisible()
+
+  // Verify redirect to market page
+  await expect(page).toHaveURL(/\/markets\/test-market/)
+})
+```
+
+## Test File Organization
+
+```
+src/
+├── components/
+│   ├── Button/
+│   │   ├── Button.tsx
+│   │   ├── Button.test.tsx          # Unit tests
+│   │   └── Button.stories.tsx       # Storybook
+│   └── MarketCard/
+│       ├── MarketCard.tsx
+│       └── MarketCard.test.tsx
+├── app/
+│   └── api/
+│       └── markets/
+│           ├── route.ts
+│           └── route.test.ts         # Integration tests
+└── e2e/
+    ├── markets.spec.ts               # E2E tests
+    ├── trading.spec.ts
+    └── auth.spec.ts
+```
+
+## Mocking External Services
+
+### Supabase Mock
+```typescript
+jest.mock('@/lib/supabase', () => ({
+  supabase: {
+    from: jest.fn(() => ({
+      select: jest.fn(() => ({
+        eq: jest.fn(() => Promise.resolve({
+          data: [{ id: 1, name: 'Test Market' }],
+          error: null
+        }))
+      }))
+    }))
+  }
+}))
+```
+
+### Redis Mock
+```typescript
+jest.mock('@/lib/redis', () => ({
+  searchMarketsByVector: jest.fn(() => Promise.resolve([
+    { slug: 'test-market', similarity_score: 0.95 }
+  ])),
+  checkRedisHealth: jest.fn(() => Promise.resolve({ connected: true }))
+}))
+```
+
+### OpenAI Mock
+```typescript
+jest.mock('@/lib/openai', () => ({
+  generateEmbedding: jest.fn(() => Promise.resolve(
+    new Array(1536).fill(0.1) // Mock 1536-dim embedding
+  ))
+}))
+```
+
+## Test Coverage Verification
+
+### Run Coverage Report
+```bash
+npm run test:coverage
+```
+
+### Coverage Thresholds
+```json
+{
+  "jest": {
+    "coverageThresholds": {
+      "global": {
+        "branches": 80,
+        "functions": 80,
+        "lines": 80,
+        "statements": 80
+      }
+    }
+  }
+}
+```
+
+## Common Testing Mistakes to Avoid
+
+### ❌ WRONG: Testing Implementation Details
+```typescript
+// Don't test internal state
+expect(component.state.count).toBe(5)
+```
+
+### ✅ CORRECT: Test User-Visible Behavior
+```typescript
+// Test what users see
+expect(screen.getByText('Count: 5')).toBeInTheDocument()
+```
+
+### ❌ WRONG: Brittle Selectors
+```typescript
+// Breaks easily
+await page.click('.css-class-xyz')
+```
+
+### ✅ CORRECT: Semantic Selectors
+```typescript
+// Resilient to changes
+await page.click('button:has-text("Submit")')
+await page.click('[data-testid="submit-button"]')
+```
+
+### ❌ WRONG: No Test Isolation
+```typescript
+// Tests depend on each other
+test('creates user', () => { /* ... */ })
+test('updates same user', () => { /* depends on previous test */ })
+```
+
+### ✅ CORRECT: Independent Tests
+```typescript
+// Each test sets up its own data
+test('creates user', () => {
+  const user = createTestUser()
+  // Test logic
+})
+
+test('updates user', () => {
+  const user = createTestUser()
+  // Update logic
+})
+```
+
+## Continuous Testing
+
+### Watch Mode During Development
+```bash
+npm test -- --watch
+# Tests run automatically on file changes
+```
+
+### Pre-Commit Hook
+```bash
+# Runs before every commit
+npm test && npm run lint
+```
+
+### CI/CD Integration
+```yaml
+# GitHub Actions
+- name: Run Tests
+  run: npm test -- --coverage
+- name: Upload Coverage
+  uses: codecov/codecov-action@v3
+```
+
+## Best Practices
+
+1. **Write Tests First** - Always TDD
+2. **One Assert Per Test** - Focus on single behavior
+3. **Descriptive Test Names** - Explain what's tested
+4. **Arrange-Act-Assert** - Clear test structure
+5. **Mock External Dependencies** - Isolate unit tests
+6. **Test Edge Cases** - Null, undefined, empty, large
+7. **Test Error Paths** - Not just happy paths
+8. **Keep Tests Fast** - Unit tests < 50ms each
+9. **Clean Up After Tests** - No side effects
+10. **Review Coverage Reports** - Identify gaps
+
+## Success Metrics
+
+- 80%+ code coverage achieved
+- All tests passing (green)
+- No skipped or disabled tests
+- Fast test execution (< 30s for unit tests)
+- E2E tests cover critical user flows
+- Tests catch bugs before production
+
+---
+
+**Remember**: Tests are not optional. They are the safety net that enables confident refactoring, rapid development, and production reliability.

package/template/.agent/skills/tech-stack-catalog/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: tech-stack-catalog
+description: "Per-surface tech stack decision tables and development tooling options. Use during /create-prd-stack to present constraint-filtered options to the user."
+category: reference
+risk: none
+source: self
+date_added: "2026-02-28"
+---
+
+# Tech Stack Catalog
+
+Reference tables for tech stack decisions organized by project surface type. Used by `/create-prd-stack` to present constraint-filtered options.
+
+## When to Use This Skill
+
+- During `/create-prd-stack` — load the decision tables for each applicable surface
+- When adding a new surface to an existing project
+- When evaluating tech stack alternatives
+
+## How to Use
+
+1. Read the project's surface classification from `vision.md`
+2. Load `references/surface-decision-tables.md` for the applicable surface sections
+3. Filter options using constraint questions before presenting
+4. Load `references/dev-tooling-decisions.md` for development tooling
+
+## Reference Files
+
+| File | Contents |
+|------|----------|
+| `references/surface-decision-tables.md` | Universal, web, desktop, mobile, CLI, multi-surface decision axes |
+| `references/dev-tooling-decisions.md` | Package manager, test runner, linter, type checker + bootstrap keys |
+| `references/constraint-questions.md` | Per-axis constraint questions for filtering options |
+
+## Option Presentation Format
+
+For each axis, filter options using constraints, then present:
+
+| # | Option | Strengths | Risks | Fit |
+|---|--------|-----------|-------|-----|
+| 1 | [Option] | ... | ... | [/5] |
+| H | **Hybrid** | [Combine elements] | ... | [/5] |
+
+> **Recommendation**: Based on constraints [list], **Option [N]** scores highest because [rationale].
+
+## Related Skills
+
+- `design-direction` — visual direction interview (runs during stack decisions)
+- `brainstorming` — one-decision-at-a-time approach

package/template/.agent/skills/tech-stack-catalog/references/constraint-questions.md

@@ -0,0 +1,21 @@
+# Constraint Questions
+
+Use these per-axis constraint questions to filter the option space before presenting choices.
+
+| Axis | Constraint Questions |
+|------|---------------------|
+| **Hosting** | Is there an existing cloud provider? Budget ceiling per month? Compliance requirements (data residency, SOC2)? Team familiarity? |
+| **Database** | Expected data volume? Read/write ratio? Need for graph/document/relational? Existing database expertise? Multi-tenancy requirements? |
+| **Auth** | Social login required? SSO/SAML needed? Age verification? Compliance (COPPA, GDPR)? Budget for auth provider? |
+| **Frontend framework** | SSR required for SEO? Static site sufficient? Interactive app needs? Team framework experience? |
+| **Backend runtime** | Latency requirements? Cold start tolerance? Existing language expertise? Deployment target (edge, server, serverless)? |
+| **CI/CD** | Existing CI provider? Monorepo or polyrepo? Deployment frequency? Manual approval gates needed? |
+
+## Per-axis flow
+
+1. Ask the constraint questions for this axis
+2. Filter options based on answers
+3. Present the filtered option table with recommendation
+4. Wait for user confirmation
+5. Fire bootstrap with only that key: read `.agent/workflows/bootstrap-agents.md` and call with `PIPELINE_STAGE=create-prd` + the confirmed key (e.g., `DATABASE=SurrealDB`)
+6. Move to next axis

package/template/.agent/skills/tech-stack-catalog/references/dev-tooling-decisions.md

@@ -0,0 +1,37 @@
+# Development Tooling Decisions
+
+## Tooling axes
+
+| Tool | Question |
+|------|----------|
+| **Package manager / build system** | pnpm, npm, yarn, bun, cargo, go modules, pip/poetry? |
+| **Test runner** | Vitest, Jest, pytest, cargo test, go test, XCTest? |
+| **Linter** | ESLint, Biome, Ruff, clippy, golangci-lint? |
+| **Type checker** | TypeScript (tsc), mypy, Rust compiler, Go compiler? |
+| **Build command** | What builds the project for production? |
+
+## Bootstrap keys to fire after confirmation
+
+After the user confirms all development tooling, fire bootstrap with `PIPELINE_STAGE=create-prd` and ALL of these keys:
+
+- `PACKAGE_MANAGER` — the confirmed package manager (e.g., `pnpm`)
+- `TEST_RUNNER` — the confirmed test runner (e.g., `vitest`)
+- `LINTER` — the confirmed linter (e.g., `eslint`)
+- `TYPE_CHECKER` — the confirmed type checker (e.g., `tsc`)
+- `TEST_COMMAND` — derived from package manager + test runner (e.g., `pnpm test`)
+- `TEST_WATCH_COMMAND` — derived test watch command (e.g., `pnpm test:watch`)
+- `TEST_COVERAGE_COMMAND` — derived coverage command (e.g., `pnpm test:coverage`)
+- `LINT_COMMAND` — derived lint command (e.g., `pnpm lint`)
+- `LINT_FIX_COMMAND` — derived lint fix command (e.g., `pnpm lint:fix`)
+- `FORMAT_COMMAND` — derived format command (e.g., `pnpm format`)
+- `TYPE_CHECK_COMMAND` — derived type-check command (e.g., `pnpm type-check`)
+- `BUILD_COMMAND` — derived build command (e.g., `pnpm build`)
+- `VALIDATION_COMMAND` — the full validation pipeline (e.g., `pnpm test && pnpm lint && pnpm type-check && pnpm build`)
+
+This fills command placeholders in `commands.md`, `workflow.md`, `implement-slice-tdd.md`, and `validate-phase.md`.
+
+## Validation command derivation
+
+```
+{{BUILD_TOOL}} test && {{BUILD_TOOL}} lint && {{BUILD_TOOL}} type-check && {{BUILD_TOOL}} build
+```

package/template/.agent/skills/tech-stack-catalog/references/surface-decision-tables.md

@@ -0,0 +1,69 @@
+# Surface Decision Tables
+
+## Universal decisions (all project types)
+
+| Axis | Decision Needed |
+|------|----------------|
+| **Primary language(s)** | TypeScript, Rust, Go, Python, Swift, Kotlin, C++, etc. |
+| **Database** | ⚠️ **Handled by Persistence Map Interview** in `create-prd-stack.md` — do NOT process as a single axis. Covers primary, vector, graph, cache, and time-series sub-keys. |
+| **Auth provider** | Firebase vs Auth0 vs Clerk vs custom vs OS-level keychain |
+| **CI/CD** | GitHub Actions vs GitLab CI vs custom |
+| **Monitoring** | Sentry vs Datadog vs custom |
+
+## Web surface decisions
+
+| Axis | Decision Needed |
+|------|----------------|
+| **Frontend framework** | SSR vs SSG vs hybrid, which framework (Next.js, Astro, SvelteKit, etc.) |
+| **Backend runtime** | Edge workers vs traditional server vs serverless |
+| **Hosting** | Cloudflare vs Vercel vs AWS vs self-hosted |
+| **CDN/Assets** | Provider-native vs S3 vs Cloudinary |
+
+## Desktop surface decisions
+
+| Axis | Decision Needed |
+|------|----------------|
+| **UI framework** | Tauri vs Electron vs native (GTK, Qt, SwiftUI, WPF, WinUI) |
+| **Cross-platform strategy** | Single OS, cross-platform with shared UI (Tauri, Electron, Flutter Desktop), or cross-platform with native UI per OS |
+| **Local data storage** | SQLite vs LevelDB vs filesystem vs embedded DB (RocksDB, etc.) |
+| **Distribution** | Installer type (MSI, DMG, AppImage, Flatpak), auto-updater strategy (Sparkle, squirrel, custom) |
+| **OS targets** | Windows, macOS, Linux — which combinations and minimum versions? |
+
+## Mobile surface decisions
+
+| Axis | Decision Needed |
+|------|----------------|
+| **Framework** | Native per-platform (Swift/Kotlin) vs cross-platform (React Native, Flutter, .NET MAUI, Kotlin Multiplatform) |
+| **Cross-platform strategy** | iOS-only, Android-only, or both? Shared codebase or separate? |
+| **Local data storage** | SQLite, Realm, Core Data, Room |
+| **Distribution** | App Store, Play Store, enterprise sideload, TestFlight/Firebase App Distribution |
+| **OS targets** | iOS minimum version, Android minimum API level |
+
+## Desktop + Mobile shared decisions
+
+Some frameworks support building for **both** desktop and mobile from one codebase. If the vision indicates this is desired:
+
+| Axis | Decision Needed |
+|------|----------------|
+| **Shared framework** | Flutter (desktop + mobile + web), Kotlin Multiplatform, .NET MAUI, Compose Multiplatform |
+| **Shared vs platform-specific UI** | Fully shared UI, shared logic with native UI per platform, or hybrid? |
+| **Platform-specific features** | What functionality requires native code per platform? (file system, notifications, hardware access) |
+
+## CLI surface decisions
+
+| Axis | Decision Needed |
+|------|----------------|
+| **Language** | Rust (clap), Go (cobra), Python (click/typer), Node (commander/yargs) |
+| **Distribution** | npm, cargo, homebrew, apt, binary releases (goreleaser, cross) |
+| **Shell integration** | Tab completions, man pages, config file format (TOML, YAML, JSON) |
+
+## Multi-surface connection decisions (2+ connected surfaces)
+
+| Axis | Decision Needed |
+|------|----------------|
+| **Shared API protocol** | REST vs gRPC vs GraphQL vs WebSocket between surfaces |
+| **Sync strategy** | Real-time (WebSocket/SSE), eventual consistency (message queue), batch (cron), offline-first (CRDT/merge) |
+| **Shared contract layer** | How are data shapes shared? Monorepo with shared package? Published npm/crate package? Code generation from OpenAPI/protobuf? |
+| **Auth federation** | Shared auth server with SSO? OAuth2 token exchange? Separate auth per surface? |
+| **Conflict resolution** | Last-write-wins, operational transform, CRDT, manual resolution, server-authoritative |
+| **Offline support** | Which surfaces work offline? What data is cached locally? How are conflicts resolved on reconnect? |