Document shared Supabase pattern for web-dev agent

Added to web-dev agent rules:
- Shared Supabase project (qnatchrjlpehiijwtreh) for all Vercel apps
- Table naming convention: <projectName>_tableName
- Copy .env.local from existing projects
- Shared auth across apps
- Migration scripts with prefixed table names

Updated SPECIALIZED_AGENTS.md documentation with pattern details
This commit is contained in:
Matt Bruce 2026-02-21 19:50:59 -06:00
parent 2c41753316
commit b1d3546f70

View File

@ -69,11 +69,20 @@ openclaw agents switch ios-dev
- Error boundaries & loading states - Error boundaries & loading states
- Semantic HTML & accessibility - Semantic HTML & accessibility
- **Supabase for backend/database (preferred)** - **Supabase for backend/database (preferred)**
- **Shared Supabase pattern for all Vercel apps** (same project, prefixed tables)
- Supabase SSR auth patterns - Supabase SSR auth patterns
- Server components for data fetching - Server components for data fetching
- Proper RLS policies - Proper RLS policies
- Service role key only in API routes - Service role key only in API routes
**Shared Supabase Pattern (IMPORTANT):**
All Vercel-deployed web apps share the same Supabase project (`qnatchrjlpehiijwtreh`):
- Copy `.env.local` from existing project (blog-backup or gantt-board)
- **Table naming:** MUST use `<projectName>_tableName` format
- Examples: `blog_messages`, `mission-control_tasks`, `heartbeat-status`
- This prevents table name collisions across apps
- Auth is shared (same users table across all apps)
**Usage:** **Usage:**
```bash ```bash
# Switch to web agent # Switch to web agent