Business requirements, user stories, data model, and workflows for each feature area.
| Document | Description |
|---|---|
| Authentication | Google OAuth, user accounts, role assignments |
| Profiles | Personal information, burner names, location, profile pictures |
| Asociado Applications | Tier application workflow and Board voting |
| Legal Documents & Consent | GDPR compliance, document versioning, consent tracking |
| Volunteer Status | Volunteer approval, status computation |
| Teams | Self-organizing teams, system teams, join requests, role slots |
| Google Integration | Drive provisioning, Groups via Cloud Identity, sync modes |
| Background Jobs | Automated sync, reminders, compliance enforcement |
| Administration | Admin dashboard, human management, configuration |
| Contact Fields | Granular contact visibility, E.164 phone validation |
| Preferred Email | System notification email preferences |
| Audit Log | Comprehensive audit trail for admin and automated actions |
| Drive Activity Monitoring | Google Drive permission change tracking |
| Profile Pictures & Birthdays | Avatar uploads, birthday calendar |
| Membership Tiers | Volunteer / Colaborador / Asociado tier system |
| Onboarding Pipeline | Signup → consent → review → approval flow |
| Coordinator Roles | Consent and Volunteer Coordinator workflows |
| Board Voting | Board voting on tier applications |
| Camps | Event camp registration, approval, co-leads, public API |
| Email Outbox | Outbox-based email delivery with retry and crash recovery |
| Campaigns | Campaign system with CSV import and discount codes |
| Membership Status | 6-bucket membership partition model |
| Ticket Vendor Integration | TicketTailor sync, sales dashboard, attendee matching |
| Shift Management | Shift browsing, signup workflows, urgency scoring, coordinator tooling |
| Shift Signup Visibility | Visibility rules for volunteer and admin shift views |
| Feedback System | Feedback reports, triage workflow, GitHub issue integration |
| Communication Preferences | Member communication channel and frequency preferences |
| Contact Accounts | External contact records and account linking |
| Magic Link Auth | Passwordless email-based login and signup |
| Budget | Seasonal budget planning, visibility, and approvals |
| Workspace Account Provisioning | @nobodies.team account provisioning and linking |
| Document | Description |
|---|---|
| Admin Role Setup | Adding initial admin users via SQL |
| GUID Reservations | Reserved deterministic GUID blocks for seeded data |
| Seed Data Strategy | When to use HasData, migration backfills, and dev-only runtime seeders |
| Google & External Service Setup | OAuth, service account, Maps, GitHub credentials |
| Document | Description |
|---|---|
| Development Statistics | Historical codebase growth, file counts, and commit cadence |
Design specs and implementation plans preserved for historical context. These document the thinking behind major features at the time they were built.
| Directory | Contents |
|---|---|
| plans/ | Early design and implementation plans (semantic versioning, Google Groups) |
| superpowers/specs/ | Feature design specifications |
| superpowers/plans/ | Feature implementation plans |
Clean Architecture with four layers:
Web Controllers, Views, ViewModels
Application Interfaces, DTOs, Use Cases
Infrastructure EF Core, Services, Jobs
Domain Entities, Enums, Value Objects
Primary macro-level guidance lives in architecture.md.
See the root CLAUDE.md for build commands, coding rules, and project conventions.