architecture-refactor

Architecture refactoring splits large pages, components, or composables by applying boundary-aware module separation to ensure incremental and verifiable changes. You progressively execute small modifications according to domain rules.

Backend modularization is achieved by organizing module boundaries and public capabilities while synchronizing rules and documentation. It aligns rules, skills, and AGENTS.md files to maintain consistency across the architecture.

Incremental architecture refactoring works by reading AGENTS.md and rules/README.md, then executing small boundary-aware module separation steps. Each modification is verified incrementally to ensure changes remain stable and aligned.

Yes, cross-platform architecture refactoring relies on AGENTS.md and rules/README.md files. These documents define the domain rules and module boundaries required to guide verifiable, incremental changes across platforms.

Incremental refactoring for large component splits should be avoided when domain rules or boundary definitions in rules/README.md are incomplete. Without these prerequisites, verifiable small-step changes cannot be properly executed or aligned.