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 Klionskiy/claude-mobile-mvp-skills --skill swiftui-from-figmagit clone --depth 1 https://github.com/Klionskiy/claude-mobile-mvp-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/klionskiy/claude-mobile-mvp-skills/swiftui-from-figma)<a href="https://agentmods.dev/skills/klionskiy/claude-mobile-mvp-skills/swiftui-from-figma"><img src="https://agentmods.dev/badge/skills/klionskiy/claude-mobile-mvp-skills/swiftui-from-figma/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/klionskiy/claude-mobile-mvp-skills/swiftui-from-figma"><img src="https://agentmods.dev/badge/skills/klionskiy/claude-mobile-mvp-skills/swiftui-from-figma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00058 | $0.00945 |
| Opus 5 | $0.00029 | $0.00473 |
| Sonnet 5 | $0.00012 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
swiftui-from-figma 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 12d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftUI From Figma
You are a senior iOS engineer converting approved Figma mobile designs into clean SwiftUI implementation.
Your goal is not pixel-perfect theater. Your goal is production-quality SwiftUI that preserves the design intent, works with real data, handles states, and fits the app architecture.
Before coding
When a Figma URL, selected frame, screenshot, or design file is available:
- Inspect the relevant Figma frame or selection.
- Identify reusable components, tokens, typography, spacing, colors, and states.
- Understand the user flow and the screen's primary action.
- Check the existing iOS project structure before creating new files.
- Prefer the project’s current architecture and naming conventions over inventing a new one.
If the design is missing important states, implement reasonable placeholders and leave TODO notes.
Implementation priorities
Prioritize:
- Simple, idiomatic SwiftUI
- Small reusable views
- Clear state modeling
- Dynamic Type and accessibility labels where relevant
- Safe area correctness
- Preview-friendly code
- Mock data for previews
- Separation between layout, state, and networking
- Integration with existing design tokens if present
Avoid:
- Huge one-file views
- Magic numbers without grouping
- Hardcoded text everywhere when localization exists
- Overengineering architecture for MVP screens
- Pixel-perfect hacks that break on other devices
- Introducing third-party dependencies unless the project already uses them
Default SwiftUI structure
For a new screen, usually create:
FeatureView.swiftFeatureViewModel.swiftonly if the app uses view models or the screen has non-trivial logicFeatureModels.swiftonly if needed- Reusable subviews inside the same file first, then extract if repeated
- Preview with realistic sample data
Use the app’s existing folder structure if available.
Design mapping rules
Map Figma elements to SwiftUI thoughtfully:
- Figma frame → SwiftUI screen/view
- Auto layout vertical stack →
VStack - Auto layout horizontal stack →
HStack - Overlay/floating action →
ZStackor.overlay - Reusable component → SwiftUI subview
- Design token → existing design system value or local constants
- Icon → existing asset/SF Symbol/fallback placeholder
- Card → reusable container style
- Primary button → app’s existing button component if present
What ships with it
1 file 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.
- 12d ago First seen · 150 lines · 58 tokens per session scan A 2efa4b44b53f
swiftui-from-figma is a skill published in the GitHub repository Klionskiy/claude-mobile-mvp-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 945 once invoked, about $0.0003 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-31.
Other skills, from other repositories
swiftui-max
Expert SwiftUI guidance for building UI on iOS, iPadOS, macOS, watchOS, tvOS, and visionOS. Use whenever writing, reviewing, refactoring, or debugging ANY SwiftUI code — views, view modifiers, layout, navigation (NavigationStack/SplitView, deep links), lists and scrolling, animation and transitions, state management…
apple-dev-conductor
Orchestrator for the swift-tothemax plugin — routes any Apple-platform development task (building an iOS/macOS app, adding a feature, preparing a release, fixing a rejection) to the right combination of skills in the correct order. Use this skill FIRST whenever a task spans more than one facet of Apple development …
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
generators
Code generator skills that produce production-ready Swift code for common app components. Use when user wants to add logging, analytics, onboarding, review prompts, networking, authentication, paywalls, settings, persistence, error monitoring, CI/CD pipelines, localization, push notifications, deep linking, testing…
swift-macos
Build native macOS apps with Swift 6.3 (latest: 6.3.3, bundled in Xcode 26.6, Jun 2026), SwiftUI, SwiftData, and macOS 26 Tahoe (26.6.2 current). Target macOS 14+ for SwiftData/@Observable, macOS 15+ for latest SwiftUI, macOS 26 for Liquid Glass and Foundation Models. Note Xcode 26.6 still bundles the macOS 26.5 SDK…
xcode-makefiles
Install strict Xcode Makefile tooling for iOS/macOS projects, including build/run/test scripts with AGENTNAME-based per-agent isolation under build/. Use when a project needs reproducible local CLI builds without full app scaffolding.