1294caa7fa
Complete rebuild of 22-year-old PHP CMS as modern SaaS: Database (15 migrations, 42+ tables): - Foundation: account_settings, audit_log, GDPR register, cms_files - Module Engine: modules, fields, records, permissions, relations + RPC - Members: 45+ field member profiles, departments, roles, honors, SEPA mandates - Courses: courses, sessions, categories, instructors, locations, attendance - Bookings: rooms, guests, bookings with availability - Events: events, registrations, holiday passes - Finance: SEPA batches/items (pain.008/001 XML), invoices - Newsletter: campaigns, templates, recipients, subscriptions - Site Builder: site_pages (Puck JSON), site_settings, cms_posts - Portal Auth: member_portal_invitations, user linking Feature Packages (9): - @kit/module-builder — dynamic low-code CRUD engine - @kit/member-management — 31 API methods, 21 actions, 8 components - @kit/course-management, @kit/booking-management, @kit/event-management - @kit/finance — SEPA XML generator + IBAN validator - @kit/newsletter — campaigns + dispatch - @kit/document-generator — PDF/Excel/Word - @kit/site-builder — Puck visual editor, 15 blocks, public rendering Pages (60+): - Dashboard with real stats from all APIs - Full CRUD for all 8 domains with react-hook-form + Zod - Recharts statistics - German i18n throughout - Member portal with auth + invitation system - Public club websites via Puck at /club/[slug] Infrastructure: - Dockerfile (multi-stage, standalone output) - docker-compose.yml (Supabase self-hosted + Next.js) - Kong API gateway config - .env.production.example
79 lines
3.0 KiB
Markdown
79 lines
3.0 KiB
Markdown
---
|
|
name: gitnexus-exploring
|
|
description: "Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\""
|
|
---
|
|
|
|
# Exploring Codebases with GitNexus
|
|
|
|
## When to Use
|
|
|
|
- "How does authentication work?"
|
|
- "What's the project structure?"
|
|
- "Show me the main components"
|
|
- "Where is the database logic?"
|
|
- Understanding code you haven't seen before
|
|
|
|
## Workflow
|
|
|
|
```
|
|
1. READ gitnexus://repos → Discover indexed repos
|
|
2. READ gitnexus://repo/{name}/context → Codebase overview, check staleness
|
|
3. gitnexus_query({query: "<what you want to understand>"}) → Find related execution flows
|
|
4. gitnexus_context({name: "<symbol>"}) → Deep dive on specific symbol
|
|
5. READ gitnexus://repo/{name}/process/{name} → Trace full execution flow
|
|
```
|
|
|
|
> If step 2 says "Index is stale" → run `npx gitnexus analyze` in terminal.
|
|
|
|
## Checklist
|
|
|
|
```
|
|
- [ ] READ gitnexus://repo/{name}/context
|
|
- [ ] gitnexus_query for the concept you want to understand
|
|
- [ ] Review returned processes (execution flows)
|
|
- [ ] gitnexus_context on key symbols for callers/callees
|
|
- [ ] READ process resource for full execution traces
|
|
- [ ] Read source files for implementation details
|
|
```
|
|
|
|
## Resources
|
|
|
|
| Resource | What you get |
|
|
| --------------------------------------- | ------------------------------------------------------- |
|
|
| `gitnexus://repo/{name}/context` | Stats, staleness warning (~150 tokens) |
|
|
| `gitnexus://repo/{name}/clusters` | All functional areas with cohesion scores (~300 tokens) |
|
|
| `gitnexus://repo/{name}/cluster/{name}` | Area members with file paths (~500 tokens) |
|
|
| `gitnexus://repo/{name}/process/{name}` | Step-by-step execution trace (~200 tokens) |
|
|
|
|
## Tools
|
|
|
|
**gitnexus_query** — find execution flows related to a concept:
|
|
|
|
```
|
|
gitnexus_query({query: "payment processing"})
|
|
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
|
|
→ Symbols grouped by flow with file locations
|
|
```
|
|
|
|
**gitnexus_context** — 360-degree view of a symbol:
|
|
|
|
```
|
|
gitnexus_context({name: "validateUser"})
|
|
→ Incoming calls: loginHandler, apiMiddleware
|
|
→ Outgoing calls: checkToken, getUserById
|
|
→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
|
|
```
|
|
|
|
## Example: "How does payment processing work?"
|
|
|
|
```
|
|
1. READ gitnexus://repo/my-app/context → 918 symbols, 45 processes
|
|
2. gitnexus_query({query: "payment processing"})
|
|
→ CheckoutFlow: processPayment → validateCard → chargeStripe
|
|
→ RefundFlow: initiateRefund → calculateRefund → processRefund
|
|
3. gitnexus_context({name: "processPayment"})
|
|
→ Incoming: checkoutHandler, webhookHandler
|
|
→ Outgoing: validateCard, chargeStripe, saveTransaction
|
|
4. Read src/payments/processor.ts for implementation details
|
|
```
|