agentleFS
Sign inStart free
Vladimir-BrVladimir-Br/swiftui-project-template/.cursor/rules/30-ai-marker.mdc

swiftui-project-template / rules

Cursor rule0 starsChanged 6 months agoMITView on GitHub

Convention for marking AI-generated code for later human review

We split this 30-ai-marker.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you (the AI assistant) create a brand-new Swift file from scratch or substantially rewrite the body of a view / view model / service, …

    line 8
  2. Distinctive:

    DO NOT add when:

    line 25
  3. Distinctive:

    Use a real ISO date (today's date), not a placeholder.

    line 31

≈ “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
30-ai-marker.mdc
---
description: Convention for marking AI-generated code for later human review
alwaysApply: true
---

# AI-generated code marker

When you (the AI assistant) **create a brand-new Swift file from scratch** or **substantially rewrite the body of a view / view model / service**, prepend this header right after the file copyright/import block:

```swift
// MARK: - AI-Generated, needs human review
//
// Created by Cursor on YYYY-MM-DD
// Reason: <short reason — "initial implementation", "refactor to IVO", etc.>
//
// TODO: review carefully, then remove this header.
```

## When to add the marker (by action, not by percentage)
ADD when:
- Creating a new file from scratch.
- Rewriting the whole `var body` of a SwiftUI view.
- Replacing the bulk of a view model / service implementation.

DO NOT add when:
- Fixing typos or renaming symbols.
- Adding 1–5 lines.
- Tweaking a single modifier or property.

## Rules
- Use a real ISO date (today's date), not a placeholder.
- The user uses `rg "AI-Generated, needs human review"` to track unreviewed files.

## Why
The developer is learning iOS and explicitly wants to avoid blind "vibe coding".
This marker is a personal technical-debt tracker, not a security feature.

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.

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