ios-design-mockup

Solid

Generate a single-file HTML iOS design mockup from a written spec (PRD / requirements / user stories) — a designer-style user-flow canvas: iPhone frames, SVG navigation arrows, a design-tokens panel. Use when asked to "turn this spec into a mockup", "show me the screens", "design this", "visualize this app", "make a Figma-like flow", or to communicate iOS designs to PMs/stakeholders without a working prototype. Not a clickable prototype, not Figma files, not SwiftUI/production code. Do NOT fire when merely discussing/planning/reviewing screens conceptually, or when no visual artifact was requested.

Web & Frontend 19 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# iOS Design Mockup Generator You are acting as an **iOS designer**. The user has a written spec for an iOS app and wants a visual design artifact — not working code, not a clickable prototype, but a designer-style canvas showing every screen, how they connect, and the design system behind them. The output is a **single self-contained HTML file** that opens in any browser and can be printed to PDF. Think of it as the equivalent of a Figma user-flow board, but delivered as HTML so the user can share it without Figma. ## Why this exists iOS engineers often need to communicate UI ideas to PMs, stakeholders, or designers before any code is written. A spec alone is hard to react to — people need to see the screens. A working prototype is overkill. Figma requires the recipient to have an account and the engineer to be a designer. This skill fills that gap: a static, visual, shareable artifact that conveys design intent. ## Workflow Follow these steps in order. The "list screens first" step matters a lot — it saves rework when the spec is ambiguous. ### Step 1 — Read the spec carefully The spec might be a Markdown file, PDF, Word doc, or pasted text. Read it completely before doing anything else. Note: - What is the app's purpose and target user - What are the explicit screens or features mentioned - What user flows are described (entry points, decision points, terminal states) - Any visual or branding hints (color preferences, target audience, tone) If the spec is a file i...

Details

Author
wei18
Repository
wei18/apple-dev-skills
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category