stick-crisis-check-arch

Name: stick-crisis-check-arch
Availability: InStock
Author: vmram95

Validate Unity C# class placement against DDD and Hexagonal architecture constraints.

Updated May 10, 2026

Search Tags:#csharp #architecture #unity #refactoring #ddd #hexagonal

Ready to run

npx skills add https://github.com/VMRam95/vmram-skills --skill stick-crisis-check-arch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stick-crisis-check-arch
Source: https://github.com/VMRam95/vmram-skills/tree/main/skills/stick-crisis-check-arch
Command: npx skills add https://github.com/VMRam95/vmram-skills --skill stick-crisis-check-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents architectural drift in the Stick Crisis project by ensuring that code is placed in the correct layer according to Domain-Driven Design and Hexagonal architecture principles.

Core Features & Use Cases

Layer Validation: Automatically verifies if classes are correctly categorized into domain, application, or infrastructure layers.
Unity API Guardrails: Enforces the rule that Unity-specific code must reside strictly within the infrastructure layer.
Use Case: Before committing a new feature, use this skill to ensure your new MonoBehaviour is correctly placed in the infrastructure folder and that your domain logic remains pure C#.

Quick Start

Use the stick-crisis-check-arch skill to validate the architectural placement of the newly created player controller class.

Frequently Asked Questions about stick-crisis-check-arch

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

FAQPage Schema

How do I enforce Hexagonal architecture rules in a Unity C# project?▼

Enforce Hexagonal architecture in Unity C# by validating class placement against domain and infrastructure constraints. This skill checks that Unity-specific MonoBehaviours reside in the infrastructure layer, keeping domain logic pure and separated.

How do I validate DDD layer placement for new MonoBehaviour components?▼

Validate DDD layer placement for MonoBehaviours by checking that new components are categorized correctly into domain, application, or infrastructure folders. This skill verifies naming conventions and folder structures to prevent architectural drift.

Why does my domain logic break when adding Unity API calls in C#?▼

Domain logic breaks when mixing Unity API calls because DDD requires pure C# domain layers. This skill enforces guardrails ensuring Unity-specific code stays strictly within the infrastructure layer to maintain separation of concerns.

Does this architecture validation tool require specific folder structures in Unity?▼

Architecture validation requires adherence to specific folder structures and naming conventions for MonoBehaviour components. This skill checks your Unity-based C# workflow against predefined DDD and Hexagonal architecture constraints.

What is the best way to prevent architectural drift in Domain-Driven Design projects?▼

Prevent architectural drift in Domain-Driven Design projects by validating code placement against DDD and Hexagonal architecture constraints. This skill ensures separation of concerns between domain logic and infrastructure before committing features.

When should I use a DDD and Hexagonal architecture validator for Unity development?▼

Use a DDD and Hexagonal architecture validator for Unity development before committing new features to ensure correct layer categorization. This skill checks that domain logic remains pure C# and Unity-specific code stays in infrastructure.