Two files, one repository
Light-Brands/planetary-party-html ships 3 formats across 17 indexed files. The question worth asking is whether the second one says anything the first does not.
| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 10 | 4 | 0% |
| Commands | 0 | 4 | 0 | 0% |
| Section tags | 1 | 7 | 1 | 11% |
What each file covers
Sections
0 shared · 10 only in A · 4 only in B- − Project Context for AI Assistants
- − Always Apply Rules
- − Tech Stack
- − Project Structure
- − Domain Concepts
- − Commands
- − Code Conventions
- − Design Philosophy
- − Git Workflow
- − Important Notes
- + Creating Claude Code Skills
- + Valid Frontmatter Format
- + Writing Concise Descriptions
- + Example Skill
Commands
0 shared · 4 only in A · 0 only in B- − npm run dev
- − npm run build
- − npm run test
- − npm run lint
Section tags
1 shared · 7 only in A · 1 only in B- − build
- − test
- − code-style
- − architecture
- − types
- − git-pr
- − do-not
- + lint-format
- agent-behaviour
Line diff
Light-Brands/planetary-party-html · AGENTS.md
@@ −1 @@
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
Light-Brands/planetary-party-html · .claude/skills/CLAUDE.md
@@ +1 @@
1# Creating Claude Code Skills
2
3When creating custom skill files in `.claude/skills/`, the YAML frontmatter format
4matters.
5
6## Valid Frontmatter Format
7
8```yaml
9---
10name: skill-name
11description: "Keep under 75 characters"
12---
13```
14
15**Critical constraints:**
16
17- **Single line only** - Claude Code doesn't parse block scalars (`>` or `|`) correctly
18- **Under 75 characters** - With `description: ` prefix (13 chars), total line must be
19 under 88 to prevent prettier wrapping
20- **Use quotes** - Always quote descriptions to handle special characters like colons
21
22**Valid formats:**
23
24- `description: "Double quoted under 75 chars"` (recommended)
25- `description: 'Single quoted under 75 chars'`
26- `description: Plain text under 75 chars` (only if no special characters)
27
28## Writing Concise Descriptions
29
30Keep descriptions focused on WHEN to use the skill:
31
32- Good: "Use when rough ideas need design before code"
33- Too long: "Use when developing rough ideas into designs before writing code. Refines
34 concepts through collaborative questioning..."
35
36If you need to cut content to stay under 75 chars, move that detail into the skill body
37instead.
38
39## Example Skill
40
41```yaml
42---
43name: systematic-debugging
44description: "Use for bugs, test failures, or unexpected behavior needing root cause"
45---
46
47<objective>
48Find the root cause before writing fixes. Understanding why something breaks leads to
49correct fixes. Guessing wastes time and creates new problems.
50
51Core principle: If you can't explain WHY it's broken, you're not ready to fix it.
52</objective>
53
54[Rest of skill content...]
55```
56
@@ −1 +1 @@
1−# Project Context for AI Assistants
1+# Creating Claude Code Skills
22
3−Planet Party is a living ecosystem platform enabling bioregional communities to sense,
4−decide, and act together in service to life. The Planetary Party Protocol (PPP) provides
5−connective architecture for communities to coordinate, amplify efforts, and emerge as
6−something larger than themselves.
3+When creating custom skill files in `.claude/skills/`, the YAML frontmatter format
4+matters.
75
8−## Always Apply Rules
6+## Valid Frontmatter Format
97
10−Core 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−
8+```yaml
9+---
10+name: skill-name
11+description: "Keep under 75 characters"
12+---
2813 ```
29−src/
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−```
4914
50−## Domain Concepts
15+**Critical constraints:**
5116
52−**Bioregions**: Geographic areas defined by ecological and cultural boundaries, not
53−political ones. Each bioregion has its own dashboard, councils, and flow funds.
17+- **Single line only** - Claude Code doesn't parse block scalars (`>` or `|`) correctly
18+- **Under 75 characters** - With `description: ` prefix (13 chars), total line must be
19+ under 88 to prevent prettier wrapping
20+- **Use quotes** - Always quote descriptions to handle special characters like colons
5421
55−**Guilds**: Nine specialized teams stewarding different dimensions:
56−1. Bioregional Intelligence - dashboards and sensing
57−2. Technology & Data Sovereignty - digital infrastructure
58−3. Ecosystem Weaving - cross-sector connections
59−4. Community Capacity & Trust-Building - relational work
60−5. Storytelling & Mythos - narrative and culture
61−6. Regenerative Governance - decision-making structures
62−7. Event Production & Cultural Activation - gatherings
63−8. Living Systems & Solutions - ecological regeneration
64−9. Regenerative Capital Flows - flow funds and economics
22+**Valid formats:**
6523
66−**Flow Funds**: Trust-based, relational capital that moves to where life needs it.
24+- `description: "Double quoted under 75 chars"` (recommended)
25+- `description: 'Single quoted under 75 chars'`
26+- `description: Plain text under 75 chars` (only if no special characters)
6727
68−**Councils**: Community decision-making bodies at bioregional level.
28+## Writing Concise Descriptions
6929
70−**The Protocol**: SENSE → SEE → FLOW → CELEBRATE → REGENERATE
30+Keep descriptions focused on WHEN to use the skill:
7131
72−## Commands
32+- Good: "Use when rough ideas need design before code"
33+- Too long: "Use when developing rough ideas into designs before writing code. Refines
34+ concepts through collaborative questioning..."
7335
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
36+If you need to cut content to stay under 75 chars, move that detail into the skill body
37+instead.
7938
80−## Code Conventions
39+## Example Skill
8140
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
41+```yaml
42+---
43+name: systematic-debugging
44+description: "Use for bugs, test failures, or unexpected behavior needing root cause"
45+---
8946
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
47+<objective>
48+Find the root cause before writing fixes. Understanding why something breaks leads to
49+correct fixes. Guessing wastes time and creates new problems.
9650
97−## Design Philosophy
51+Core principle: If you can't explain WHY it's broken, you're not ready to fix it.
52+</objective>
9853
99−The 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−
106−Visual identity uses organic, flowing designs with earth tones and bioluminescent
107−accents (teal, gold, deep green).
108−
109−## Git Workflow
110−
111−**Commit format:** `{emoji} {imperative verb} {concise description}`
112−
113−Examples:
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
119−permanent 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−
54+[Rest of skill content...]
55+```
12956
