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/madebyaris/rakitui-ai/swift-developmentgit clone --depth 1 https://github.com/madebyaris/rakitui-aiWrote 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/madebyaris/rakitui-ai/swift-development)<a href="https://agentmods.dev/rules/madebyaris/rakitui-ai/swift-development"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/swift-development.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.04166 |
| Opus 5 | $0.00000 | $0.02083 |
| Sonnet 5 | $0.00000 | $0.00833 |
| Haiku 4.5 | $0.00000 | $0.00417 |
Grade A, and why
swift-development 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 4d 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 — 777 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift Development Patterns
Modern Swift patterns for iOS, macOS, and Apple platform development.
CRITICAL: Agentic-First Swift/iOS Development
Pre-Development Verification (MANDATORY)
Before writing ANY Swift/iOS code:
1. CHECK XCODE/SWIFT AVAILABILITY
→ run_terminal_cmd("swift --version")
→ run_terminal_cmd("xcodebuild -version")
→ run_terminal_cmd("xcrun simctl list") # Available simulators
2. VERIFY CURRENT VERSIONS (use web_search)
→ web_search("Swift version December 2024")
→ web_search("iOS SDK version December 2024")
→ web_search("Xcode latest version 2024")
3. CHECK EXISTING PROJECT
→ Does *.xcodeproj exist? If yes, use Xcode to modify!
→ Read Package.swift if it's a Swift Package
→ NEVER manually edit project.pbxproj files!
⚠️ CRITICAL: Xcode Project Files
NEVER manually create or edit:
*.xcodeproj/project.pbxproj- This is a complex binary-like file managed by Xcode*.xcworkspace/contents.xcworkspacedata*.xcodeproj/xcuserdata/*
These files MUST be created through:
- Xcode IDE (Create New Project)
swift package initfor Swift Package Manager projectsxcodebuildcommands for CI/CD
Why? The .pbxproj file has:
- UUID references that must be consistent
- Specific formatting Xcode expects
- Build settings that are complex to replicate
- Manual creation will result in CORRUPTED projects
CLI-First Swift Development
For Swift Packages (preferred for libraries):
# Create new package (NEVER manually create Package.swift)
swift package init --type library
swift package init --type executable
swift package init --type tool
# Add dependencies
# Edit Package.swift, then:
swift package resolve
swift build
swift test
For iOS/macOS Apps:
# You MUST use Xcode to create .xcodeproj
# There is NO CLI equivalent for full iOS projects
# Build from command line (project must exist)
xcodebuild -project MyApp.xcodeproj -scheme MyApp -sdk iphonesimulator build
# Run tests
xcodebuild test -project MyApp.xcodeproj -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 15'
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.
- 4d ago First seen · 777 lines · 0 tokens per session scan A 56cc3f50f122
swift-development is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,166 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
swiftui-guidelines-cursorrules-prompt-file
Cursor rule "swiftui-guidelines-cursorrules-prompt-file" from ItamarZand88/awesome-agent-conventions, covering role & perspective, code generation guidelines, 1. general principles, 2. swiftui best practices (performance first) and 3. swift 6 concurrency & threading.
android-jetpack-compose-cursorrules-prompt-file
description: "Cursor rules for Android development with Jetpack Compose integration." globs: / alwaysApply: false.
errors
Please don't fix any code errors unless reported by XcodeBuildMCP server tool responses.
trove-swift
Swift 6 and SwiftUI coding conventions for iOS development. Auto-activates when working with Swift files. Covers @Observable, async/await, NavigationStack, Swift Testing, and accessibility.
figma-ios-codegen-workflow
Figma → iOS UIKit codegen workflow. Apply when the user mentions figma / figma.com and wants to convert or generate Swift/UIKit code. Enforces: data package first (preload CLI), bindings maps, full node coverage, audit.json, then coverage + screenshot verification. Do NOT load for unrelated tasks.
AIRules
NexusLink MCP four-step workflow and prohibitions (copy to project .cursor/rules/ and fill the project-specific section).