Skip to main content
SEASON 01 ・ 紅の刻 ・ THE FORGE OPENSFIRST SHORT INCOMING ・ MIRA ・ 覚醒STUDIO 伝 ・ ANIMELEGENDS.AI ・ EST. 2026v0.9.0 ・ THE GATE TREMBLES7 STAGES ・ 99 AGENTS ・ 3 NARRATORS ・ 0 COPIEDBUILT ON SIP ・ ATTESTED ・ 通信SEASON 01 ・ 紅の刻 ・ THE FORGE OPENSFIRST SHORT INCOMING ・ MIRA ・ 覚醒STUDIO 伝 ・ ANIMELEGENDS.AI ・ EST. 2026v0.9.0 ・ THE GATE TREMBLES7 STAGES ・ 99 AGENTS ・ 3 NARRATORS ・ 0 COPIEDBUILT ON SIP ・ ATTESTED ・ 通信
Open source ・ v0.1 ・ MIT

Fork the studio.Run your own.

Six skills, three MCP servers, five Remotion templates, five slash commands. Open-source. MIT with a single carve-out — mascots stay mine, everything else is yours.

  • MIT + mascot carve-out
  • Forkable, runnable, yours
  • Python MCPs ・ TypeScript Remotion
What's inside

Everything you need to run a studio.

Real file paths. Real tool names. Real commands. If you clone this repo tonight, these are the files you'll find in the morning.

6 Production Skills

