mobile-system-design

Automate mobile system design with EventStorming, ADR templates, and Mermaid diagrams.

1|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zzafergok/skills --skill mobile-system-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-system-design
Source: https://github.com/zzafergok/skills/tree/main/02-software-architecture/mobile-system-design
Command: npx skills add https://github.com/zzafergok/skills --skill mobile-system-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile system design and architectural decision workflows for mobile apps, enabling structured discovery, ADR documentation, and diagrammatic communication.

Core Features & Use Cases

  • EventStorming for domain discovery
  • Architecture Decision Records templates
  • Mermaid-based C4 diagrams for documentation
  • Mobile-backend integration architecture and offline-first considerations
  • Domain modelling and stakeholder-facing diagrams

Quick Start

Describe a mobile feature idea and have the skill outline ADRs, eventstorming notes, and Mermaid diagrams for stakeholders.

Frequently Asked Questions about mobile-system-design

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

FAQPage Schema
How do I document mobile architecture decisions for stakeholders?▼

Document mobile architecture decisions by generating Architecture Decision Records (ADRs) that capture trade-offs and context. This approach provides structured templates for stakeholder-facing communication and technical rationale.

What is the best way to visualize a mobile system design for offline-first features?▼

Visualize a mobile system design using Mermaid-based C4 diagrams to map out offline-first architecture and backend integrations. This generates clear, diagrammatic documentation for technical communication.

How does EventStorming work for mobile domain discovery?▼

EventStorming works for mobile domain discovery by mapping domain events and workflows to identify architectural requirements. It automates structured discovery to reveal integration points and system boundaries.

Can I use ADR templates for both iOS and Android backend integration architecture?▼

Yes, you can use ADR templates for both iOS and Android backend integration architecture. The process supports configuring platform-agnostic integration patterns, including push-notification and offline-first setups.

When do I need architectural decision records for a new mobile feature?▼

You need architectural decision records when a new mobile feature involves complex trade-offs, such as configuring offline-first synchronization or push-notification architectures. ADRs ensure these decisions are documented systematically.