unikit-architecture

# Architecture — Generate Project Architecture Guidelines Generate `.unikit/ARCHITECTURE.md` with architecture decisions tailored to the game project. ## Language Awareness — BLOCKING PRE-REQUISITE **BEFORE producing ANY output**, silently read `.unikit/system/LANGUAGE_RULES.md` and apply its rules to ALL subsequent output. If the file is missing or unreadable, fall back to English. Do not produce any user-facing output until language rules are loaded. Do not announce, confirm, or mention the language setting. ## Workflow ### Step 0: Load Engine Rules Read `{{skills_dir}}/{{self_name}}/references/ENGINE_RULES.md`. This file is installed by `unikit-ai init` based on the user's engine choice and contains engine-specific paths, scan targets, framework lists, and pattern indicators. Use it for all engine-specific details in subsequent steps. If the file is missing, inform the user: "Engine rules not found. Please run `unikit-ai init` to configure your project." ### Step 1: Load Existing Context **Read `.unikit/DESCRIPTION.md`** if it exists — project specification, tech stack, constraints. This gives you the baseline understanding of what technologies are in play before scanning. **Read `.unikit/memory/code/RULES_INDEX.md`** if it exists — it contains the index of framework-specific rule files that the project already uses. This tells you which frameworks and patterns are in play. Do NOT read the individual rule files — only the index to understand what's covered. **Re...