Classifies nine zones with rules for visibility, movement, and card state transitions.
npx skills add https://github.com/kelody104/DMVault --skill rule-4-zones
Please help me install this Agent Skill. Skill: rule-4-zones Source: https://github.com/kelody104/DMVault/tree/main/skills/rule-4-zones Command: npx skills add https://github.com/kelody104/DMVault --skill rule-4-zones
This Skill provides a precise reference for the game's zones, their visibility (public vs private), and movement rules, helping players and designers resolve zone-related questions quickly and consistently.
Read the zone rules to answer a question about where a card goes when played from hand and how its visibility is updated.
High-intent search queries and answers about installing and using this skill.
Game zone movement rules state that cards transitioning between zones must update their untapped and face orientation status. This ensures that a card moved from the hand to the battle zone correctly adjusts its state to match the destination zone's requirements.
The nine zones form a comprehensive taxonomy for gameplay interactions, each with specific transition rules governing how cards move. Understanding these zone boundaries is essential for accurate rule interpretation, gameplay planning, and resolving conflicts during card interactions.
A card played from hand to the battle zone becomes public, as visibility rules dictate that hand zones are private while battle zones are public. The transition updates the card's visibility status to align with the destination zone's public state.
Resolving visibility rule conflicts during zone transitions requires checking the public or private status of both the origin and destination zones. The movement rules codify exactly how orientation and untapped status update, providing a consistent reference for gameplay planning and dispute resolution.
You need to check card orientation and untapped status during any zone movement to ensure compliance with transition rules. The rulebook specifies how face orientation considerations apply when cards move between the nine zones, maintaining consistent state tracking for gameplay.
trioskosmosDefine card orientations, zone requirements, and rotation logic for game boards.
BasarEkinciModel card game rules with zones, turn phases, and LIFO effect resolution in C#.
ilove323Synchronizes project tracker tasks and updates related metadata.
dralgorhythmGenerate Swift code scaffolds for SwiftPM, Xcode, and SwiftUI/UIKit modules.
