quantumquirkxyz 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
- Identify the core mobile interaction path.
- Define the seam around device and connectivity constraints.
- Decide what must work offline or under interruption.
- Describe the platform-specific behaviors that matter.
Completion criteria
- the mobile seam is named
- the offline boundary is named
- the device constraints are explicit