Vibe Director Studio

Vibe Director Studio is an AI storytelling and animation workflow for directing short, emotionally clear scenes with reusable characters, narration, music, sound effects, continuity memory, and human review.

The product goal is simple: users should feel like they are directing a story, not operating raw generation models.

What This Repo Contains

• dashboard/: React + Express studio for stories, scenes, characters, workspaces, jobs, and generation settings.
• scripts/: Story, image, animation, narration, music, sound effect, composition, timeline, and upload pipeline scripts.
• assets/: Local placeholder media used by the generation and rendering pipeline.
• output/: Generated stories, scene images, animations, audio, timelines, and manifests.

Local Setup

npm install
cd dashboard
npm install
cp .env.example .env
npm run db:generate
npm run db:migrate -- --name init
npm run db:seed
npm start

The dashboard runs at http://localhost:3456 and the API server runs at http://localhost:3458.

Database

Local development uses PostgreSQL through docker-compose.yml.

docker compose up -d postgres

Default local connection:

postgresql://vibedirectorstudio:vibe_director_studio_dev_password@localhost:5432/vibedirectorstudio?schema=public

If you have an older local legacy Postgres volume, leave it as a backup or export/import the data into the new vibe_director_studio_postgres_data volume.

Common Commands

npm run dashboard
npm run generate-story
npm run generate-narration
npm run generate-music
npm run generate-sfx
npm run render-compositions
npm run assemble-video

From dashboard/:

npm run dev
npm run server
npm run build
npm run db:seed

Product Direction

Vibe Director Studio prioritizes continuity, narration, music/sound, scene review, progressive rendering, character bibles, timeline editing, and cinematic tooling. The platform should stay focused on stylized, coherent-enough, emotionally compelling storytelling rather than photorealistic model demos.

Progress Documentation

Implementation progress is tracked in docs/progress.md. Update it after meaningful product, UI, workflow, or architecture changes. Roadmap status and next steps live in docs/completed/VIBE_DIRECTOR_STUDIO_ROADMAP.md unless a newer active roadmap file exists, and should be updated when the implementation changes roadmap state.