People, pastoral hierarchy, DCC and Cell attendance, leadership development, and reporting for a G12 church organised into two homogeneous networks.
概览
People, pastoral hierarchy, DCC and Cell attendance, leadership development, and reporting for a G12 church organised into two homogeneous networks. The skeleton is in place and carries no features: authentication, the authorization guard, the first migration with the Section 5 constraints, and continuous integration. SKILL.md remains the contract everything is written against. Read SKILL.md before planning or implementing anything. Where any other instruction disagrees with it, SKILL.md wins. Commands to install, run, migrate and test are in CLAUDE.md under Running the project. Settled in SKILL.md §2. Changing it requires a recorded decision, not a pull request. - — NestJS + TypeScript, REST under /api/v1, separately deployable - — PostgreSQL 16, with hand-written SQL migrations and no ORM - — Next.
README
以下为原文 README 节选，完整内容请查看原文。
G12 Church Management System
People, pastoral hierarchy, DCC and Cell attendance, leadership development, and reporting for a G12 church organised into two homogeneous networks.
Status: Stage 1, foundations. The skeleton is in place and carries no features: authentication, the authorization guard, the first migration with the Section 5 constraints, and continuous integration. SKILL.md remains the contract everything is written against.
Start here
| Document | What it is |
|---|---|
| SKILL.md | Source of truth. Every domain rule, permission, reporting definition, and invariant. 26 sections. |
| CLAUDE.md | Project governance: review gates, definition of done, the decisions index, and what is open. |
| docs/decisions/ | The rulings themselves, one numbered file each, in the order they were made. |
| docs/ROADMAP.md | How the system gets built, in order, and how you know a stage is finished. |
Read SKILL.md before planning or implementing anything. Where any other instruction disagrees with it, SKILL.md wins.
Layout
| Path | What it is |
|---|---|
api/ |
The API. NestJS, TypeScript, PostgreSQL, served under /api/v1 |
api/migrations/ |
Hand-written SQL. The constraints of SKILL.md §5 live here |
api/test/authorization/ |
The eleven authorization cases. They fail until Stage 2, deliberately |
web/ |
The web client. Next.js, no API routes, no server actions |
docker-compose.yml |
PostgreSQL 16 for local development |
Commands to install, run, migrate and test are in CLAUDE.md under Running the project.
Stack
Settled in SKILL.md §2. Changing it requires a recorded decision, not a pull request.
- API — NestJS + TypeScript, REST under
/api/v1, separately deployable - Database — PostgreSQL 16, with hand-written SQL migrations and no ORM
- Web — Next.js + TypeScript as a pure client: no API routes, no server actions
- Styling — Tailwind CSS, with a palette that carries no judgement (§13)
- Mobile — the same web application, added to the home screen as the phone app; no App Store or Play Store app (decision 0424)
The API is the product. The web application is its one client, on laptops and on phones, used concurrently, so the API is stateless, token-authenticated, and detects write conflicts rather than resolving them silently.
The rules broken most often by accident
Each is stated in full in SKILL.md. This list is an index, not a substitute.
- Authorization is enforced by the API, never by a client — §7
- Capability and scope are separate grants, and both are checked on every request — §7
- An invariant that can be a database constraint must be a database constraint — §5
- Totals of people are distinct people, never summed attendance occurrences — §20
- History is effective-dated and never overwritten in place — §1, principle 12
推荐工具
换一个关键词，或者移除筛选条件。
安装
npx skillfish add rsedilla/dfcreportv2