CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-layout-components

Build SwiftUI layouts using stacks, grids, lists, scroll views, forms, and controls. Covers VStack/HStack/ZStack, LazyVGrid/LazyHGrid, List with sections and swipe actions, ScrollView with ScrollPosition and scroll-driven reveal surfaces, Form with validation, Toggle/Picker/Slider, .searchable, and overlay patterns. Use when building data-driven layouts, collection views, paged detail reveals, settings screens, search interfaces, or transient overlay UI.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is dpearson2699/swift-ios-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured reference skill: executable snippets, clear container-selection guidance, a useful review checklist, and a clean one-level-deep reference bundle. The main improvement is trimming the long inline searchable/toast examples to keep the overview leaner.

Suggestions

Trim the .searchable section to the key modifiers (`.searchable`, `.searchScopes`, `.task(id:)` debounce) and move the full debounced-search view struct into references, shortening SKILL.md.

Shorten the toast overlay example to the `.overlay(alignment:)` + transition + auto-dismiss pattern and drop the surrounding struct boilerplate.

Tighten prose that restates code (e.g. 'Show a placeholder when search is empty. Debounce input...') into a single rule line or fold it into the Review Checklist.

DimensionReasoningScore

Conciseness

The body is largely lean — decision bullets, a controls table, and terse rules like 'Never place GeometryReader inside lazy containers' — with no basic-concept padding. However, the .searchable section inlines a full ~40-line view struct and a few prose sentences restate what adjacent code shows, so minor trimming is possible. Not 5 (some over-length examples); not 3 (no unnecessary explanations of things Claude already knows).

4 / 5

Actionability

Code is copy-paste-ready with real modifiers and APIs — '.scrollPosition($scrollPosition)' with 'scrollPosition.scrollTo(edge: .bottom)', '.task(id: searchQuery)' debounce, GridItem adaptive/flexible columns, '.safeAreaBar(edge:)', safeAreaInset — plus a control decision table and concrete do/don't rules. Fully executable examples cover the common cases, matching the anchor-5 example.

5 / 5

Workflow Clarity

As a pattern-reference skill, the selection workflow is well sequenced ('When to use which' bullets, per-section use guidance) and the Review Checklist plus Common Mistakes act as checkpoints for review tasks. Not 5 because there is no explicit multi-step execution flow with validation checkpoints; not 3 because the checklist and mistake list provide clear checkpoints and the sequences present are coherent.

4 / 5

Progressive Disclosure

Each section gives a concise inline pattern and then a clearly signaled one-level-deep pointer — 'See [references/grids.md](references/grids.md) for full grid patterns and design choices' — and all four referenced files (grids.md, list.md, scrollview.md, form.md) exist in the bundle. With a contents list and appropriately split content, this matches the anchor-5 structure exactly.

5 / 5

Total

18

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, API-specific capabilities paired with an explicit and natural 'Use when' trigger clause. The only weakness is minor boundary overlap with closely related SwiftUI sibling skills around overlays and presentation.

Suggestions

Clarify the overlay boundary in the description, e.g. 'Use for transient overlays (toasts, banners); use swiftui-navigation for sheets and full-screen presentation,' to reduce overlap with sibling skills.

Consider dropping or simplifying the jargon-adjacent phrase 'paged detail reveals' in favor of a more common user phrasing like 'scroll-driven or paged detail views.'

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities with named APIs — 'VStack/HStack/ZStack, LazyVGrid/LazyHGrid, List with sections and swipe actions, ScrollView with ScrollPosition and scroll-driven reveal surfaces, Form with validation, Toggle/Picker/Slider, .searchable, and overlay patterns' — covering essentially the full layout-component domain. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' rather than 4, which requires minor coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: 'what' via 'Build SwiftUI layouts using stacks, grids, lists, scroll views, forms, and controls' with component specifics, and 'when' via 'Use when building data-driven layouts, collection views, paged detail reveals, settings screens, search interfaces, or transient overlay UI.' This matches the anchor-5 example structure exactly; score 4 would require the 'when' clause to be less explicit.

5 / 5

Trigger Term Quality

Natural user phrases appear throughout: 'data-driven layouts, collection views, paged detail reveals, settings screens, search interfaces, or transient overlay UI', plus stack/grid/list/form/scroll view vocabulary. Coverage is comprehensive with synonyms; not 4 because no common natural phrasing for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

The SwiftUI layout-container niche is clear and mostly distinct, but 'transient overlay UI' and settings/form work sit near sibling skills (swiftui-navigation, swiftui-patterns referenced in the body), creating minor overlap risk. Not 5 because of that boundary ambiguity; not 3 because the core triggers (stacks, grids, lists, scroll views) are unambiguous.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dpearson2699/swift-ios-skills

Path

skills/swiftui-layout-components/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.