Architecture Skill

Version: 3.0 Source: Architecture Principles + Project Structure Profiles

How to structure a project — both logically (module design, dependency flow) and physically (folder layout, naming, type-specific conventions).

The Problem

AI agents don't remember where they put things last session. Without explicit structure, each session invents its own folder layout, module boundaries, and dependency patterns — leading to scattered files, circular imports, and architectures that only make sense to the session that created them. These standards define one structure so every session builds in the same place.

Consumption

• Builders: Read ## Builder Checklist before creating files or folders. Follow the project type profile that matches your target.
• Refactorers: Use ## Enforced Rules to find structural violations. Read narrative sections for migration guidance.
• Both: Narrative sections are the authoritative standard. Checklist and rules table are compressed views of the same content.