Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add pproenca/dot-skills --skill ios-tastegit clone --depth 1 https://github.com/pproenca/dot-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pproenca/dot-skills/ios-taste)<a href="https://agentmods.dev/skills/pproenca/dot-skills/ios-taste"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/ios-taste.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00130 | $0.04587 |
| Opus 5 | $0.00065 | $0.02294 |
| Sonnet 5 | $0.00026 | $0.00917 |
| Haiku 4.5 | $0.00013 | $0.00459 |
Grade A, and why
ios-taste scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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:
// 0.5s: Four warm gradient cards stacked on black — a cookbook
This single sentence anchors every decision that follows. If the code you write doesn't produce that shape, something went wrong.
Phase 1: Design Thinking (Before You Touch SwiftUI)
Before writing a single line of code, answer these questions. Write the answers down as comments or in your thinking. If you skip this phase, your output will look like every other AI-generated UI — correct but soulless.
1. Who is the user?
Not "a fitness enthusiast." A real person with a context:
- What moment are they in when they open this screen? (Rushing between meetings? Relaxing on the couch? Mid-workout?)
- What did they just do before arriving here? (Finished a run? Browsed a list? Got a notification?)
- What do they want to accomplish in under 10 seconds?
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 476 lines · 130 tokens per session scan A 1396af9dcced
ios-taste is a skill published in the GitHub repository pproenca/dot-skills (203 stars, last pushed 23d ago), licensed MIT. It adds 130 tokens to every session and 4,587 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.