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 agentmods add rules/beettlle/pi-spine/ios-ui-development-focusgit clone --depth 1 https://github.com/beettlle/pi-spineWrote 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/rules/beettlle/pi-spine/ios-ui-development-focus)<a href="https://agentmods.dev/rules/beettlle/pi-spine/ios-ui-development-focus"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/ios-ui-development-focus.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02037 |
| Opus 5 | $0.00000 | $0.01019 |
| Sonnet 5 | $0.00000 | $0.00407 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
ios-ui-development-focus 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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Development Standards
CRITICAL: All UI and UX development must follow these standards
🛑 ZERO TOLERANCE: UI Anti-Patterns
-
Custom Sheets/Overlays:
- ❌ NEVER build custom
ZStackoverlays for modals. - ✅ ALWAYS use
.sheet(item:)with.presentationDetents(). - Reason: Custom overlays break keyboard handling and accessibility.
- ❌ NEVER build custom
-
"Sleep" Logic:
- ❌ NEVER use
Task.sleepto wait for data/player readiness. - ✅ ALWAYS use
await,AsyncStream, or Combine publishers.
- ❌ NEVER use
-
Text Blend Modes on Materials:
- ❌ NEVER use
.blendMode(.overlay)or other blend modes for text on translucent materials - ✅ ALWAYS use semantic foreground styles:
.foregroundStyle(.primary)or.foregroundStyle(.secondary) - ✅ ALWAYS use
.liquidText()modifier which implements semantic vibrancy correctly - Reason: HIG requires semantic vibrancy for text on materials. Blend modes create unpredictable contrast and violate WCAG accessibility standards.
- ❌ NEVER use
UI Development Guidelines
CRITICAL: All UI and UX features MUST follow Apple's Human Interface Guidelines (HIG) and Liquid Glass design system
- Always consult Apple HIG documentation (locally indexed) for component usage, design patterns, and accessibility requirements
- Integrate current Apple design materials (e.g. Liquid Glass per HIG) for new components when available on the project's deployment target; verify API names and availability in Apple docs for the SDK in use
Liquid Glass Design System (project + SDK)
CRITICAL: New UI must follow Apple's Human Interface Guidelines and current materials documentation (e.g. Liquid Glass where applicable).
Implementation Requirements
- Mandatory Usage (when supported): Use Liquid Glass (or successor) materials for new components when the project's minimum deployment target and SDK support them—use
#available/ project design-system wrappers when supporting multiple OS versions. - Materials: Use Apple's documented APIs for the active SDK; leverage customization options (clear, tinted, dark appearances) as documented.
- Accessibility: Test for readability, verify VoiceOver/Dynamic Type support, ensure WCAG contrast ratios
- Reference: Always consult https://developer.apple.com/documentation/technologyoverviews/liquid-glass and HIG for the SDK you build with.
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.
- 5d ago First seen · 187 lines · 0 tokens per session scan A b571fe7da547
ios-ui-development-focus is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,037 tokens. 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 cursor rules, from other repositories
nativescript
NativeScript best practices and patterns for mobile applications.
performance-optimization
// Use weak/unowned references appropriately class ViewController: UIViewController { private var timer: Timer?
webkit-browser
Cursor rule "webkit-browser" from duckduckgo/apple-browsers, covering webkit & browser development guidelines, webview configuration, basic webview setup, user scripts management and tab management.
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.