- 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>
950 B
950 B
OpenSpec Conventions — using-cash-app
Every change to this codebase starts as an OpenSpec proposal. Code without a linked, merged proposal is not accepted.
How to propose a change
- Create
openspec/changes/<slug>/proposal.md - Describe: what changes, why, acceptance criteria, and any spec deltas to
openspec/project.mdoropenspec/capabilities/ - Run
openspec validate— must pass before review - Self-review (for solo changes) or request Engineer review
- Merge the proposal; add
.completefile to the change directory - Implement the code change referencing the proposal slug in commits
Validation gate
openspec validate is run in CI. PRs fail if validation does not pass.
Archive flow
Completed changes stay in openspec/changes/ indefinitely for audit trail. Add .complete to mark done.
Naming convention
Change slugs: <verb>-<noun> e.g. scaffold-app, add-wallet-connection, add-pl-report