swiftui-design-skill
정보
이 스킬은 개발자들이 일반적인 AI 생성 패턴을 피하면서 독특하고 고품질의 SwiftUI 인터페이스를 설계할 수 있도록 돕습니다. 디자인 방향, 레이아웃, 타이포그래피에 대한 지침과 뷰, 프로토타입, 앱 미학을 위한 체계적인 검토 프로세스를 제공합니다. SwiftUI 화면을 제작하거나 개선할 때 사용하여 의도적으로 설계된 모습을 보장하세요.
빠른 설치
Claude Code
추천npx skills add wholiver/swiftui-design-skill -a claude-code/plugin add https://github.com/wholiver/swiftui-design-skillgit clone https://github.com/wholiver/swiftui-design-skill.git ~/.claude/skills/swiftui-design-skillClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
SwiftUI Design Skill
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.
When to Use
- Designing new SwiftUI views or screens from scratch
- Reviewing or improving existing UI quality
- Creating iOS app prototypes or mockups
- Choosing a visual style or design direction
- Integrating brand assets into SwiftUI
- When someone says "the UI looks generic" or "make it look better"
- When building a new feature that needs visual design
When NOT to Use
- Pure backend / API work with no UI
- Fixing SwiftUI compilation errors (use swiftui-expert-skill instead)
- Performance optimization of existing views (use swiftui-expert-skill)
- Accessibility compliance only (use swiftui-expert-skill's accessibility topic)
Prerequisites
- Xcode 16+ with iOS 18+ / macOS 15+ SDK
- SwiftUI framework (not UIKit unless explicitly requested)
- Familiarity with SwiftUI view hierarchy and modifiers
Core Design Philosophy
These 6 principles guide every design decision. They are distilled from real-world design practice and anti-patterns observed in AI-generated UI.
Principle 1: Start From Context, Never Blank
Before designing any screen, ask:
- Is there an existing design system, UI kit, or Figma file?
- Is there an existing codebase with established visual language?
- Are there brand guidelines or a style guide?
If no context exists, create a brand-spec.md first (see Brand Asset Protocol below).
Principle 2: Junior Designer Mode — Hypothesize Early, Iterate Fast
Don't wait for the "perfect" design. Show hypotheses with placeholders early:
- Gray boxes for images are better than bad AI-generated SVGs
- System fonts with good spacing > custom fonts with bad spacing
- A rough but honest layout > a polished but generic one
Principle 3: Offer Variations, Not Finals
Always present 2-3 distinct design directions, not one "final answer." Each variation should:
- Represent a different design philosophy (e.g., editorial, functional, expressive)
- Have a clear rationale for why it works
- Be visually distinct — not just color swaps
Principle 4: Placeholder > Bad Implementation
If you cannot source a real asset (icon, image, illustration):
- Use a clean gray placeholder with clear labeling
- Never use AI-generated SVG clipart
- Never use emoji as icon substitutes in production UI
- For icons, prefer SF Symbols (Apple's built-in icon library)
Principle 5: System First, Don't Fill
Every element must earn its place. Before adding any UI element, ask:
- Does this serve the user's goal?
- Can this be combined with something else?
- What happens if I remove it?
Whitespace is a feature, not emptiness.
Principle 6: Anti-AI-Slop
These patterns are banned in production UI. See references/anti-ai-slop.md for detailed rules.
Banned visual patterns:
- ❌ Purple-to-blue gradient backgrounds
- ❌ Emoji as functional icons
- ❌ Rounded cards with left-border accent color
- ❌ Generic "hero section" with centered text over gradient
- ❌ Inter/Roboto as display fonts on Apple platforms
- ❌ Neon-on-dark "cyber" aesthetic (#0D1117 base)
- ❌ Symmetric 3-column feature grids
- ❌ AI-drawn SVG illustrations or CSS silhouettes
What to do instead:
- ✅ Single warm accent color on neutral background
- ✅ SF Symbols for icons, or custom icon set
- ✅ Serif display font (e.g., New York, Georgia) for headings
- ✅ Restrained info density — let content breathe
- ✅ One signature detail at 120% effort per screen
- ✅ Real photography or clean placeholders
Brand Asset Protocol
When building UI for a specific brand, follow this 5-step hard flow:
- Ask — Request brand guidelines, logo files, color palette, typography
- Search — If not provided, search the web for "[brand name] brand guidelines"
- Download — Get actual asset files (PNG/SVG logos, font files)
- Verify — Confirm colors match official sources (check hex values)
- Write brand-spec.md — Document: primary/secondary colors, fonts, logo usage rules, spacing tokens
Quality threshold: 5 real brand colors, 10 verified design tokens, 2 font families, 8pt spacing grid.
If no brand exists, create a brand-spec.md with:
- 1 primary accent color (warm, not purple-blue gradient)
- 1 neutral palette (grays with warm undertone)
- 1 display font + 1 body font (SF Pro default is fine)
- 8pt spacing grid
Design Direction Workflow
When requirements are vague or the user asks "what style should we use?", follow this workflow:
Phase 1: Understand Context (5 min)
- Ask: What is the app? Who is the user? What platform (iOS/macOS/watchOS)?
- Ask: Any reference apps or websites they admire?
- Check: Existing design system or brand assets?
Phase 2: Recommend 3 Directions
Present 3 distinct design philosophies from different schools:
| School | Example Directions |
|---|---|
| Information | Clean data-first, chart-heavy, Bloomberg-style |
| Editorial | Magazine layout, serif typography, generous whitespace |
| Expressive | Bold color, asymmetric layout, motion-forward |
| Functional | Dense utility, monospace accents, minimal decoration |
| Warm Minimal | Soft neutrals, rounded shapes, subtle texture |
Phase 3: Present Visual Anchors
For each direction, describe:
- Color palette (3-5 colors with hex values)
- Typography pairing (display + body)
- Layout density (comfortable / compact / spacious)
- Signature detail (one standout element per screen)
Phase 4: Let User Choose
Present options clearly. After choice, lock in the design system.
SwiftUI Design Workflow
Step 1: Define the Design System (Before Coding)
Create or confirm these design tokens:
// Requires: references/swift-extensions.md (Color(hex:) extension)
// DesignTokens.swift
enum DesignTokens {
// Colors
static let accent = Color(hex: "E85D3A") // Warm coral
static let background = Color(hex: "FAFAF8") // Warm white
static let textPrimary = Color(hex: "1A1A1A") // Near-black
static let textSecondary = Color(hex: "6B6B6B") // Muted gray
// Typography
static let displayFont = "New York" // Serif for headings
static let bodyFont = "SF Pro" // System default
// Spacing (8pt grid)
static let spaceXS: CGFloat = 4
static let spaceS: CGFloat = 8
static let spaceM: CGFloat = 16
static let spaceL: CGFloat = 24
static let spaceXL: CGFloat = 32
static let spaceXXL: CGFloat = 48
// Corner radius
static let radiusS: CGFloat = 8
static let radiusM: CGFloat = 12
static let radiusL: CGFloat = 16
}
Step 2: Build the Layout Hierarchy
Follow the layout patterns in references/layout-patterns.md:
- Start with the primary content container
- Use
VStackfor vertical flow,HStackfor horizontal - Use
LazyVGrid/LazyHGridfor grid layouts - Use
ScrollViewwith.scrollTargetBehavior(.paging)for paged content - Avoid
GeometryReader— prefercontainerRelativeFrame(iOS 17+)
Step 3: Apply Typography Hierarchy
Follow references/typography-color.md:
- Display (screen titles): Serif font, 28-34pt, bold
- Heading (section titles): Sans-serif, 20-24pt, semibold
- Body (content text): Sans-serif, 15-17pt, regular
- Caption (labels, metadata): Sans-serif, 12-13pt, secondary color
Step 4: Add the Signature Detail
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.
Examples:
- A custom pull-to-refresh with brand-colored animation
- A card that expands with a spring animation on tap
- A header that uses the brand's display font at an oversized scale
- A subtle parallax effect on scroll
Step 5: Review Against Checklist
Before shipping, run the 5-Dimension Review (see references/design-review.md).
Common Mistakes to Avoid
| Mistake | Fix |
|---|---|
Using UIColor or NSColor | Use Color (SwiftUI native) |
UIScreen.main.bounds for sizing | Use containerRelativeFrame or geometry-based modifiers |
| Default blue tint everywhere | Define a custom accent color in design tokens |
| No spacing system (random padding values) | Use 8pt grid: 4, 8, 16, 24, 32, 48 |
| Emoji as icons | Use SF Symbols or custom icon assets |
| Purple-blue gradient background | Use solid warm neutrals |
| All content in one giant VStack | Break into semantic sections with clear hierarchy |
| No visual hierarchy (everything same size) | Use 3+ type scales (display, heading, body, caption) |
| Ignoring dark mode | Define semantic colors that adapt to appearance |
| Generic "Welcome!" hero section | Show actual content immediately |
Quick Reference: Topic Router
| Topic | Reference File |
|---|---|
| Anti-AI-Slop Rules (detail) | references/anti-ai-slop.md |
| Layout Patterns & Grids | references/layout-patterns.md |
| Typography & Color Systems | references/typography-color.md |
| 5-Dimension Design Review | references/design-review.md |
| Swift Extensions (required) | references/swift-extensions.md |
| Brand Spec Template | templates/brand-spec.md |
Validation Checklist
Before considering any SwiftUI design complete, verify:
- Design tokens defined (colors, fonts, spacing)
- No banned AI-slop patterns present
- Typography has clear hierarchy (3+ scales)
- Spacing follows 8pt grid
- Dark mode colors defined and tested
- One signature detail per screen
- SF Symbols used for icons (not emoji)
- Minimum 44×44pt tap targets
- No
GeometryReaderorUIScreen.main.bounds - 5-Dimension Review score ≥ 7/10 on all dimensions
GitHub 저장소
연관 스킬
content-collections
메타이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
polymarket
메타이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
creating-opencode-plugins
메타이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
sglang
메타SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
