add-engine-effect

Add new engine effects to phase.rs across type definitions, parser, resolver, and tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gamajose/MagicTheGathering --skill add-engine-effect-gamajose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-engine-effect
Source: https://github.com/gamajose/MagicTheGathering/tree/main/.claude/skills/add-engine-effect
Command: npx skills add https://github.com/gamajose/MagicTheGathering --skill add-engine-effect-gamajose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of adding a new effect, mechanic, or parser capability to the phase.rs engine, ensuring consistency across type definitions, parsing, resolving, targeting, frontend integration, AI, and tests.

Core Features & Use Cases

  • End-to-end guidance from type definition to testing for new effects.
  • Enforces a step-by-step workflow across Phase 1–8.
  • Helps teams validate integration points (resolver, targeting, parser, and AI) for new mechanics.

Quick Start

Follow the phase.rs checklist to implement a new engine effect from type definitions through parser integration to test coverage.

Frequently Asked Questions about add-engine-effect

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

FAQPage Schema
How do I add a new engine effect to a Rust game engine?

Adding an engine effect requires updating type definitions, parsers, resolvers, targeting, and tests. This skill streamlines that multi-phase workflow to ensure full integration across the phase.rs engine from start to finish.

What steps are needed to implement a new mechanic in the phase.rs engine?

Implementing a mechanic involves following a structured checklist across phases. You progress from type definitions through parser integration to test coverage, validating resolver and AI integration points along the way.

Does this workflow cover parser and targeting integration for new game effects?

Yes, the workflow covers parser and targeting integration. It enforces a step-by-step checklist ensuring new mechanics are validated across resolvers, targeting systems, parsers, and frontend components.

How do I ensure comprehensive test coverage when adding Rust parser capabilities?

You ensure test coverage by following the structured multi-phase checklist. It enforces frontmatter presence, integration patterns, and comprehensive tests across the full lifecycle of the new effect.

Can I use this to integrate AI behavior for new mechanics in my engine?

Yes, AI integration is part of the lifecycle. The workflow guides you through updating AI components alongside resolvers and frontend to ensure new mechanics function correctly across the engine.