skills/*/SKILL.md

One file per pipeline stage. Fork them, rewrite them, publish your own.

  • Turn a topic string or signal into a concept.json — logline, hook, payoff, mascot, archetype language.

    Input
    topic string or signal.json
    Output
    concept.json

3 MCP Servers

mcp/animelegends-*

Typed tool surfaces for signal, generation, and the Grimoire. Python, stdio transport, swappable providers.

animelegends-signal

mcp/animelegends-signal/server.py

Trend ingest and topic scoring. Feeds /from-signal.

Tools (5)

  • signal_get_trending
  • signal_score_topic
  • signal_get_hot_debates
  • signal_manual_topic
  • signal_get_release_calendar

animelegends-gen

mcp/animelegends-gen/server.py

Image, video, voice, music generation. Provider-agnostic contract.

Tools (6)

  • gen_estimate_cost
  • gen_image
  • gen_video_clip
  • gen_voice
  • gen_music
  • gen_batch_images

animelegends-grimoire

mcp/animelegends-grimoire/server.py

Dataset read/write. Every production, every metric, every hook insight.

Tools (8)

  • grimoire_log_production
  • grimoire_update_status
  • grimoire_log_metrics
  • grimoire_list_productions
  • grimoire_get_production
  • grimoire_query_performance
  • grimoire_get_hook_insights
  • grimoire_get_stats

5 Remotion Templates

remotion/src/templates/*.tsx

TypeScript + React. Functional components, frame-driven, safe-zone aware, caption-ready.

  • PowerScalingShort

    remotion/src/templates/PowerScalingShort.tsx

    AnimeLegends

    Tier-list reveals, archetype rankings, comparison callouts. 15/30/60s.

  • PhilosophyShort

    remotion/src/templates/PhilosophyShort.tsx

    Legends Mind

    Quote-led philosophy drops — large kerned text, slow camera, ambient score.

  • LoreDropShort

    remotion/src/templates/LoreDropShort.tsx

    Legends Lore

    Mascot universe worldbuilding — establishing shots, codex overlays, sigil animations.

  • TrainingArcShort

    remotion/src/templates/TrainingArcShort.tsx

    Legends Dojo

    Discipline, flow state, FrankX bridge — high-contrast cuts, reps counter, quote card.

  • LegendsLabsShort

    remotion/src/templates/LegendsLabsShort.tsx

    Legends Labs

    Build-in-public demos — terminal overlays, code snippets, before/after model tests.

5 Slash Commands

commands/*.md

Claude Code entry points. Type one command, run a full pipeline.

  • /new-shortcommands/new-short.md
    /new-short <topic> [--mascot akashi|kage|mira] [--duration 15|30|60] [--channel flagship|lore|dojo|mind|labs]

    The full pipeline: topic → concept → script → storyboard → assets → render → publish-ready.

  • /from-signalcommands/from-signal.md
    /from-signal [--channel <channel>] [--duration 15|30|60]

    Pull the highest-opportunity trending topic and run /new-short automatically.

  • /remixcommands/remix.md
    /remix <project_id> [--angle <new angle>] [--mascot <mascot>] [--duration ...]

    Variant a proven concept: new angle, new mascot, new duration. Max output, min risk.

  • /publishcommands/publish.md
    /publish <project_id|file_path> <platforms> [--schedule <ISO>]

    Distribute to TikTok, YouTube Shorts, Instagram Reels. Logs back to the Grimoire.

  • /grimoire-querycommands/grimoire-query.md
    /grimoire-query "<natural-language question>"

    Ask the dataset anything — hook performance, mascot comparisons, topic saturation.

1 Grimoire Schema

grimoire/schema.sql

Postgres + pgvector. Productions, assets, metrics, hook insights, embeddings. Seed data + query templates included.

  • productions— one row per short
  • assets— every gen, every seed
  • metrics— views, retention, CTR
  • embeddings— pgvector semantic search

3 Mascot Sheets

mascots/{akashi,kage,mira}/

Character sheets referenced by the pipeline, included for build context only. Not redistributable — this is the IP carve-out.

  • AKASHI — the cosmic narrator.
  • KAGE — the analytical strategist.
  • MIRA — the curious student.
Three tracks

Pick your path.

There's no one way to use the Forge. Clone the whole studio, plug in just the MCPs, or ship a contribution. All three are first-class.

  1. Track 01

    Clone + run

    For creators who want their own studio.

    Fork the whole repo, plug in your API keys, run your first short in an hour. Mascots stay ours — build your own, or commission some.

    1. 01git clone github.com/frankxai/AnimeLegends
    2. 02cd AnimeLegends && ./setup.sh
    3. 03/new-short "your first topic"
  2. Track 02

    Use via MCP

    For users who want the gen stack without the full pipeline.

    Install our three MCP servers in Claude Code. Get signal ingest, image/video/voice generation, and Grimoire logging as tools you can call from any conversation.

    1. 01pip install -r mcp/animelegends-gen/requirements.txt
    2. 02claude mcp add animelegends-gen ./mcp/animelegends-gen/server.py
    3. 03ask Claude to gen_image or gen_video_clip directly
  3. Track 03

    Contribute

    For builders adding skills, templates, or providers.

    Add a new Remotion template. Add a Wan 2.2 provider to gen-director. Propose a new skill for a new pipeline stage. Attribution, revenue share on commercial templates, and a Discord Keeper role.

    1. 01gh repo fork frankxai/AnimeLegends
    2. 02read CONTRIBUTING.md + CODE_OF_CONDUCT.md
    3. 03gh pr create --title 'add: <your contribution>'
Quick start

Clone. Setup. Ship a short.

Every line below is literally what you run. No boilerplate, no wrapper scripts hiding the real commands.

~/AnimeLegends · claude-code
# 1. Clone the Forge
$ git clone https://github.com/frankxai/AnimeLegends.git
Cloning into 'AnimeLegends'...
remote: Enumerating objects: 1,284, done.
Receiving objects: 100% (1,284/1,284), 4.2 MiB
✓ cloned in 3.1s
 
$ cd AnimeLegends
 
# 2. Run the setup script — installs deps, creates .venv, wires MCPs
$ ./setup.sh
→ creating .venv (python 3.11)...
→ pip install mcp[cli] httpx pydantic...
→ npm install (remotion, react, typescript)...
→ registering 3 MCP servers with Claude Code...
✓ animelegends-signal
✓ animelegends-gen
✓ animelegends-grimoire
✓ setup complete. Add API keys in .env.local.
 
# 3. Drop your API keys
$ cp .env.example .env.local && $EDITOR .env.local
# Required: ANTHROPIC_API_KEY, FAL_KEY, KLING_API_KEY, ELEVENLABS_API_KEY, SUNO_API_KEY, SUPABASE_URL, SUPABASE_KEY
 
# 4. Run your first short — the full 7-stage pipeline
$ /new-short "why the strongest characters always lose first"
[1/7] signal ─ manual topic accepted
[2/7] concept-forge ─ logline locked · mascot: akashi
[3/7] script-forge ─ 5 beats · 30s · archetype-safe ✓
[4/7] storyboard ─ 8 shots · continuity anchors set
[5/7] gen-director ─ 8 frames (flux) · 8 clips (kling) · VO + score
[6/7] remotion ─ rendered PowerScalingShort @ 1080x1920
[7/7] publish ─ awaiting your approval (no auto-post)
logged → grimoire · production: proj_20260419_strongest
✓ grimoire/assets/proj_20260419_strongest/output/final.mp4
 
$

From zero to a rendered MP4 in under 15 minutes on a modern machine (assuming API keys are ready).

Contributors

Builders wanted.

The Forge gets better when other people build on it. Here's how contribution actually works — roles, incentives, and the door.

  • Vault Keepers

    Maintainers and reviewers.

    Review incoming PRs, shepherd new templates, guard the IP carve-out. Commit access to the main repo and a permanent seat in the Keeper circle.

  • Skill Authors

    New SKILL.md, new pipeline stage.

    Design a skill that doesn't exist yet — a new stage, a new provider wrapper, a new asset type. Attribution in CHANGELOG and a co-author credit on every short that uses it.

  • Template Makers

    Remotion templates and LoRAs.

    Build a template the studio can ship on. If it becomes a commercial template, you share revenue. Every render using your template logs you as author.

How contributions are recognized

No promises we can't keep. Every accepted contribution ships with a real credit and a real reward.

  • Attribution in CHANGELOG and RELEASE_NOTES.
  • Revenue share on accepted commercial templates.
  • Discord Keeper role + direct line to maintainers.
  • First look at v0.2 skills and MCP contracts.
Roadmap

v0.1 shipped. v1.0 in sight.

Public roadmap. Dates are intent, not promise — but the direction is committed.

  1. v0.1Shipped
    Now

    The Forge opens.

    • 6 production skills (concept → publish)
    • 3 MCP servers (signal, gen, grimoire)
    • 5 Remotion templates
    • 5 slash commands
    • Grimoire Postgres + pgvector schema
  2. v0.2Next
    Week 8

    The Atlas goes public.

    • Atlas API endpoints (read-only, anonymized)
    • LoRA training helper for custom mascot styles
    • Analytics dashboard (retention, hook heatmaps)
    • Wan 2.2 provider in gen-director
  3. v0.3Planned
    Month 3

    Multi-studio forks.

    • Sub-studio template (run your own channel on the same schema)
    • Vault Keeper editorial tools (review queue, IP checks)
    • Provider marketplace inside gen-director
    • First external template accepted for revenue share
  4. v1.0Stretch
    Month 6

    Stable API. Plugin era.

    • Stable, semver-committed MCP contracts
    • Plugin architecture (skills install via one command)
    • External contributor studios live on the platform
    • Legal Keeper circle for IP + archetype review
Your turn

The studio is yours to run.

Fork it tonight. Render your first short before breakfast. The legend you build is yours — we just hand you the forge.

Open on GitHub

github.com/frankxai/AnimeLegends

Fork. Run. Publish. Contribute. Repeat.