Prompt file imported from SystemVirtue/obie-march-26 (.windsurf/workflows/custom-agent-instructions.md). Copyright stays with the author.

Custom Agent Instructions for OBIE v5

Name: custom-agent-instructions
Author: SystemVirtue

Project Overview

OBIE v5 is a server-first real-time jukebox application built with Supabase. It consists of three main web applications:

Admin: Management interface for the jukebox system
Player: Music playback interface for users
Kiosk: Public-facing interface for song selection

Architecture

Backend: Supabase (PostgreSQL database, real-time subscriptions, auth, storage)
Frontend: Three separate web applications (likely React/Next.js based on workspace structure)
Real-time: Uses Supabase real-time features for live updates
Authentication: Supabase Auth
Database: PostgreSQL via Supabase

Development Workflow

Install dependencies: npm install
Start all dev servers: npm run dev (runs admin, player, kiosk concurrently)
Start individual servers:
- Admin: npm run dev:admin
- Player: npm run dev:player
- Kiosk: npm run dev:kiosk
Supabase commands:
- Start: npm run supabase:start
- Stop: npm run supabase:stop
- Reset: npm run supabase:reset

Key Considerations

This is a monorepo with workspaces
All three apps share the same Supabase backend
Real-time functionality is critical for the jukebox experience
Database schema changes require migrations via Supabase
Edge functions can be deployed with npm run supabase:deploy

Common Tasks

Adding new features to any of the three interfaces
Managing Supabase database schema and migrations
Implementing real-time updates between apps
Deploying edge functions
Managing authentication and permissions

File Structure

obie-v5/
├── package.json (root workspace)
├── web/
│   ├── admin/
│   ├── player/
│   └── kiosk/
├── supabase/
└── .windsurf/workflows/

Development Notes

Use concurrently for running multiple dev servers
Each web app has its own package.json and dependencies
Supabase configuration is shared across all apps
Real-time subscriptions should be handled carefully to avoid memory leaks

# Custom Agent Instructions for OBIE v5 ## Project Overview OBIE v5 is a server-first real-time jukebox application built with Supabase. It consists of three main web applications: - **Admin**: Management interface for the jukebox system - **Player**: Music playback interface for users - **Kiosk**: Public-facing interface for song selection ## Architecture - **Backend**: Supabase (PostgreSQL database, real-time subscriptions, auth, storage) - **Frontend**: Three separate web applications (likely React/Next.js based on workspace structure) - **Real-time**: Uses Supabase real-time features for live updates - **Authentication**: Supabase Auth - **Database**: PostgreSQL via Supabase ## Development Workflow 1. Install dependencies: `npm install` 2. Start all dev servers: `npm run dev` (runs admin, player, kiosk concurrently) 3. Start individual servers: - Admin: `npm run dev:admin` - Player: `npm run dev:player` - Kiosk: `npm run dev:kiosk` 4. Supabase commands: - Start: `npm run supabase:start` - Stop: `npm run supabase:stop` - Reset: `npm run supabase:reset` ## Key Considerations - This is a monorepo with workspaces - All three apps share the same Supabase backend - Real-time functionality is critical for the jukebox experience - Database schema changes require migrations via Supabase - Edge functions can be deployed with `npm run supabase:deploy` ## Common Tasks - Adding new features to any of the three interfaces - Managing Supabase database schema and migrations - Implementing real-time updates between apps - Deploying edge functions - Managing authentication and permissions ## File Structure ``` obie-v5/ ├── package.json (root workspace) ├── web/ │ ├── admin/ │ ├── player/ │ └── kiosk/ ├── supabase/ └── .windsurf/workflows/ ``` ## Development Notes - Use concurrently for running multiple dev servers - Each web app has its own package.json and dependencies - Supabase configuration is shared across all apps - Real-time subscriptions should be handled carefully to avoid memory leaks

{ "prompt": "# Custom Agent Instructions for OBIE v5\n\n## Project Overview\nOBIE v5 is a server-first real-time jukebox application built with Supabase. It consists of three main web applications:\n\n- **Admin**: Management interface for the jukebox system\n- **Player**: Music playback interface for users\n- **Kiosk**: Public-facing interface for song selection\n\n## Architecture\n- **Backend**: Supabase (PostgreSQL database, real-time subscriptions, auth, storage)\n- **Frontend**: Three separate web applications (likely React/Next.js based on workspace structure)\n- **Real-time**: Uses Supabase real-time features for live updates\n- **Authentication**: Supabase Auth\n- **Database**: PostgreSQL via Supabase\n\n## Development Workflow\n1. Install dependencies: `npm install`\n2. Start all dev servers: `npm run dev` (runs admin, player, kiosk concurrently)\n3. Start individual servers:\n - Admin: `npm run dev:admin`\n - Player: `npm run dev:player`\n - Kiosk: `npm run dev:kiosk`\n4. Supabase commands:\n - Start: `npm run supabase:start`\n - Stop: `npm run supabase:stop`\n - Reset: `npm run supabase:reset`\n\n## Key Considerations\n- This is a monorepo with workspaces\n- All three apps share the same Supabase backend\n- Real-time functionality is critical for the jukebox experience\n- Database schema changes require migrations via Supabase\n- Edge functions can be deployed with `npm run supabase:deploy`\n\n## Common Tasks\n- Adding new features to any of the three interfaces\n- Managing Supabase database schema and migrations\n- Implementing real-time updates between apps\n- Deploying edge functions\n- Managing authentication and permissions\n\n## File Structure\n```\nobie-v5/\n├── package.json (root workspace)\n├── web/\n│ ├── admin/\n│ ├── player/\n│ └── kiosk/\n├── supabase/\n└── .windsurf/workflows/\n```\n\n## Development Notes\n- Use concurrently for running multiple dev servers\n- Each web app has its own package.json and dependencies\n- Supabase configuration is shared across all apps\n- Real-time subscriptions should be handled carefully to avoid memory leaks", "variables": [], "notes": "Generate custom agent instructions for the obie-v5 project", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/SystemVirtue/obie-march-26", "path": ".windsurf/workflows/custom-agent-instructions.md", "ref": "4f17efa01fdd9be5878f3ce791c0f031d8345cc6", "url": "https://github.com/SystemVirtue/obie-march-26/blob/4f17efa01fdd9be5878f3ce791c0f031d8345cc6/.windsurf/workflows/custom-agent-instructions.md", "key": "SystemVirtue/obie-march-26/.windsurf/workflows/custom-agent-instructions.md" } } }

custom-agent-instructions

About

Custom Agent Instructions for OBIE v5

Project Overview

Architecture

Development Workflow

Key Considerations

Common Tasks

File Structure

Development Notes

Use it

Manifest

Reviews