Files
henrik.larssonandPaperclip a5a680ad46 feat: scaffold using-cash-app with OpenSpec workflow
- Next.js 14 App Router + TypeScript strict + pnpm + Tailwind
- Clerk auth middleware (routes /dashboard protected, /sign-in exposed)
- Drizzle ORM + Postgres schema: users, wallets, addresses,
  transactions, price_snapshots, categories with proper enums + FKs
- OpenSpec 1.4.1 initialized with Claude Code skills/commands
- openspec/project.md: CTO architecture decisions (BCH Q1, oracle Q2,
  auth Q6, DB/ORM, polyrepo, k8s hosting)
- openspec/config.yaml: spec-driven schema + project context
- openspec/changes/scaffold-app: first change with specs (5 ADDED
  requirements, validate --all passes)
- Multi-stage Dockerfile (deps → builder → runner, node:20-alpine)
- k8s manifests: namespace, deployment, service, ingress (infra/k8s/)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-06-27 09:35:26 +00:00

24 lines
1.0 KiB
YAML

schema: spec-driven
context: |
Repo: git.falkvinge.net/using-cash/app (polyrepo — separate from marketing site)
Framework: Next.js 14 App Router, TypeScript strict, pnpm
Auth: Clerk (@clerk/nextjs)
DB: PostgreSQL 16 + Drizzle ORM (drizzle-orm + drizzle-kit)
BCH source: Self-hosted BCHN + Fulcrum (PRO-167) — no third-party APIs
Price oracle: CoinGecko (primary) → CryptoCompare → Binance (fallback chain)
FMV: captured at block confirmation timestamp
Hosting: k8s cluster (same pattern as PRO-148)
All changes require an OpenSpec proposal in openspec/changes/<slug>/ before implementation.
Workstream context: using.cash MVP — BCH merchant accounting tool.
See openspec/project.md for full architecture decisions.
rules:
proposal:
- Reference the relevant workstream (WS1/WS2/WS3) and PRO issue number
- Include acceptance criteria with checkboxes
specs:
- Specify DB schema changes when relevant (Drizzle table definitions)
- Specify API route signatures for any new endpoints