improve-card-generator

Diagnose and repair Lorcana card parsing and generation gaps in lorcana-cards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill fixes missing parsing and generation coverage in the Lorcana card library so previously unparseable or stubbed card implementations can be accurately generated and handled.

Core Features & Use Cases

  • Parser/Generator Diagnosis: Identifies gaps such as missing implementations, mismatched manual overrides, and unparseable ability text patterns in packages/lorcana/lorcana-cards.
  • Minimal, Pattern-Focused Fixes: Applies the smallest viable changes in parser/generator code (often in parser v2 and manual-overrides) to unblock specific cards without introducing unrelated gameplay behavior changes.
  • Verification-First Workflow: Runs type checks and tests before handoff, then reports the root cause and the set of unblocked cards to the lorcana-cards layer.

Quick Start

Use the improve-card-generator skill to diagnose why a specific Lorcana card ability text cannot be parsed, apply a minimal parser/generator fix in lorcana-cards, and validate the result with check-types and tests.

Frequently Asked Questions about improve-card-generator

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

FAQPage Schema
How do I fix Lorcana card parser failures when ability text cannot be parsed?

Fix Lorcana card parser failures by diagnosing missing parsing coverage or generation stubs in lorcana-cards, applying minimal code changes to the parser or manual overrides, and verifying the result with type checks and tests.

Why does my Lorcana card generation produce a stub instead of the correct ability implementation?

Lorcana card generation produces stubs when manual-override coverage mismatches or unsupported ability-text patterns block the parser, requiring targeted generator code fixes to unblock specific cards.

How do I diagnose unparseable ability text patterns in a TypeScript card library?

Diagnose unparseable ability text patterns by running repository diagnostics and reproducing parser failures with minimal input to identify missing implementations in the lorcana-cards package.

What is the best way to unblock Lorcana cards without changing unrelated gameplay behavior?

The best way to unblock Lorcana cards is applying minimal, pattern-focused fixes to parser v2 and manual overrides, ensuring no unrelated gameplay behavior changes are introduced.

Do I need to run TypeScript type checks after modifying Lorcana card manual overrides?

Yes, you need to run TypeScript type checks after modifying manual overrides to verify that parser and generator code changes correctly unblock targeted Lorcana cards.

Can I use manual overrides to fix mismatched Lorcana card parsing coverage?

You can use manual overrides to fix mismatched Lorcana card parsing coverage by applying minimal code changes to handle unsupported ability-text patterns and generation stubs.