AGENTS.md

1# Project Context for AI Assistants
2 
3Planet Party is a living ecosystem platform enabling bioregional communities to sense,
4decide, and act together in service to life. The Planetary Party Protocol (PPP) provides
5connective architecture for communities to coordinate, amplify efforts, and emerge as
6something larger than themselves.
7 
8## Always Apply Rules
9 
10Core project rules that apply to all tasks:
11 
12@rules/git-interaction.mdc @rules/heart-centered-ai-philosophy.mdc
13@rules/code-style-and-zen-of-python.mdc
14 
15## Tech Stack
16 
17- **Frontend**: Next.js 14+ with App Router, TypeScript, Tailwind CSS
18- **Backend**: Next.js API routes with Supabase
19- **Database**: Supabase (PostgreSQL) for data persistence
20- **Auth**: Supabase Auth with social providers
21- **Real-time**: Supabase Realtime for collaborative features
22- **Styling**: Tailwind CSS with custom design system
23- **State**: React Query (TanStack Query) for server state
24- **Testing**: Vitest + Playwright
25 
26## Project Structure
27 
28```
29src/
30├── app/                    # Next.js App Router pages
31│   ├── (public)/           # Public routes (home, about, etc.)
32│   ├── (auth)/             # Auth routes (login, signup)
33│   ├── dashboard/          # Bioregional intelligence dashboards
34│   ├── councils/           # Council management
35│   ├── guilds/             # Guild system
36│   ├── flow-funds/         # Flow fund management
37│   └── api/                # API routes
38├── components/             # Reusable UI components
39│   ├── ui/                 # Base UI components
40│   ├── dashboard/          # Dashboard-specific components
41│   └── forms/              # Form components
42├── lib/                    # Utilities and shared code
43│   ├── supabase/           # Supabase client and helpers
44│   ├── hooks/              # Custom React hooks
45│   └── utils/              # Utility functions
46├── types/                  # TypeScript type definitions
47└── styles/                 # Global styles and theme
48```
49 
50## Domain Concepts
51 
52**Bioregions**: Geographic areas defined by ecological and cultural boundaries, not
53political ones. Each bioregion has its own dashboard, councils, and flow funds.
54 
55**Guilds**: Nine specialized teams stewarding different dimensions:
561. Bioregional Intelligence - dashboards and sensing
572. Technology & Data Sovereignty - digital infrastructure
583. Ecosystem Weaving - cross-sector connections
594. Community Capacity & Trust-Building - relational work
605. Storytelling & Mythos - narrative and culture
616. Regenerative Governance - decision-making structures
627. Event Production & Cultural Activation - gatherings
638. Living Systems & Solutions - ecological regeneration
649. Regenerative Capital Flows - flow funds and economics
65 
66**Flow Funds**: Trust-based, relational capital that moves to where life needs it.
67 
68**Councils**: Community decision-making bodies at bioregional level.
69 
70**The Protocol**: SENSE → SEE → FLOW → CELEBRATE → REGENERATE
71 
72## Commands
73 
74**Development:**
75- `npm run dev` - Start development server
76- `npm run build` - Build for production
77- `npm run test` - Run tests
78- `npm run lint` - Run linter
79 
80## Code Conventions
81 
82**DO:**
83- Follow heart-centered AI philosophy in all user-facing content
84- Use TypeScript strict mode
85- Write components with accessibility in mind
86- Use Supabase Row Level Security (RLS) for data access
87- Create commits only when user explicitly requests
88- Test critical paths with integration tests
89 
90**DON'T:**
91- Use `--no-verify` flag unless explicitly requested
92- Commit changes without explicit user permission
93- Expose API keys or secrets
94- Skip error handling
95- Write overly complex components
96 
97## Design Philosophy
98 
99The platform embodies living systems principles:
100- **Decentralized** yet **Unified**
101- **Adaptive** yet **Grounded**
102- **Scalable** yet **Relational**
103- **Mythic** yet **Practical**
104- **Global** yet **Rooted**
105 
106Visual identity uses organic, flowing designs with earth tones and bioluminescent
107accents (teal, gold, deep green).
108 
109## Git Workflow
110 
111**Commit format:** `{emoji} {imperative verb} {concise description}`
112 
113Examples:
114- `✨ Add bioregional dashboard component`
115- `🐛 Fix council member invitation flow`
116- `♻️ Refactor flow fund allocation logic`
117 
118**Philosophy:** AI makes code changes but leaves version control to user. Commits are
119permanent records requiring explicit permission.
120 
121## Important Notes
122 
123- Rules with `alwaysApply: true` are critical - check frontmatter
124- Environment variables must never be committed
125- All database operations should use Supabase client
126- Real-time subscriptions need proper cleanup
127- Authentication state should be checked on protected routes
128 
129