source-command-implement-card

Migrate Lorcana card implementations by writing failing Bun tests first.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When a user requests the migrated Lorcana source command to implement a specific card, this Skill helps you correctly identify what the new engine is missing and implement the required behavior without guessing.

Core Features & Use Cases

  • Legacy-informed migration: Uses legacy card and legacy test behavior as the reference truth before changing the new engine.
  • Gap analysis to unblock implementation: Compares required card mechanics against what the new engine already supports to pinpoint the exact missing primitive or hook.
  • TDD workflow with gameplay assertions: Writes a failing test first, then implements only the minimal engine and card changes needed to make the test pass.
  • Migration-safe execution: Avoids engine-to-cards imports in engine tests and focuses changes narrowly on engine files, card definitions, and tests.

Quick Start

Run the implement-card migration for a specific Lorcana card name by telling the agent to use legacy behavior to identify the new engine gaps and produce a failing-then-passing test-driven implementation.

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 card behavior when the new engine is missing required mechanics?▼

Migrate card behavior by performing a legacy-vs-new gap analysis to locate missing mechanics, writing a failing test asserting observable gameplay, then implementing minimal engine changes to pass Bun tests.

What is the best way to implement missing card mechanics using test-driven development?▼

Test-driven development for card implementation requires writing a failing Bun test first that asserts observable gameplay behavior, then adding only the minimal engine and card definition changes needed to make it pass.

How does legacy-informed gap analysis work for engine migration?▼

Legacy-informed gap analysis compares required card mechanics and triggers from legacy implementations against the new engine's current support to pinpoint exact missing primitives or hooks before writing code.

Can I use Bun testing to verify migrated card triggers and edge cases?▼

Bun testing verifies migrated card triggers and edge cases by running gameplay assertions that must fail initially, ensuring only minimal engine and card changes are implemented to achieve a passing state.

What are the type safety constraints when implementing engine and card changes?▼

Type safety constraints prohibit unsafe imports and engine-to-cards imports in engine tests, requiring changes to focus narrowly on engine files, card definitions, and test files without type violations.

When should I not use the legacy card behavior as the reference truth for migration?▼

Legacy card behavior should not serve as the reference truth when a requested card's mechanics, triggers, tests, or edge cases are already fully supported in the migrated card and runtime pipeline.