What architectural pattern does this skill support?

It follows a layered approach (Data, State, Logic, View) with a heavy emphasis on Separation of Concerns and Singleton-based managers for core Unity systems.

How is hardware input handled in this architecture?

It uses Board SDK Isolation, meaning only the InputManager interacts with the Board SDK, preventing hardware-specific types from leaking into the core game logic.

Where should I store immutable game data like tile definitions?

According to this architecture, immutable data should be stored in ScriptableObjects within the Core/Data/ directory using the ZeroDayAttack.Core.Data namespace.

How do I ensure my new scripts match the project structure?

The skill provides a detailed folder map and namespace rules, such as using ZeroDayAttack.View for visual components and ZeroDayAttack.Editor for tool scripts.

Zero-Day Attack Project Architecture

Name: Zero-Day Attack Project Architecture
Author: jwmyers

byjwmyers

Game Development

Provides expert architectural guidance and codebase patterns for the Zero-Day Attack Unity project.

About

This skill equips Claude with deep structural knowledge of the Zero-Day Attack Unity codebase, enabling it to assist with system-wide design decisions. It covers critical architectural layers—Data, State, Logic, View, and Input—while enforcing best practices such as Board SDK isolation, singleton management, and ScriptableObject-driven data. Whether you are adding new features or refactoring existing logic, this skill ensures consistency with established design patterns, folder structures, and namespace conventions specific to this game environment.

Key Features

Board SDK isolation and abstraction patterns
ScriptableObject-based data management strategies
0 GitHub stars
Standardized namespace and folder organization
Singleton manager implementation for core systems
Enforcement of layered architecture (Core, View, Input, Data)

Use Cases

Implementing new game managers or view components following established patterns
Ensuring new scripts adhere to the Zero-Day Attack naming and directory conventions
Refactoring existing code to improve separation of concerns and testability

About

Key Features

Board SDK isolation and abstraction patterns
ScriptableObject-based data management strategies
0 GitHub stars
Standardized namespace and folder organization
Singleton manager implementation for core systems
Enforcement of layered architecture (Core, View, Input, Data)

Use Cases

Implementing new game managers or view components following established patterns
Ensuring new scripts adhere to the Zero-Day Attack naming and directory conventions
Refactoring existing code to improve separation of concerns and testability