design-ios

Solid

iOS + macOS mockups and handoff specs — Dynamic Type scale, semantic colors, device viewports, Liquid Glass, macOS text/window/pointer conventions, device-framed HTML mockup, and a SwiftUI-ready handoff spec. Produces tokens + mockup only, never SwiftUI code.

Web & Frontend 22 stars 3 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 88/100

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

Skill Content

## Design iOS/macOS — Mockup and Handoff, Not Code ### When After `design-system` tokens exist. This skill never writes SwiftUI — it produces a static HTML mockup at exact device/window dimensions plus a spec that `swift-expert` or an Apple-platform developer implements. ### Input - `design-system.md` — OKLCH palette, typography direction, motion personality. - The screen/flow to mock up and the target platform: iPhone / iPad (iOS) or a resizable window (macOS). ### Steps — iOS 1. **Map tokens to iOS roles.** Typography → Dynamic Type text styles, anchored at Body 17pt down to Caption 2 11pt (never fixed point sizes) — see `references/dynamic-type.md`. Colors → semantic color roles (never raw RGB/hex) — see `references/semantic-colors.md`. 2. **Pick the device viewport(s)** from `references/viewports.md` — mock up in exact points at the chosen scale factor. 3. **Build the HTML mockup**: a device-frame `<div>` at the exact viewport dimensions, `viewport-fit=cover` meta tag, `env(safe-area-inset-*)` for notch/Dynamic Island/home indicator spacing. See `references/mockup.md`. 4. **Apply Liquid Glass where it fits** — a floating layer of controls *above* regular content, not a content background. Two variants: **regular** (content-aware, the default for controls) and **clear** (more transparent — dim the content beneath it ~35% when clear sits over light content, so controls stay legible). Plus control morphing, concentricity between nested shapes...

Details

Author
fusengine
Repository
fusengine/agents
Created
6 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

design-android

Android mockups and handoff specs — Material 3 Expressive type scale (baseline + emphasized), full color-role system (45 roles incl. surface-container ramp + dynamic color), elevation tokens, shape scale, window size classes, FAB tiers, motion, device-framed HTML mockup, and a Compose-ready handoff spec. Produces tokens + mockup only, never Compose code.

22 Updated 2 days ago
fusengine
Web & Frontend Listed

design-handoff

Turns a mockup, screenshot, or HTML file into a dev-ready handoff spec - layout measurements, a token map, a component-state inventory, accessibility notes, and numbered open questions. Use for "write a handoff spec for this screen", "turn this mockup into dev docs", "document component states", or "what tokens does this screen use". Not for critiquing design quality or generating new UI - see design-review or html-mockup.

0 Updated 1 weeks ago
humbleteam
Web & Frontend Listed

claude-design-handoff

Implement designs handed off from Claude Design (claude.ai/design) into a real Next.js/TypeScript/React codebase with 1:1 visual fidelity AND working integration with live data and AI features. Use this whenever the user wants to build, implement, port, or "make real" a design that came from Claude Design: a handoff bundle (a folder whose README starts with "CODING AGENTS: READ THIS FIRST"), an exported .zip or standalone HTML, a set of .jsx prototype files plus a primary .html, or the user says things like "implement this design," "build this 1:1," "pixel-perfect," "I exported this from Claude Design," or "wire this design into the app." Trigger it even when the user only attaches a screenshot or PDF of a Claude Design mockup and asks to build it, and even when they describe a dashboard/report/genome/page design rather than naming Claude Design explicitly. Do not skip this skill in favor of eyeballing a screenshot and free-handing components: the failure mode it exists to prevent is exactly that.

0 Updated 3 days ago
andrewr303