Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jpavley/meta-loop-iosnpx agentmods add skills/jpavley/meta-loop-ios/view-specificationsWrote 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/jpavley/meta-loop-ios/view-specifications)<a href="https://agentmods.dev/skills/jpavley/meta-loop-ios/view-specifications"><img src="https://agentmods.dev/badge/skills/jpavley/meta-loop-ios/view-specifications/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/jpavley/meta-loop-ios/view-specifications"><img src="https://agentmods.dev/badge/skills/jpavley/meta-loop-ios/view-specifications.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.00021 | $0.03734 |
| Opus 5.5 | $0.00008 | $0.01494 |
| Sonnet 5.5 | $0.00004 | $0.00747 |
| Haiku 4.5 | $0.00002 | $0.00373 |
Grade A, and why
view-specifications 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 1mo 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 — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How to Write a View Spec
This guide teaches Claude how to write specification documents for SwiftUI views. Use this alongside the template section below as your reference.
Key Concepts
View Principles
- Composed from views — Views arrange reusable child views with appropriate spacing
- Callback navigation — Views receive closures (
onDismiss,onSelectItem); they don't know where to navigate - Data independent — Views accept only primitive inputs (IDs, strings, values) and derive display data themselves. A view should never require its caller's data model.
- Layout-aware — Every view provides portrait and landscape layouts where appropriate
- Animation coordination — Views assign animation offsets to each element
- Platform-agnostic requirements — All sections above Implementation Reference describe WHAT to build using prose, tables, and diagrams. Platform-specific code (Swift, Kotlin, etc.) belongs exclusively in Implementation Reference
View Scope: What to Think About vs. Trust the System
View specs should focus thinking on view-level concerns and trust other systems for everything else.
Requirements vs. implementation details: Specs capture what the view must do (requirements from the wireframe) — not how the code achieves it. If the wireframe says "scrolling text should not receive a visual effect," the spec states that requirement in the Notes section. It does not prescribe the layering approach, modifier chain, or rendering technique. The implementor decides the approach.
Platform-Agnostic Vocabulary
| Instead of... | Write... |
|---|---|
VStack / HStack |
"vertical stack" / "horizontal stack" |
ScrollView |
"scrollable area" |
struct MyView: View { let x: Type } |
Interface table (see Section 10) |
@State private var x: Type |
View State table (see Section 10) |
ForEach(items) { ... } |
"For each item in the collection" |
.cancellationAction / .bottomBar |
"top-left" / "bottom bar" |
Content VStack / Left VStack |
"Content column" / "Left column" |
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.
- 1mo ago First seen · 537 lines · 21 tokens per session scan A af6274f4923e
view-specifications is a skill published in the GitHub repository jpavley/meta-loop-ios (3 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 3,734 once invoked, about $0.0001 per session on Opus 5.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
ax-design-ref
Design API reference -- HIG color/background/material system, typography (San Francisco, text styles, Dynamic Type, tracking, leading), SF Symbols complete API (rendering modes, effects, UIKit equivalents, platform matrix), Liquid Glass adoption guide (controls, navigation, windows, icons, migration), accessibility…
ax-design
Apple Human Interface Guidelines and SF Symbols -- design decisions, rendering modes, symbol effects/animations, Draw animations (iOS 26), accessibility compliance, and defending HIG decisions in design reviews.
figma-a11y-annotations
Rules for generating accessibility annotations on iOS/iPadOS mobile designs in Figma. Enforces a bare-minimum annotation discipline, an iOS vocabulary instead of web ARIA terms, and exact grammar for names, control types, page titles, values, hints, headings, groups, and reading order. Never annotates visible text as…
iOS SwiftUI Accessibility
Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 24 WCAG criteria.
liquid-glass
Implement, migrate, review, and diagnose iOS Liquid Glass interfaces in SwiftUI and UIKit. Use for system chrome, custom glass effects, transitions, accessibility, and version-specific issues in native iOS apps.
motion-system
Give an iOS app one consistent motion language: a small set of named timings, springs and haptics in a single Motion.swift, derived from the app's own code and from real shipped apps with the same feel. Use when asked to make an app's animations consistent, create motion tokens or a motion system, clean up scattered…