source-command-implement-card

Migrate Lorcana cards into the new simulator engine using TDD.

14|5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill source-command-implement-card
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-implement-card
Source: https://github.com/TheCardGoat/lorcana-simulator/tree/main/.agents/skills/source-command-implement-card
Command: npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill source-command-implement-card

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify and implement the missing game-engine capabilities required to support a specific Lorcana card during migration, using the legacy implementation as the source of truth.

Core Features & Use Cases

  • Targeted gap identification: Pinpoints exactly which engine primitive, card-layer hook, or data model field is missing for the requested card.
  • TDD-first migration: Adds or extends card tests in the new cards package so behavior changes are verified before implementation.
  • Legacy-informed correctness: Reads both legacy and new card definitions and their tests to derive required observable behavior (including edge cases).

Quick Start

Ask the AI to run the migrated source command implement-card for a specific Lorcana card so it can migrate the card by writing a failing test, implementing the required engine gaps, and making the test pass.

Frequently Asked Questions about source-command-implement-card

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

FAQPage Schema
How do I migrate a Lorcana card to a new engine when required primitives are missing?

To migrate a Lorcana card with missing engine primitives, use a TDD-first workflow: write a failing test, analyze the gap between legacy and new code, then implement the required engine hooks and card definition to make the test pass.

What is engine gap analysis for card migration in TypeScript?

Engine gap analysis for card migration identifies missing game-engine primitives, card-layer hooks, or data model fields by comparing legacy card implementation against the new cards package to derive required observable behavior.

How do I implement missing engine hooks for a Lorcana card using test-driven development?

Implement missing engine hooks by first adding a failing card test in the new package that captures the expected behavior, then scoping implementation changes to the engine and card definition until the test passes.

Can I use legacy card code as the source of truth for migrating to a new simulator engine?

Yes, legacy card code and its tests serve as the source of truth for migration, providing the required observable behavior and edge cases needed to derive correct implementation in the new engine.

What should I do when a Lorcana card exists in the new package but engine primitives are missing?

When a card exists in the new package but lacks required engine primitives, perform targeted gap identification to pinpoint the missing primitive, then apply TDD to implement and verify the needed behavior.

Why does my migrated Lorcana card behavior differ from the legacy implementation?

Behavior differences often arise from missing engine primitives or card-layer hooks in the new package; analyzing the legacy code and tests reveals the exact gaps that must be resolved to match expected behavior.