mobile-memory

State persistence for mobile projects saves your project structure, dependencies, architecture patterns, and test coverage between sessions. Use /memory-load all to restore context and /memory-save all to store it, enabling consistent onboarding and feature planning without manual re-documentation.

Yes. Memory persistence records modules, variants, feature modules, Gradle dependencies, and tool versions alongside architecture patterns like MVI and DI modules. Query saved state with /memory-query to recall existing layouts and verify consistency when starting new features.

State persistence tracks test coverage status and failing tests over time. Save coverage snapshots with /memory-save all and retrieve them during maintenance or debugging via /memory-query and /memory-summary to catch regressions and ensure test consistency.

Load persisted memory at session start with /memory-load all to instantly recall documented patterns, DI module structure, data flows, and dependencies. This eliminates manual context reconstruction and accelerates team onboarding and new feature planning.

Yes. The persistence system is designed for Gradle-based mobile development and stores dependency versions, tool configurations, and module relationships. It maintains this metadata across sessions to support consistent builds and architecture documentation.

Use /memory-refresh on hooks to update persisted state during development cycles. This ensures your saved modules, dependencies, architecture, and test coverage reflect current project changes without manual re-entry or session restarts.