add-card-data-pipeline

Modify MTGJSON export, Oracle parsing, and synthesis pipeline components.

212|148|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/phase-rs/phase --skill add-card-data-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-card-data-pipeline
Source: https://github.com/phase-rs/phase/tree/main/.claude/skills/add-card-data-pipeline
Command: npx skills add https://github.com/phase-rs/phase --skill add-card-data-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when modifying the card data pipeline — adding new fields to card exports, changing Oracle parser output shape, updating card database loading, modifying the coverage report, adding synthesis functions, or debugging why a card's data looks wrong at runtime.

Core Features & Use Cases

  • Define and propagate changes to card export fields, including shape and typings.
  • Update MTGJSON loading, Oracle parsing, and synthesis function pipeline to keep engine data consistent.
  • Debug and validate data transformations to ensure CR-correctness and compatibility across front-end and server.

Quick Start

Run the data pipeline update workflow to add a new field to card exports and regenerate card-data.json.

Frequently Asked Questions about add-card-data-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new field to MTGJSON card exports and regenerate card data?

To add new card export fields, you modify the MTGJSON export components, Oracle parsing logic, and synthesis functions, then update types and tests to regenerate card-data.json with CR correctness.

How do I update the Oracle parser output shape for MTG card data?

Updating the Oracle parser output shape requires modifying the parser components and propagating those structural changes through synthesis functions and coverage reports to maintain type safety and backward compatibility.

Why does my MTG card data look wrong at runtime after a pipeline change?

Runtime card data errors often stem from unpropagated changes across MTGJSON loading, Oracle parsing, or synthesis functions, requiring you to validate data transformations and ensure CR-correctness across front-end and server.

What's the best way to maintain backward compatibility when changing card database loading paths?

Maintaining backward compatibility during card database loading updates requires updating types, tests, and documentation simultaneously while ensuring the MTGJSON export and synthesis pipeline remains CR-correct.

Can I use this pipeline to debug data transformations between MTGJSON and Oracle parsing?

Yes, the pipeline supports debugging and validating data transformations between MTGJSON loading, Oracle parsing, and synthesis functions to ensure CR-correctness and compatibility across front-end and server environments.

Do I need to update tests when adding synthesis functions to the card data pipeline?

Yes, adding synthesis functions requires updating tests and data regeneration to ensure type safety, CR correctness, and backward compatibility across the updated MTGJSON export and Oracle parsing pipeline.