rd-conventions

Enforces RedDust Unity development conventions for naming, architecture, and iterative coding.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/Sky9th/RedDust-Abandon --skill rd-conventions-sky9th
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rd-conventions
Source: https://github.com/Sky9th/RedDust-Abandon/tree/main/.claude/skills/rd-conventions
Command: npx skills add https://github.com/Sky9th/RedDust-Abandon --skill rd-conventions-sky9th

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It keeps all code written for the RedDust Unity project consistent with the team's established conventions, preventing architectural drift, null-check clutter, and oversized unreviewable commits. ## Core Features & Use Cases - Development Principles Enforcement: Applies the non-null principle, clear naming rules, task splitting, and iterative delivery to every coding task. - Architecture Guardrails: Enforces top-down data flow, single write entry points per physical domain, contract-based decoupling, and hierarchical signal forwarding in Unity systems. - Use Case: When asking the assistant to implement a new audio subsystem in the RedDust project, it will first propose a plan, use English identifiers, wire dependencies from the composition root, and deliver one small reviewable feature block at a time. ## Quick Start Ask the assistant to write or refactor any RedDust Unity code and it will automatically follow these conventions, starting with a plan before writing code.

Frequently Asked Questions about rd-conventions

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

FAQPage Schema
How do I enforce coding conventions in a Unity project with AI assistance?▼

Load a conventions skill that defines naming rules, architecture principles, and workflow constraints, then have the assistant follow it for every coding task. This skill applies RedDust conventions automatically whenever code is written, refactored, or debugged.

What architecture principles does this skill enforce for Unity?▼

It enforces top-down data flow from a composition root, single write entry points per physical domain like Transform or audio sources, contract-based decoupling via pure data Request/Response, and hierarchical signal forwarding instead of cross-layer subscriptions.

Does this skill support Chinese-language interaction?▼

Yes, the assistant addresses the user as Vito and responds in Chinese, while all code identifiers remain in English. This separates communication language from code naming conventions.

When should inheritance be used according to these conventions?▼

Inheritance is only used when structures genuinely differ. Same-structure cases with different data should use multiple instances of the same type rather than creating subclasses.

Why does the skill require planning before writing code?▼

The design-before-code principle ensures solutions are discussed and documented before implementation, reducing rework. Combined with the splitting principle, it keeps each commit small, independent, and reviewable.