Skip to content
Back to search

swiftui-design-skill

SkillWorks with Claude CodeGitHub

SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wholiver--swiftui-design-skill/badge.svg)](/listings/wholiver--swiftui-design-skill)

HTML

<a href="/listings/wholiver--swiftui-design-skill"><img src="/api/listings/wholiver--swiftui-design-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

npx skills add wholiver/swiftui-design-skill -g -y

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 270 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: swiftui-design-skill
  3. description: SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.
  4. license: MIT
  5. metadata:
  6. author: wholiver
  7. version: "1.0.0"
  8. ---
  9. # SwiftUI Design Skill
  10. > **TL;DR**: Design SwiftUI apps that look intentionally crafted, not AI-generated. Follow the 6 Anti-Slop Rules, use the Design Direction workflow when requirements are vague, and always pass the 5-Dimension Review before shipping.
  11. ## When to Use
  12. - Designing new SwiftUI views or screens from scratch
  13. - Reviewing or improving existing UI quality
  14. - Creating iOS app prototypes or mockups
  15. - Choosing a visual style or design direction
  16. - Integrating brand assets into SwiftUI
  17. - When someone says "the UI looks generic" or "make it look better"
  18. - When building a new feature that needs visual design
  19. ## When NOT to Use
  20. - Pure backend / API work with no UI
  21. - Fixing SwiftUI compilation errors (use swiftui-expert-skill instead)
  22. - Performance optimization of existing views (use swiftui-expert-skill)
  23. - Accessibility compliance only (use swiftui-expert-skill's accessibility topic)
  24. ## Prerequisites
  25. - Xcode 16+ with iOS 18+ / macOS 15+ SDK
  26. - SwiftUI framework (not UIKit unless explicitly requested)
  27. - Familiarity with SwiftUI view hierarchy and modifiers
  28. ---
  29. ## Core Design Philosophy
  30. These 6 principles guide every design decision. They are distilled from real-world design practice and anti-patterns observed in AI-generated UI.
  31. ### Principle 1: Start From Context, Never Blank
  32. Before designing any screen, ask:
  33. - Is there an existing design system, UI kit, or Figma file?
  34. - Is there an existing codebase with established visual language?
  35. - Are there brand guidelines or a style guide?
  36. If no context exists, create a **brand-spec.md** first (see Brand Asset Protocol below).
  37. ### Principle 2: Junior Designer Mode — Hypothesize Early, Iterate Fast
  38. Don't wait for the "perfect" design. Show hypotheses with placeholders early:
  39. - Gray boxes for images are **better** than bad AI-generated SVGs
  40. - System fonts with good spacing > custom fonts with bad spacing
  41. - A rough but honest layout > a polished but generic one
  42. ### Principle 3: Offer Variations, Not Finals
  43. Always present **2-3 distinct design directions**, not one "final answer." Each variation should:
  44. - Represent a different design philosophy (e.g., editorial, functional, expressive)
  45. - Have a clear rationale for why it works
  46. - Be visually distinct — not just color swaps
  47. ### Principle 4: Placeholder > Bad Implementation
  48. If you cannot source a real asset (icon, image, illustration):
  49. - Use a clean gray placeholder with clear labeling
  50. - Never use AI-generated SVG clipart
  51. - Never use emoji as icon substitutes in production UI
  52. - For icons, prefer SF Symbols (Apple's built-in icon library)
  53. ### Principle 5: System First, Don't Fill
  54. Every element must earn its place. Before adding any UI element, ask:
  55. - Does this serve the user's goal?
  56. - Can this be combined with something else?
  57. - What happens if I remove it?
  58. Whitespace is a feature, not emptiness.
  59. ### Principle 6: Anti-AI-Slop
  60. These patterns are **banned** in production UI. See `references/anti-ai-slop.md` for detailed rules.
  61. **Banned visual patterns:**
  62. - ❌ Purple-to-blue gradient backgrounds
  63. - ❌ Emoji as functional icons
  64. - ❌ Rounded cards with left-border accent color
  65. - ❌ Generic "hero section" with centered text over gradient
  66. - ❌ Inter/Roboto as display fonts on Apple platforms
  67. - ❌ Neon-on-dark "cyber" aesthetic (#0D1117 base)
  68. - ❌ Symmetric 3-column feature grids
  69. - ❌ AI-drawn SVG illustrations or CSS silhouettes
  70. **What to do instead:**
  71. - ✅ Single warm accent color on neutral background
  72. - ✅ SF Symbols for icons, or custom icon set
  73. - ✅ Serif display font (e.g., New York, Georgia) for headings
  74. - ✅ Restrained info density — let content breathe
  75. - ✅ One signature detail at 120% effort per screen
  76. - ✅ Real photography or clean placeholders
  77. ---
  78. ## Brand Asset Protocol
  79. When building UI for a specific brand, follow this 5-step hard flow:
  80. 1. **Ask** — Request brand guidelines, logo files, color palette, typography
  81. 2. **Search** — If not provided, search the web for "[brand name] brand guidelines"
  82. 3. **Download** — Get actual asset files (PNG/SVG logos, font files)
  83. 4. **Verify** — Confirm colors match official sources (check hex values)
  84. 5. **Write brand-spec.md** — Document: primary/secondary colors, fonts, logo usage rules, spacing tokens
  85. **Quality threshold**: 5 real brand colors, 10 verified design tokens, 2 font families, 8pt spacing grid.
  86. If no brand exists, create a brand-spec.md with:
  87. - 1 primary accent color (warm, not purple-blue gradient)
  88. - 1 neutral palette (grays with warm undertone)
  89. - 1 display font + 1 body font (SF Pro default is fine)
  90. - 8pt spacing grid
  91. ---
  92. ## Design Direction Workflow
  93. When requirements are vague or the user asks "what style should we use?", follow this workflow:
  94. ### Phase 1: Understand Context (5 min)
  95. 1. Ask: What is the app? Who is the user? What platform (iOS/macOS/watchOS)?
  96. 2. Ask: Any reference apps or websites they admire?
  97. 3. Check: Existing design system or brand assets?
  98. ### Phase 2: Recommend 3 Directions
  99. Present 3 distinct design philosophies from different schools:
  100. | School | Example Directions |
  101. | --------------- | ------------------------------------------- |
  102. | **Information** | Clean data-first, chart-heavy, Bloomberg-style |
  103. | **Editorial** | Magazine layout, serif typography, generous whitespace |
  104. | **Expressive** | Bold color, asymmetric layout, motion-forward |
  105. | **Functional** | Dense utility, monospace accents, minimal decoration |
  106. | **Warm Minimal** | Soft neutrals, rounded shapes, subtle texture |
  107. ### Phase 3: Present Visual Anchors
  108. For each direction, describe:
  109. - Color palette (3-5 colors with hex values)
  110. - Typography pairing (display + body)
  111. - Layout density (comfortable / compact / spacious)
  112. - Signature detail (one standout element per screen)
  113. ### Phase 4: Let User Choose
  114. Present options clearly. After choice, lock in the design system.
  115. ---
  116. ## SwiftUI Design Workflow
  117. ### Step 1: Define the Design System (Before Coding)
  118. Create or confirm these design tokens:
  119. ```swift
  120. // Requires: references/swift-extensions.md (Color(hex:) extension)
  121. // DesignTokens.swift
  122. enum DesignTokens {
  123. // Colors
  124. static let accent = Color(hex: "E85D3A") // Warm coral
  125. static let background = Color(hex: "FAFAF8") // Warm white
  126. static let textPrimary = Color(hex: "1A1A1A") // Near-black
  127. static let textSecondary = Color(hex: "6B6B6B") // Muted gray
  128. // Typography
  129. static let displayFont = "New York" // Serif for headings
  130. static let bodyFont = "SF Pro" // System default
  131. // Spacing (8pt grid)
  132. static let spaceXS: CGFloat = 4
  133. static let spaceS: CGFloat = 8
  134. static let spaceM: CGFloat = 16
  135. static let spaceL: CGFloat = 24
  136. static let spaceXL: CGFloat = 32
  137. static let spaceXXL: CGFloat = 48
  138. // Corner radius
  139. static let radiusS: CGFloat = 8
  140. static let radiusM: CGFloat = 12
  141. static let radiusL: CGFloat = 16
  142. }
  143. ```
  144. ### Step 2: Build the Layout Hierarchy
  145. Follow the layout patterns in `references/layout-patterns.md`:
  146. - Start with the primary content container
  147. - Use `VStack` for vertical flow, `HStack` for horizontal
  148. - Use `LazyVGrid` / `LazyHGrid` for grid layouts
  149. - Use `ScrollView` with `.scrollTargetBehavior(.paging)` for paged content
  150. - Avoid `GeometryReader` — prefer `containerRelativeFrame` (iOS 17+)
  151. ### Step 3: Apply Typography Hierarchy
  152. Follow `references/typography-color.md`:
  153. - **Display** (screen titles): Serif font, 28-34pt, bold
  154. - **Heading** (section titles): Sans-serif, 20-24pt, semibold
  155. - **Body** (content text): Sans-serif, 15-17pt, regular
  156. - **Caption** (labels, metadata): Sans-serif, 12-13pt, secondary color
  157. ### Step 4: Add the Signature Detail
  158. Each screen should have ONE element that goes 120% — a custom animation, a unique layout choice, a distinctive color moment. This is what makes the design memorable.
  159. Examples:
  160. - A custom pull-to-refresh with brand-colored animation
  161. - A card that expands with a spring animation on tap
  162. - A header that uses the brand's display font at an oversized scale
  163. - A subtle parallax effect on scroll
  164. ### Step 5: Review Against Checklist
  165. Before shipping, run the 5-Dimension Review (see `references/design-review.md`).
  166. ---
  167. ## Common Mistakes to Avoid
  168. | Mistake | Fix |
  169. | ------------------------------------------ | -------------------------------------------------------- |
  170. | Using `UIColor` or `NSColor` | Use `Color` (SwiftUI native) |
  171. | `UIScreen.main.bounds` for sizing | Use `containerRelativeFrame` or geometry-based modifiers |
  172. | Default blue tint everywhere | Define a custom accent color in design tokens |
  173. | No spacing system (random padding values) | Use 8pt grid: 4, 8, 16, 24, 32, 48 |
  174. | Emoji as icons | Use SF Symbols or custom icon assets |
  175. | Purple-blue gradient background | Use solid warm neutrals |
  176. | All content in one giant VStack | Break into semantic sections with clear hierarchy |
  177. | No visual hierarchy (everything same size) | Use 3+ type scales (display, heading, body, caption) |
  178. | Ignoring dark mode | Define semantic colors that adapt to appearance |
  179. | Generic "Welcome!" hero section | Show actual content immediately |
  180. ---
  181. ## Quick Reference: Topic Router
  182. | Topic | Reference File |
  183. | ---------------------------- | ----------------------------------- |
  184. | Anti-AI-Slop Rules (detail) | `references/anti-ai-slop.md` |
  185. | Layout Patterns & Grids | `references/layout-patterns.md` |
  186. | Typography & Color Systems | `references/typography-color.md` |
  187. | 5-Dimension Design Review | `references/design-review.md` |
  188. | Swift Extensions (required) | `references/swift-extensions.md` |
  189. | Brand Spec Template | `templates/brand-spec.md` |
  190. ---
  191. ## Validation Checklist
  192. Before considering any SwiftUI design complete, verify:
  193. - [ ] Design tokens defined (colors, fonts, spacing)
  194. - [ ] No banned AI-slop patterns present
  195. - [ ] Typography has clear hierarchy (3+ scales)
  196. - [ ] Spacing follows 8pt grid
  197. - [ ] Dark mode colors defined and tested
  198. - [ ] One signature detail per screen
  199. - [ ] SF Symbols used for icons (not emoji)
  200. - [ ] Minimum 44×44pt tap targets
  201. - [ ] No `GeometryReader` or `UIScreen.main.bounds`
  202. - [ ] 5-Dimension Review score ≥ 7/10 on all dimensions
README.md · README · 127 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. # SwiftUI Design Skill
  3. > *"One prompt. A shippable SwiftUI interface."*
  4. [![License](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
  5. [![Agent-Agnostic](https://img.shields.io/badge/Agent-Agnostic-blueviolet)](https://skills.sh)
  6. [![Skills](https://img.shields.io/badge/skills.sh-Compatible-green)](https://skills.sh)
  7. </div>
  8. <p align="center">
  9. <a href="README.md"><img src="https://img.shields.io/badge/English-blue?style=flat-square" alt="English"></a>
  10. <a href="README-zh.md"><img src="https://img.shields.io/badge/中文-red?style=flat-square" alt="中文"></a>
  11. </p>
  12. **Type one line in your agent. Get back a SwiftUI interface that doesn't look AI-generated.**
  13. In 3 to 30 minutes, you can design a **signature iOS interface** — not "AI-made-it-looks-okay" quality, but something that looks like it was crafted by a designer with taste.
  14. Anti-AI Slop 6 Iron Rules, Design Direction Advisor, Brand Asset Protocol, 5-Dimension Review — all built in. Give the skill your brand palette and it will read your vibe; give nothing and the 5 built-in design languages will still hold their ground.
  15. Works across agents — Claude Code, Cursor, Codex, OpenCode, Hermes, all supported.
  16. ## Install & Go
  17. ```bash
  18. npx skills add wholiver/swiftui-design-skill -g -y
  19. ```
  20. ## What Can It Do
  21. | Capability | Deliverable | Typical Time |
  22. |------------|-------------|--------------|
  23. | SwiftUI Interface Design | Compilable SwiftUI code · Design system tokens · Layout patterns | 10–15 min |
  24. | Design Direction Advisor | 5 schools × N design philosophies · 3 recommended directions · Visual anchor descriptions | 5 min |
  25. | Brand Asset Integration | brand-spec.md · Color palette · Typography · Spacing system | 5–10 min |
  26. | Anti-AI Slop Review | Item-by-item check · Concrete fix code · Alternative approaches | 3–5 min |
  27. | 5-Dimension Review | Radar chart scoring · Keep/Fix/Quick Wins · Actionable fix checklist | 3 min |
  28. | Layout Pattern Library | 9 common layouts · Copy-paste SwiftUI code | Instant |
  29. | Animation Design | Spring/parallax/pull-to-refresh · Compilable code | 5–10 min |
  30. ## Core Mechanisms
  31. ### Anti-AI Slop 6 Iron Rules
  32. This is the hardest set of rules in the skill. All designs must pass these 6 checks:
  33. | # | Iron Rule | ❌ Forbidden | ✅ Alternative |
  34. |---|-----------|-------------|----------------|
  35. | 1 | Start from context | Inventing from a blank canvas | Ask about design system / UI kit / brand assets first |
  36. | 2 | Junior Designer Mode | Waiting for the perfect solution | Gray placeholder > bad SVG |
  37. | 3 | Give variants, not finals | One "final answer" | 2–3 differentiated directions |
  38. | 4 | Placeholder > bad implementation | AI-generated clip art | Clean gray placeholder + text label |
  39. | 5 | System-first, don't fill | Packing every pixel | Every element must justify its existence |
  40. | 6 | Ban AI slop patterns | Purple-blue gradients, emoji icons, rounded cards + left border | Single warm accent color, SF Symbols, serif headlines |
  41. See `references/anti-ai-slop.md` for details.
  42. ### Design Direction Advisor
  43. When requirements are vague, the skill recommends 3 differentiated directions from 5 major design schools:
  44. | School | Characteristics | Signature Style |
  45. |--------|-----------------|-----------------|
  46. | **Informational** | Data-first, chart-dense | Bloomberg Terminal |
  47. | **Editorial** | Magazine layout, serif type, generous whitespace | NYT, Medium |
  48. | **Expressive** | Bold color, asymmetric layout, motion-forward | Stripe, Linear |
  49. | **Functional** | Dense tool feel, monospace accents | Things, OmniFocus |
  50. | **Warm Minimal** | Soft neutrals, rounded corners, subtle texture | Notion, Craft |
  51. ### Brand Asset Protocol
  52. A mandatory 5-step hard process when working with a specific brand:
  53. | Step | Action | Purpose |
  54. |------|--------|---------|
  55. | 1 · Ask | Does the user have brand guidelines? | Respect existing assets |
  56. | 2 · Search | Search the brand's official pages | Obtain real materials |
  57. | 3 · Download | Download actual asset files | PNG/SVG logos, fonts |
  58. | 4 · Verify | Verify colors match official sources | Cross-check hex values |
  59. | 5 · Write | Generate brand-spec.md | Record complete design system |
  60. Quality threshold: 5 real brand colors, 10 design tokens, 2 font families, 8pt spacing grid.
  61. ### 5-Dimension Review
  62. Every design must pass a 5-dimension review before delivery:
  63. | Dimension | Scoring Criteria | Minimum Score |
  64. |-----------|------------------|---------------|
  65. | 🎯 Philosophy Consistency | Does the design embody the chosen design philosophy? | ≥ 7/10 |
  66. | 📐 Visual Hierarchy | Is the information priority clear? | ≥ 7/10 |
  67. | 🔧 Detail Execution | Are spacing, typography, and colors precise? | ≥ 7/10 |
  68. | ⚡ Functionality | Does the layout serve user goals? | ≥ 7/10 |
  69. | ✨ Originality | Is there at least 1 signature detail? | ≥ 7/10 |
  70. ## File Structure
  71. ```
  72. swiftui-design-skill/
  73. ├── SKILL.md ← Core definition (278 lines)
  74. ├── references/
  75. │ ├── anti-ai-slop.md ← Anti-AI Slop detailed rules (268 lines)
  76. │ ├── layout-patterns.md ← 9 layout patterns + copy-paste code (265 lines)
  77. │ ├── typography-color.md ← Typography hierarchy + color system (172 lines)
  78. │ ├── design-review.md ← 5-Dimension Review process (151 lines)
  79. │ └── swift-extensions.md ← Color/Font/Animation extensions (373 lines, essential)
  80. └── templates/
  81. └── brand-spec.md ← Brand spec template (77 lines)
  82. ```
  83. ## Difference from swiftui-expert-skill
  84. | | SwiftUI Design Skill | swiftui-expert-skill |
  85. |---|---|---|
  86. | **Focus** | Visual design, aesthetics, brand feel | Code quality, performance, correctness |
  87. | **Question** | "How does it look?" | "Is the code correct?" |
  88. | **Output** | Design direction, color palette, layout, review | Code review, Instruments analysis, API modernization |
  89. | **Complementary** | Use Design first to set direction | Then use Expert to ensure code quality |
  90. The two skills work together: Design decides **what to build**, Expert ensures **how to build it right**.
  91. ## License
  92. MIT — use freely, but please keep the original author attribution.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.