Board/vtuber-desk
CreatorAIrotting
Content desk for VTubers
A planner that knows stream cadence, clip formats, and platform bans. Drafts titles, thumbnails briefs, and a week's shorts from one stream VOD.
For VTubers and their one overworked editor
Riff on @T_Zahil niched idea list
The problem, sharper
VTubers and their one overworked editor already tried the generic version and bounced. A planner that knows stream cadence, clip formats, and platform bans. Drafts titles, thumbnails briefs, and a week's shorts from one stream VOD. The wedge is the constraint, not another feature list.
Features that make the pitch true
- 01Capture the job in one screen: A planner that knows stream cadence, clip formats, and platform bans. Drafts titles,…
- 02Audience-aware defaults for vtubers and their one overworked editor.
- 03Shareable artifact you can send to a teammate in one tap.
- 04Honest empty states. No fake social proof, no infinite onboarding.
- 05Export: the user can leave with their data on day one.
This weekend
- Friday: landing page, one happy path, seed data.
- Saturday: the core loop that makes the pitch true.
- Sunday: share link, ugly-but-working export, tell ten people.
Stack
- — Next.js + TypeScript
- — Local-first persistence, server later
- — asset library
- — platform char limits
- — batch export
- — streaming LLM calls
User stories
- As a person in this group: VTubers and their one overworked editor, I can describe the job in one sentence and get a usable first result.
- As a skeptic, I can try it without creating an account.
- As someone who might build this, I can copy a spec and start this weekend.
Paste into Cursor, Claude Code, or Codex
Build a working product called VoltLine. Tagline: Content desk for VTubers — without the usual product theater. One-liner: A planner that knows stream cadence, clip formats, and platform bans. Drafts titles, thumbnails briefs, and a week's shorts from one stream VOD. Who it is for: VTubers and their one overworked editor Non-goals: do not build a generic creator app. Do not add auth until the core loop works. Do not invent extra personas. Must-have features: 1. Capture the job in one screen: A planner that knows stream cadence, clip formats, and platform bans. Drafts titles,… 2. Audience-aware defaults for vtubers and their one overworked editor. 3. Shareable artifact you can send to a teammate in one tap. 4. Honest empty states. No fake social proof, no infinite onboarding. 5. Export: the user can leave with their data on day one. Suggested stack: - Next.js + TypeScript - Local-first persistence, server later - asset library - platform char limits - batch export - streaming LLM calls UX: - Distinctive, editorial, not purple-gradient SaaS - Works on a phone - Empty states teach the product - One primary action per screen Ship this weekend: 1. A landing page that states the job in one breath 2. The core loop end to end with sample data 3. A shareable output 4. A README that explains what was intentionally left out Constraints: TypeScript. Keep the first version local-first if a database would slow you down. Name the product VoltLine unless you have a clearly better one.