mobile-memory

Persist mobile project context across sessions with /memory- commands.

61|17|Updated Feb 2, 2026

Search Tags:#architecture #onboarding #mobile #memory #state persistence #test-coverage

Ready to run

npx skills add https://github.com/ahmed3elshaer/everything-claude-code-mobile --skill mobile-memory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mobile-memory
Source: https://github.com/ahmed3elshaer/everything-claude-code-mobile/tree/main/skills/mobile-memory
Command: npx skills add https://github.com/ahmed3elshaer/everything-claude-code-mobile --skill mobile-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory persistence for mobile development context across sessions. Maintains project structure, dependencies, architecture, and test state to speed onboarding and ongoing work.

Core Features & Use Cases

Project Structure Memory: Remembers modules, variants, and feature modules.
Dependencies Memory: Tracks Gradle dependencies and tool versions.
Architecture Memory: Documents patterns like MVI, DI modules, and data flows.
Test Coverage Memory: Tracks coverage status and failing tests over time.
Use Case: When starting a new feature, recall the existing layout and tests to ensure consistency.

Quick Start

/memory-load all
/memory-save all
/memory-query What modules exist?
/memory-summary

Frequently Asked Questions about mobile-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I persist mobile project context across development sessions?▼

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.

Can I track module structure and dependencies over time in mobile development?▼

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.

What's the best way to maintain test coverage records across mobile project sessions?▼

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.

How do I speed up mobile onboarding by recalling project architecture?▼

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.

Does state persistence work with Gradle-based mobile projects?▼

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.

What happens if I need to refresh project memory during active development?▼

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.