IOS Taste
Designs iOS 18+ SwiftUI experiences with real taste — starting from user goals, not pixels. Use this skill whenever the user asks you to build SwiftUI views, screens, or experiences. Trigger when the user says "build a settings screen", "create a detail view", "design this properly", "I want this to feel like a native app", or any SwiftUI UI task. Also trigger when reviewing SwiftUI code for design quality, or when the user says the output "looks like a demo" or "feels generic." When building any user-facing SwiftUI view, lean toward triggering this skill.
Install
npx skills add pproenca/dot-skills --skill ios-tastegit clone --depth 1 https://github.com/pproenca/dot-skills.git /tmp/dot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/dot-skills/skills/.curated/ios-taste ~/.claude/skills/ios-tastePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# iOS Taste Taste doesn't start at the pixel level. It starts at "who is this person and what do they need?" The visual refinement is the LAST step. The first step is understanding the user's world deeply enough that the interface design feels inevitable — like it couldn't have been designed any other way. Your default mode skips straight to layout. It produces technically correct SwiftUI that looks generic because it was never grounded in a real person's needs. This skill changes the order of operations: think like a designer first, then write code. ## Phase 0: The 0.5-Second Test (ORIENT before everything) Before designing anything, answer ONE question: > **What does the user SEE in the first half-second — before they > read a single word?** This is not about content. It's about the SHAPE of the screen. Close your eyes and picture it. What dominates? - A **ring** at 40% of screen height? → Fitness dashboard - A **gradient card** with bold white text? → Music/travel/content - A **large number** floating in space? → Finance/health metric - A **grid of thumbnails**? → Photo/recipe/shopping collection - A **clean form** with generous space? → Settings/profile If your answer is "a List with rows of text" → STOP. That's a spreadsheet, not an app. Go back and find the visual shape. Write the 0.5-second answer as the FIRST line of the experience brief: ```swift // 0.5s: Four warm gradient cards stacked on black — a cookbook ```
Details
- Skill name
ios-taste- Repository
- pproenca/dot-skills
- Path
skills/.curated/ios-taste/SKILL.md- License
- MIT
- Repo updated
- 15 August 2026
FAQ
What does the IOS Taste skill do?
Designs iOS 18+ SwiftUI experiences with real taste — starting from user goals, not pixels. Use this skill whenever the user asks you to build SwiftUI views, screens, or experiences. Trigger when the user says "build a settings screen", "create a detail view", "design this properly", "I want this to feel like a native app", or any SwiftUI UI task. Also trigger when reviewing SwiftUI code for design quality, or when the user says the output "looks like a demo" or "feels generic." When building any user-facing SwiftUI view, lean toward triggering this skill.
How do I install the IOS Taste skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pproenca/dot-skills --skill ios-taste. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is IOS Taste popular?
It lives in pproenca/dot-skills, which has 228 GitHub stars and 19 forks.
Related skills
12 Factor App
228pproenca/dot-skills
The Twelve-Factor App methodology for building scalable, maintainable cloud-native applications. Use when designing backend services, APIs, microservices, or any software-as-a-service application. Triggers on deployment patterns, configuration management, process architecture, logging, and infrastructure decisions.
37signals Rails
228pproenca/dot-skills
37signals Rails coding principles and conventions from DHH, Jorge Manrubia, and the Fizzy/Basecamp/HEY codebase. This skill should be used when writing, reviewing, or refactoring Ruby on Rails code following the 37signals philosophy — vanilla Rails, CRUD controllers, rich domain models, concerns, no service objects, Hotwire, Turbo, Stimulus, Solid Queue, Solid Cache, Solid Cable, multi-tenancy, Minitest, custom auth, or DHH conventions.
Acceptance Pipeline Catalog
228pproenca/dot-skills
Use when implementing, reviewing, or debugging a Gherkin acceptance-test pipeline with mutation testing. Covers parser, JSON IR, generator, runtime, step handlers, test runner, mutator, value mutation rules, execution, result classification, reporting, project layout, conformance, and agent setup. Based on Uncle Bob's Acceptance Pipeline Specification. Trigger even when the user mentions Gherkin parsing, acceptance test generation, mutation testing for acceptance tests, or building a portable test pipeline.
IOS UI Refactor
228pproenca/dot-skills
Principal-level SwiftUI UI review and refactoring patterns for iOS 26 / Swift 6.2 clinic-architecture apps, grounded in Rams, Segall, and Edson principles. Use when auditing or improving existing SwiftUI screens, transitions, animations, and visual systems while preserving brand identity and respecting clinic Domain/Data/App boundaries.
IOS Storyboard
228pproenca/dot-skills
Legacy interoperability skill for Storyboard and Interface Builder maintenance in iOS 26 / Swift 6.2 clinic codebases. Use only for migration or maintenance of existing storyboard screens; not for new SwiftUI clinic feature development. Triggers on Auto Layout, segues, size classes, IB accessibility, storyboard merge conflicts, and storyboard-to-SwiftUI migration tasks.
IOS Xcode
228pproenca/dot-skills
Xcode setup and tooling guidance for iOS 26 / Swift 6.2 clinic modular MVVM-C projects covering project configuration, SwiftData container wiring, testing, debugging, profiling, and distribution workflows. Use when configuring App-target infrastructure or day-to-day tooling around clinic architecture modules.
Browse the most popular Claude skills, all mobile development skills, or write your own with the skills generator.