Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, and iOS 26+ Liquid Glass adoption.
SkillScore100Maintained
Automatic
◆Frontend / UI pack
Last verified 8/28/2026
What it changes
Passed 22 of 22 test cases with the skill, and 19 of 22 without it.
Without skill86%
With skill100%
Checks it passed that the model alone missed
Declares the subview storage using `@ViewBuilder let content: Content`.
Wraps the adjacent glass button elements inside a `GlassEffectContainer`.
Avoids initializing `@State` wrapper properties from passed arguments inside `init`.
and 1 more in the full report
3 fixed19 passed either way0 still failing0 broke
Pass-rate lift
+14 pp
Tokens
+137%
Agent turns
0%
Response time
-18%
Model gemini-3.6-flashMeasured 8/28/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
I am explicitly implementing iOS 26 visual glass styling for a toolbar containing multiple adjacent glass buttons. Which container view should wrap these adjacent glass elements?
What was checked, without and with the skill
Checked
Without skill
With skill
Wraps the adjacent glass button elements inside a `GlassEffectContainer`.
Missed
Passed
case-17 · gemini-3.6-flash · 8/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md247 linessingle file
SwiftUI Expert Skill
When to Use
You are building, reviewing, or refactoring SwiftUI code and need current best practices.
The task involves state management, view composition, performance, accessibility, or iOS 26+ Liquid Glass adoption.
You need a fact-based SwiftUI guidance layer without locking into a specific application architecture.
Overview
Use this skill to build, review, or improve SwiftUI features with correct state management, optimal view composition, and iOS 26+ Liquid Glass styling. Prioritize native APIs, Apple design guidance, and performance-conscious patterns. This skill focuses on facts and best practices without enforcing specific architectural patterns.
Workflow Decision Tree
1) Review existing SwiftUI code
First, consult references/latest-apis.md to ensure only current, non-deprecated APIs are used
Check property wrapper usage against the selection guide (see references/state-management.md)
Verify view composition follows extraction rules (see references/view-structure.md)
Check performance patterns are applied (see references/performance-patterns.md)
Verify list patterns use stable identity (see references/list-patterns.md)
Check animation patterns for correctness (see references/animation-basics.md, references/animation-transitions.md)
Review accessibility: proper grouping, traits, Dynamic Type support (see references/accessibility-patterns.md)
Inspect Liquid Glass usage for correctness and consistency (see references/liquid-glass.md)
Validate iOS 26+ availability handling with sensible fallbacks
2) Improve existing SwiftUI code
First, consult references/latest-apis.md to replace any deprecated APIs with their modern equivalents
Audit state management for correct wrapper selection (see references/state-management.md)
Extract complex views into separate subviews (see references/view-structure.md)
Refactor hot paths to minimize redundant state updates (see references/performance-patterns.md)
Ensure ForEach uses stable identity (see references/list-patterns.md)
Improve animation patterns (use value parameter, proper transitions, see references/animation-basics.md, references/animation-transitions.md)
Improve accessibility: use Button over tap gestures, add @ScaledMetric for Dynamic Type (see references/accessibility-patterns.md)
Suggest image downsampling when UIImage(data:) is used (as optional optimization, see references/image-optimization.md)
Adopt Liquid Glass only when explicitly requested by the user
3) Implement new SwiftUI feature
First, consult references/latest-apis.md to use only current, non-deprecated APIs for the target deployment version
Design data flow first: identify owned vs injected state (see references/state-management.md)
Structure views for optimal diffing (extract subviews early, see references/view-structure.md)
Keep business logic in services and models for testability (see references/layout-best-practices.md)
Use correct animation patterns (implicit vs explicit, transitions, see references/animation-basics.md, references/animation-transitions.md, references/animation-advanced.md)
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
Access a collection of open-source molecular design and structural biology tools on the Tamarind Bio platform, via its REST API or MCP server — no local GPUs required. Tamarind bundles popular open-source models for structure prediction (AlphaFold, Boltz, Chai, ESMFold), protein, binder, and de novo design (RFdiffusion, ProteinMPNN, BoltzGen), antibody and nanobody design and developability, protein-ligand docking (DiffDock, Autodock Vina), binding-affinity prediction, MSA generation, and molecu