What problem does it solve?
It solves the problem of turning a single Lorcana card’s printed text into a correct, executable card definition with real Bun test coverage—without getting stuck on misleading stubs, legacy tests, or unverified engine assumptions.
Core Features & Use Cases
- Card-first end-to-end workflow: Resolve the exact card and similar references, ground ambiguous rules via lorcana-rules when needed, author the card and test, then verify with active tests.
- Engine gap validation (probe-gated): Uses a structural support probe to confirm whether missingImplementation is truly an engine/types gap versus an authoring/DSL mismatch.
- High-quality triage and guardrails: Provides a failure-mode taxonomy and strict rules about what counts as coverage (rejects empty/legacy/keyword-only tests), plus memory-backed constraints for consistent implementation.
- Bounded extensions when required: If one card needs a small engine/types addition, that work is performed within this same skill’s lifecycle rather than delegating without context.
Quick Start
Use the lorcana-cards skill to implement the specific card whose printed text you provide, then generate and run its Bun test until it passes.
