Mobile System Design

Architecture + EventStorming + ADR + Mermaid Diagrams — structuring and documenting architectural decisions for mobile applications and their backend services.

When to Use This Skill

Invoke this skill in the following situations:

• Before designing a new feature or service
• At an architectural decision point (which approach and why)
• When defining an offline-first, push notification, or sync strategy
• When establishing an API contract between the backend and the mobile client
• When formalising a technical debt or refactoring decision in writing
• When producing architecture documentation for the team or stakeholders

Core principle: Complexity is not introduced until it is proven necessary. The simplest working solution is always the first candidate.