# Mobile

> Shape mobile projects around device constraints, offline behavior, and platform seams — with explicit performance and resilience boundaries.

- Skill: `quantumquirkxyz/mobile` (Agent Skill)
- Install (CLI): `npx skillmds@latest add quantumquirkxyz/mobile`
- Raw SKILL.md: https://api.skillmd.com/api/skills/quantumquirkxyz/mobile/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: quantumquirkxyz (https://skillmd.com/u/quantumquirkxyz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/quantumquirkxyz/mobile

---


## Contract

- **Input:** problem or task defined by the skill body.
- **Output:** Markdown artifact or structured result with completion criteria met.
- **Side effects:** none (design/review/documentation only unless explicitly stated).
- **Dependencies:** none (self-contained unless linked to other skills).
- **Stop condition:** all process steps completed; artifact saved; criteria checked.
- **Risk:** low.
- **Boundary:** produces reasoning or documentation artifacts; does not modify external systems unless explicitly instructed.


# Mobile

Use this skill when the product needs to respect device constraints, offline behavior, or platform-specific UX. It should keep the seam explicit so the app can remain reliable across different device conditions.

## Contract

- Input: mobile brief, device constraints, and interaction context.
- Output: mobile seam proposal, device-flow guidance, and offline boundary guidance.
- Scope: design the mobile shape, not the full implementation.
- Rule: account for small screens, interruptions, and connectivity loss.
- Rule: make offline behavior explicit when it matters.
- Rule: keep platform-specific quirks visible rather than hidden behind generic advice.

## Steps

1. Identify the core mobile interaction path.
2. Define the seam around device and connectivity constraints.
3. Decide what must work offline or under interruption.
4. Describe the platform-specific behaviors that matter.

## Completion criteria

- the mobile seam is named
- the offline boundary is named
- the device constraints are explicit