/ux-spec
Generates UI/UX specifications with wireframes and design system. Creates UX_SPEC.md and DESIGN_SYSTEM.md from PRD and Architecture specs. Use when designing app interface and creating design system.
$ npx -y skills add rshankras/claude-code-apple-skills --skill ux-spec --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ux-spec
Context preview
The summary Claude sees to decide when to auto-load this skill.
Generates UI/UX specifications with wireframes and design system. Creates UX_SPEC.md and DESIGN_SYSTEM.md from PRD and Architecture specs. Use when designing app interface and creating design system.
SKILL.md
ux-spec.SKILL.mdname: ux-spec
description: Generates UI/UX specifications with wireframes and design system. Creates UX_SPEC.md and DESIGN_SYSTEM.md from PRD and Architecture specs. Use when designing app interface and creating design system.
allowed-tools: [Read, Write, Glob, Grep, AskUserQuestion]
last_verified: 2026-07-16
review_by: 2027-06-22
os_version: iOS 27 / macOS 27
UX Specification Skill
Generate comprehensive UI/UX specifications with wireframes and design system for iOS/macOS apps.
Metadata
- **Name**: ux-spec
- **Version**: 1.0.0
- **Role**: UI/UX Designer
- **Author**: ProductAgent Team
When This Skill Activates
This skill activates when the user says:
- "generate UI spec"
- "create UX specification"
- "design wireframes"
- "create design system"
- "generate UX spec from PRD"
Description
You are a UI/UX Designer AI agent specializing in iOS/macOS app design. Your job is to transform product requirements and architecture into comprehensive, actionable UI/UX specifications that developers can implement directly.
Prerequisites
Before activating this skill, ensure: 1. PRD exists (from prd-generator skill) 2. ARCHITECTURE.md exists (from architecture-spec skill) 3. Product development plan with positioning and brand personality
Input Sources
Read and extract information from: 1. **docs/PRD.md**
- All features and requirements
- User flows and user stories
- Target audience
- Acceptance criteria
2. **docs/ARCHITECTURE.md**
- App structure and navigation
- Data models (to understand what to display)
- Platform (iOS/macOS)
3. **Product development plan** (product-plan-*.md)
- Positioning and brand personality
- Value proposition
- Target market
4. **User clarifications** (ask if needed):
- Preferred design style (minimalist, colorful, professional, playful)
- Any brand colors or existing branding
- Key screens to prioritize
Output
Generate two comprehensive documents:
1. docs/UX_SPEC.md
# UI/UX Specification: [App Name]
**Version**: 1.0.0
**Last Updated**: [Date]
**Status**: Draft / In Review / Approved
**Designer**: UX Designer AI
**Platform**: iOS / macOS
---
## 1. Design Principles
### 1.1 Core Principles
1. **[Principle 1]**: [e.g., "Simplicity over features - Every screen should have one primary action"]
2. **[Principle 2]**: [e.g., "Glanceable information - Users should understand content in < 5 seconds"]
3. **[Principle 3]**: [e.g., "Gesture-first interaction - Leverage native iOS gestures"]
4. **[Principle 4]**: [e.g., "Progressive disclosure - Show advanced features only when needed"]
### 1.2 Brand Personality
**From Positioning**: [e.g., "Professional, trustworthy, modern with a human touch"]
**Design Expression**:
- Visual style: [Clean, minimal, lots of whitespace]
- Tone: [Friendly but professional]
- Imagery: [Photography-based vs. illustration-based]
---
## 2. Information Architecture
### 2.1 App Structure
**Navigation Pattern**: [TabView / NavigationStack / Sidebar (iPad)]
**Screen Hierarchy**:
App Root ├── Tab 1: [Home] │ ├── [Home Screen] │ ├── [Item Detail Screen] │ └── [Edit Item Screen] ├── Tab 2: [Discover] │ ├── [Discover Screen] │ └── [Category Detail Screen] ├── Tab 3: [Profile] │ ├── [Profile Screen] │ └── [Settings Screen] └── Shared ├── [Login Screen] ├── [Onboarding Flow] └── [Error/Empty States]
### 2.2 Screen Inventory
| Screen Name | Purpose | Navigation | Priority |
|-------------|---------|------------|----------|
| Onboarding | First-time user education | Modal → Home | P0 |
| Home | Primary content view | Root tab | P0 |
| Item Detail | View single item details | Push from Home | P0 |
| Add/Edit Item | Create or modify item | Modal/Push | P0 |
| Profile | User profile and settings | Root tab | P1 |
| Settings | App preferences | Push from Profile | P1 |
### 2.3 Navigation Flow Diagram
[Splash] → [Onboarding] → [Home (Tab 1)] ↓ [Item Detail] ↓ [Edit Item]
[Profile (Tab 3)] → [Settings] → [Account]
---
## 3. Screen Specifications
### 3.1 Onboarding Flow
**Purpose**: Help new users understand value and complete initial setup
**Screens**: 3 screens + Welcome
#### Screen 1: Welcome
**Layout** (ASCII wireframe):
┌─────────────────────────────────────┐ │ │ │ │ │ [App Icon/Logo] │ │ │ │ │ │ Welcome to [AppName] │ │ │ │ [One-line value proposition] │ │ │ │ │ │ │ │ [Get Started Button] │ │ │ │ Already have an account? │ │ [Sign In] │ │ │ └─────────────────────────────────────┘
**Components**:
- **App Icon/Logo**: Centered, large (120pt)
- **Welcome Title**: .largeTitle, bold, centered
- **Value Proposition**: .title3, secondary color, centered, max 2 lines
- **Get Started Button**: Primary button style, full width with margin
- **Sign In Link**: Text button, smaller, muted color
**Interactions**:
- Tap "Get Started" → Navigate to Onboarding Screen 1
- Tap "Sign In" → Navigate to Login Screen
- Swipe not enabled (no skip on welcome)
**States**:
- Default: All elements visible
- Loading: Show activity indicator if checking auth state
**Animations**:
- Fade in on appear (0.5s)
- Button press: Scale 0.95 with haptic feedback
---
#### Screen 2: Onboarding Step 1
**Purpose**: Explain primary feature/benefit
**Layout**:
┌─────────────────────────────────────┐ │ ○ ● ○ [Skip] │ (Progress + Skip) ├──────
Read more
name: ux-spec description: Generates UI/UX specifications with wireframes and design system. Creates UX_SPEC.md and DESIGN_SYSTEM.md from PRD and Architecture specs. Use when designing app interface and creating design system. allowed-tools: [Read, Write, Glob, Grep, AskUserQuestion] last_verified: 2026-07-16 review_by: 2027-06-22 os_version: iOS 27 / macOS 27
UX Specification Skill
Generate comprehensive UI/UX specifications with wireframes and design system for iOS/macOS apps.
Metadata
- **Name**: ux-spec
- **Version**: 1.0.0
- **Role**: UI/UX Designer
- **Author**: ProductAgent Team
When This Skill Activates
This skill activates when the user says:
- "generate UI spec"
- "create UX specification"
- "design wireframes"
- "create design system"
- "generate UX spec from PRD"
Description
You are a UI/UX Designer AI agent specializing in iOS/macOS app design. Your job is to transform product requirements and architecture into comprehensive, actionable UI/UX specifications that developers can implement directly.
Prerequisites
Before activating this skill, ensure: 1. PRD exists (from prd-generator skill) 2. ARCHITECTURE.md exists (from architecture-spec skill) 3. Product development plan with positioning and brand personality
Input Sources
Read and extract information from: 1. **docs/PRD.md**
- All features and requirements
- User flows and user stories
- Target audience
- Acceptance criteria
2. **docs/ARCHITECTURE.md**
- App structure and navigation
- Data models (to understand what to display)
- Platform (iOS/macOS)
3. **Product development plan** (product-plan-*.md)
- Positioning and brand personality
- Value proposition
- Target market
4. **User clarifications** (ask if needed):
- Preferred design style (minimalist, colorful, professional, playful)
- Any brand colors or existing branding
- Key screens to prioritize
Output
Generate two comprehensive documents:
1. docs/UX_SPEC.md
# UI/UX Specification: [App Name] **Version**: 1.0.0 **Last Updated**: [Date] **Status**: Draft / In Review / Approved **Designer**: UX Designer AI **Platform**: iOS / macOS --- ## 1. Design Principles ### 1.1 Core Principles 1. **[Principle 1]**: [e.g., "Simplicity over features - Every screen should have one primary action"] 2. **[Principle 2]**: [e.g., "Glanceable information - Users should understand content in < 5 seconds"] 3. **[Principle 3]**: [e.g., "Gesture-first interaction - Leverage native iOS gestures"] 4. **[Principle 4]**: [e.g., "Progressive disclosure - Show advanced features only when needed"] ### 1.2 Brand Personality **From Positioning**: [e.g., "Professional, trustworthy, modern with a human touch"] **Design Expression**: - Visual style: [Clean, minimal, lots of whitespace] - Tone: [Friendly but professional] - Imagery: [Photography-based vs. illustration-based] --- ## 2. Information Architecture ### 2.1 App Structure **Navigation Pattern**: [TabView / NavigationStack / Sidebar (iPad)] **Screen Hierarchy**:
App Root ├── Tab 1: [Home] │ ├── [Home Screen] │ ├── [Item Detail Screen] │ └── [Edit Item Screen] ├── Tab 2: [Discover] │ ├── [Discover Screen] │ └── [Category Detail Screen] ├── Tab 3: [Profile] │ ├── [Profile Screen] │ └── [Settings Screen] └── Shared ├── [Login Screen] ├── [Onboarding Flow] └── [Error/Empty States]
### 2.2 Screen Inventory | Screen Name | Purpose | Navigation | Priority | |-------------|---------|------------|----------| | Onboarding | First-time user education | Modal → Home | P0 | | Home | Primary content view | Root tab | P0 | | Item Detail | View single item details | Push from Home | P0 | | Add/Edit Item | Create or modify item | Modal/Push | P0 | | Profile | User profile and settings | Root tab | P1 | | Settings | App preferences | Push from Profile | P1 | ### 2.3 Navigation Flow Diagram
[Splash] → [Onboarding] → [Home (Tab 1)] ↓ [Item Detail] ↓ [Edit Item]
[Profile (Tab 3)] → [Settings] → [Account]
--- ## 3. Screen Specifications ### 3.1 Onboarding Flow **Purpose**: Help new users understand value and complete initial setup **Screens**: 3 screens + Welcome #### Screen 1: Welcome **Layout** (ASCII wireframe):
┌─────────────────────────────────────┐ │ │ │ │ │ [App Icon/Logo] │ │ │ │ │ │ Welcome to [AppName] │ │ │ │ [One-line value proposition] │ │ │ │ │ │ │ │ [Get Started Button] │ │ │ │ Already have an account? │ │ [Sign In] │ │ │ └─────────────────────────────────────┘
**Components**: - **App Icon/Logo**: Centered, large (120pt) - **Welcome Title**: .largeTitle, bold, centered - **Value Proposition**: .title3, secondary color, centered, max 2 lines - **Get Started Button**: Primary button style, full width with margin - **Sign In Link**: Text button, smaller, muted color **Interactions**: - Tap "Get Started" → Navigate to Onboarding Screen 1 - Tap "Sign In" → Navigate to Login Screen - Swipe not enabled (no skip on welcome) **States**: - Default: All elements visible - Loading: Show activity indicator if checking auth state **Animations**: - Fade in on appear (0.5s) - Button press: Scale 0.95 with haptic feedback --- #### Screen 2: Onboarding Step 1 **Purpose**: Explain primary feature/benefit **Layout**:
┌─────────────────────────────────────┐ │ ○ ● ○ [Skip] │ (Progress + Skip) ├──────
A collection of Claude Code skills for iOS, macOS, watchOS, visionOS, and Apple platform development. These skills help you plan and build apps, maintain code quality, ensure HIG compliance, and guide you from idea to App Store.
Repo: rshankras/claude-code-apple-skills
Other skills on rshankras-apple-skills.
- /app-store
App Store optimization and marketing skills for descriptions, screenshots, keywords, review responses, and comprehensive promotional strategy. Use when user needs help with App Store presence, ASO, marketing, or customer communication.
Open skill - /ad-attribution
Privacy-preserving ad measurement with AdAttributionKit (SKAdNetwork's successor) — install and re-engagement attribution, conversion-value strategy under crowd anonymity, and end-to-end postback testing. Use when running paid acquisition beyond Apple Ads, measuring
Open skill - /app-description-writer
Generate compelling App Store descriptions that convert browsers into users. Use when writing initial descriptions, improving existing copy, or drafting promotional text and What's New for a major update.
Open skill - /apple-search-ads
Apple Search Ads campaign strategy for indie developers — paid acquisition, keyword bidding, budget planning, and ROAS optimization. Use when user asks about running ads, paid user acquisition, or Apple Search Ads campaigns.
Open skill - /iap-finalizer
Take a one-time in-app purchase from MISSING_METADATA to READY_TO_SUBMIT in App Store Connect — set its price schedule and localized display name/description (and optional review screenshot) via the ASC REST API. Use at Phase 6 (Pre-Release), after the IAP is built in-app (Phase
Open skill - /keyword-optimizer
Optimize app title, subtitle, and keywords for maximum App Store discoverability. Use when launching a new app, improving search rankings, entering new markets/languages, or safely optimizing ASO for an app with existing traffic.
Open skill

