This skill should be used when the user asks about "game rules", "scoring", "phases", "Attack token", "Exploit token", "Ghost token", "tile placement rules", "path matching", "movement rules", "winning conditions", "turn actions", "firewall breach", "path segments", "edge nodes", or discusses Zero-Day Attack game mechanics and design.
Provides expert knowledge of Zero-Day Attack game mechanics, including rules, phases, tokens, and tile placement. Use when users ask about game rules, scoring, or discuss hacking-themed strategy game mechanics.
/plugin marketplace add jwmyers/vui-vux-plugins/plugin install zero-day-dev@vui-vuxThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Expert knowledge of Zero-Day Attack game mechanics, rules, and design for the digital implementation targeting Board hardware.
Zero-Day Attack is a two-player asymmetric tile-laying strategy game with a hacking theme. Players compete to breach firewalls, plant exploits, and escape detection.
Move Attack token toward the firewall (board edge) by placing tiles and moving along valid paths.
Goal: Reach any edge node on the board boundary.
When Attack token reaches firewall:
Move Ghost token away from the Exploit position.
First move after Exploit:
Goal: Maximize distance (path segments) between Exploit and Ghost.
Target display: 1920×1080 pixels (landscape, 16:9)
┌────────┬──────────┬────────────────────────────┬──────────┬────────┐
│Blue UI │ Blue Res │ 5×5 PLAYABLE GRID │ Red Res │ Red UI │
│ │ (5 tiles)│ Purple "Firewall" │ (5 tiles)│ │
│ │ │ Center tile pre-placed │ │ │
└────────┴──────────┴────────────────────────────┴──────────┴────────┘
← Blue player sits here Red player sits here →
By Shape:
By Color:
| Color | Hex | Who Can Traverse |
|---|---|---|
| Red | #FF2244 | Red player only |
| Blue | #44BBFF | Blue player only |
| Purple | #BB88FF | Either player |
At connecting edges:
Once placed, tiles cannot be moved, removed, or rotated.
| Token | Design | Phase | Purpose |
|---|---|---|---|
| Attack | Filled target with crosshair | Phase 1 | Navigate to firewall |
| Exploit | Hollow rings, faint crosshair | Midpoint | Mark breach permanently |
| Ghost | Gradient opacity circles | Phase 2 | Retreat from breach |
Each turn: Two Single Actions OR One Double Action
| Action | Description | Restrictions |
|---|---|---|
| Draw | Take top tile from deck | None |
| Discard | Remove tile from reserve | Only after deck empty |
| Steal | Take from opponent's reserve | Max 2/turn; opponent can steal 1 back |
| Place | Place tile at token's edge | Must connect to token position |
| Move | Move along valid paths | Color continuity rules |
If tied, player with most purple segments wins.
For detailed analysis and implementation guidance:
Important: The official rulebook describes the original physical game with a portrait orientation (Blue at top, Red at bottom). The digital Board SDK implementation uses landscape orientation (Blue on left, Red on right) to fit the 1920×1080 display. Game mechanics are identical; only the physical layout differs.
Consult DIGITIZATION-ANALYSIS.md for C# code examples of these algorithms.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.