lorcana-cards

Author Disney Lorcana card definitions and executable Bun tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates incorrect or incomplete Disney Lorcana card implementations by guiding you through implementing a specific card’s DSL, aligning with rules constraints, and proving behavior with executable tests.

Core Features & Use Cases

  • Single-card lifecycle ownership: author the card definition, add/activate the card test, and make bounded engine/types extensions when the printed text requires new support.
  • Rules-grounded implementation: use Mode B behavior constraints from the rules skill when timing, replacement, alternate costs, or multiplayer interactions are non-trivial.
  • Engine support probing: use a structural support probe to determine whether the referenced effect/condition/target/trigger surfaces are registered before declaring an engine gap.
  • Triage-quality guardrails: avoid false-green signals like empty tests, legacy commented implementations, or tests that only validate missing flags.

Quick Start

Ask the AI to implement the Lorcana card from its printed text and produce an executable Bun test that passes for that card.

Frequently Asked Questions about lorcana-cards

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

FAQPage Schema
How do I implement Disney Lorcana card behavior with executable tests?

Implement Disney Lorcana card behavior by authoring card definitions and executable Bun tests from printed text, extending lorcana-engine and lorcana-types only when a single card requires bounded new support. You get correct, validated card logic.

What is the best way to model triggers and conditions for a Lorcana card implementation?

Model Lorcana triggers and conditions by grounding implementation in Mode B behavior constraints from the rules skill, then authoring the card DSL from printed text. This produces rules-aligned trigger and condition logic.

How do I check if the lorcana-engine supports a specific effect before writing card DSL?

Check lorcana-engine support by running a structural support probe to determine whether referenced effect, condition, target, or trigger surfaces are registered. This classifies true engine gaps before you author card definitions.

Why do my Lorcana card tests pass when the card behavior is still incorrect?

Lorcana card tests give false-green signals when tests are empty, implementations are legacy commented code, or tests only validate missing flags. Triage-quality guardrails prevent these false passes during card implementation.

Can I migrate a stubbed Lorcana card to a full implementation using this workflow?

Migrate stubbed Lorcana cards by following the resolve, ground, probe, author, test, and verify workflow to implement the card DSL from printed text. You get a complete implementation validated by the current Bun test harness.

When should I extend lorcana-types and lorcana-engine for a single card implementation?

Extend lorcana-types and lorcana-engine only when a single Lorcana card requires bounded new support that printed text demands. Structural probing first confirms the engine gap exists before you add extensions.