Ios Taste

This changes how Claude builds SwiftUI interfaces by forcing design thinking before code. Instead of jumping straight to List views and default layouts, it starts with a "0.5 second test" asking what visual shape dominates the screen, then works through who the user actually is, what they need to accomplish, and how the interface should make them feel. The workflow is deliberately ordered: understand the person and moment, map goals to features, choose components based on intent, then apply visual polish. It's opinionated about when to use sheets versus navigation, sliders versus steppers, and why most AI-generated UIs look generic. Use this when you want SwiftUI code that feels like a real app, not a settings demo.

skills.sh installs: 272
GitHub stars: 222
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pproenca/dot-skills --skill ios-taste --agent claude-code

Installs into .claude/skills of the current project.

Files

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.