unikit-architecture

To generate architecture guidelines, the Skill scans your project structure to detect the tech stack and applies engine-specific rules to produce an ARCHITECTURE.md with folder structure, dependency rules, and communication patterns.

Documenting module boundaries involves mapping discovered project architecture to a standard template, defining cross-module communication patterns, and outputting reference notes to record dependency rules and architecture decisions.

You can audit an existing project by scanning the repository structure to identify the real tech stack, applying engine rules, and generating an Architecture.md that maps module boundaries and dependencies for review.

Yes, it supports any game engine as long as engine-specific rules are defined in the references file, allowing it to detect modules and generate tailored architecture decisions and communication patterns.

An architecture doc generated from repository structure records real architecture decisions, maps actual folder structures and dependencies, and guides project setup and audits for onboarding and review.

The limitations rely on the accuracy of the repository scan and the predefined engine rules, meaning architecture decisions and cross-module communication patterns are only generated for detected engines and modules.