Duel Forge

Dual-game deck building studio for:

• MTG Command Lab
• Yu-Gi-Oh Duel Lab

Live app: duel-forge-app.vercel.app

What It Does

Duel Forge is built for players who want to generate strong lists fast, tune them manually, and print clean playtest proxies without leaving the site.

The project currently ships:

• a Commander-first Magic: The Gathering deck builder with meta-backed suggestions, power targeting, combo awareness, and print-ready proxy sheets
• a Yu-Gi-Oh builder focused on theme blending, anchored cards, popular deck-version biasing, manual seeding, and print-ready playtesting

The app is intentionally lightweight enough to deploy on Vercel while still pulling from strong free card and meta sources.

Screenshots

Launcher

MTG Command Lab

Yu-Gi-Oh Duel Lab

Feature Highlights

MTG Command Lab

• Commander-only deck building flow
• commander and color-identity discovery
• power-level targeting and deck-shape guidance
• EDHREC-backed recommendation context
• Commander Spellbook combo-pressure signals
• true-size printable proxy sheets for playtesting

Yu-Gi-Oh Duel Lab

• archetype/theme-based deck generation
• multi-anchor blending instead of single-theme overwrite
• anchored card and anchored theme controls with active/inactive toggles
• deck generation from manually added seed cards, even without anchors
• popular deck-version targeting
• manual Main / Extra / Side editing and print flow
• .ydk export

Data Sources

MTG

• Scryfall Canonical card data, oracle text, legality, and card images
• EDHREC Commander popularity, recommendation buckets, and deck-shape context
• Commander Spellbook Combo-aware pressure and Commander-specific signals
• Wizards of the Coast Official Commander format source

Yu-Gi-Oh

• YGOPRODeck Card search, archetype search, card images, and public deck/meta data

Stack

• Next.js 16
• React 19
• TypeScript
• Zustand
• Zod
• Tailwind CSS 4

Local Development

npm install
npm run dev

Useful checks:

npm run typecheck
npm run lint
npm run build

Documentation

• Architecture
• Data Sources
• Deck Generation
• Printing
• Meta Pipeline
• Types and API Contracts
• Scoring Model
• Implementation Backlog
• Phase 1 Shell Plan
• MVP Boundaries
• Acceptance Test Plan
• UI Information Architecture
• Ingestion Operations
• Risk Register
• Decision Log
• Yu-Gi-Oh Product Overview

Notes

• Deck state persists locally in the browser.
• Proxy sheets are intended for personal playtesting and iteration workflows.
• The project is organized to stay employer-friendly on GitHub, with planning docs and architecture notes kept in docs/.

License

MIT