Vladimir-BrVladimir-Br/swiftui-project-template/.cursor/rules/00-baseline.mdc

swiftui-project-template / rules

Cursor rule0 starsChanged 6 months agoMITView on GitHub

Project technical baseline — Swift, SwiftUI and iOS versions

We split this 00-baseline.mdc into the rules it gives an agent

8 rules. About 0 are common, 0 are distinctive, and 8 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Use @Observable macro for view models.
line 14
Very specific:
Use NavigationStack / NavigationSplitView.
line 15
Very specific:
Use .sheet(item:), .fullScreenCover(item:) with Identifiable payloads.
line 16
Very specific:
Use SwiftData (@Model, @Query, ModelContainer) for local persistence.
line 17
Very specific:
Use Swift Concurrency (async/await, actor, @MainActor).
line 18
Very specific:
Verify Apple APIs via the cupertino MCP — official Apple docs, HIG, Swift Evolution and samples.
line 27
Very specific:
Use the context7 MCP only for third-party libraries.
line 28
Very specific:
Check swiftui-pro skill references for deprecation.
line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

00-baseline.mdc

---
description: Project technical baseline — Swift, SwiftUI and iOS versions
alwaysApply: true
---

# Project Baseline

## Versions (TODO: adjust per project)
- iOS deployment target: **iOS 17.0+**
- Swift language version: **6**
- Xcode minimum: **16**

## SwiftUI API baseline
- Use `@Observable` macro for view models. NOT `ObservableObject` + `@Published`.
- Use `NavigationStack` / `NavigationSplitView`. NOT `NavigationView`.
- Use `.sheet(item:)`, `.fullScreenCover(item:)` with `Identifiable` payloads.
- Use SwiftData (`@Model`, `@Query`, `ModelContainer`) for local persistence.
- Use Swift Concurrency (`async/await`, `actor`, `@MainActor`). Forbidden: GCD, completion handlers in new code.

## Forbidden in this project
- UIKit imports — only as a last resort via `UIViewRepresentable` for missing SwiftUI capability.
- Force unwraps (`!`) and force casts (`as!`) — except `@IBOutlet`-style cases and tests.
- Deprecated APIs from iOS 16 and earlier (e.g., `NavigationView`).
- The legacy single-parameter `.onChange(of:) { newValue in ... }` — deprecated in iOS 17. Use either the zero-parameter form `.onChange(of:) { /* code */ }` or the two-parameter form `.onChange(of:) { oldValue, newValue in ... }`.

## When uncertain about an API
- Verify Apple APIs via the `cupertino` MCP — official Apple docs, HIG, Swift Evolution and samples.
- Use the `context7` MCP only for third-party libraries.
- Check `swiftui-pro` skill references for deprecation.

Download now (ZIP)

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 repository3 other files it gives its agents.
- .cursor/rules/10-architecture.mdcCursor rule
- .cursor/rules/20-api.mdcCursor rule
- .cursor/rules/30-ai-marker.mdcCursor rule

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free