busic-architecture

To analyze BuSic architecture, review the lib/ directory structure, identify the main source of truth, trace dependency directions, and check cross-system coupling constraints to guide change impact decisions.

The main source of truth for BuSic entry points anchors in lib/main.dart and lib/app.dart, which define the root application structure and initialization flow for architectural analysis.

Navigate BuSic's layered structure by reviewing the lib/core, lib/features, and lib/shared directories, which organize domain logic, feature modules, and shared utilities to clarify structural boundaries.

Yes, you can use this skill to verify dependency direction constraints before code reviews, as it documents unbreakable UI layering rules and cross-system coupling limits to align team decisions.

Your BuSic architecture change breaks cross-system coupling rules if it violates documented dependency ordering or UI hierarchy principles, bypassing the established lib/ structure and layer interaction constraints.

Yes, the BuSic architecture skill supports localization and documentation references by including lib/l10n and docs in its structural overview, anchoring decisions in repository references and SKILL.md frontmatter metadata.