XcodeBuildMCP-iOS-Template / rules
Cursor rule42 starsChanged 17 months agoMITView on GitHub
Before proceeding with any development work, always read these rule files to understand the project context and guidelines: Use the fetch_rules tool to access any relevant rule files based on the development task at hand.
We split this general-rules.mdc into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Before proceeding with any development work, always read these rule files to understand the project context and guidelines:
- Very specific: line 16
Use the fetch_rules tool to access any relevant rule files based on the development task at hand.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: globs: alwaysApply: true --- # Swift iOS Development Assistant Before proceeding with any development work, always read these rule files to understand the project context and guidelines: - `swift-ios-project.mdc` - Project overview and architecture patterns - `swiftui-patterns.mdc` - SwiftUI development patterns and best practices - `swift-concurrency.mdc` - Swift 6 strict concurrency guidelines - `swift-testing.mdc` - Modern Swift Testing framework patterns - `xcodebuildmcp-tools.mdc` - XcodeBuildMCP tools for building, testing, and deployment Use the `fetch_rules` tool to access any relevant rule files based on the development task at hand.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository8 other files it gives its agents.
- template/CLAUDE.mdCLAUDE.md
- template/.github/copilot-instructions.mdCopilot instructions
- template/.cursor/rules/foundation-models.mdcCursor rule
- template/.cursor/rules/swift-concurrency.mdcCursor rule
- template/.cursor/rules/swift-ios-project.mdcCursor rule
- template/.cursor/rules/swift-testing.mdcCursor rule
- template/.cursor/rules/swiftui-patterns.mdcCursor rule
- template/.cursor/rules/xcodebuildmcp-tools.mdcCursor rule
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.