agentleFS
moasqmoasq/ios-dev-agent/.cursor/rules/pricing-display.mdc

ios-dev-agent / rules

Cursor rule4 starsChanged 6 months agoMITView on GitHub

iOS development rule

The file

We split this pricing-display.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:

    Use these rules for an app's own subscriptions and in-app purchases.

    line 9
  2. Distinctive:

    Before submission, scan Swift source for:

    line 45
  3. Distinctive:

    All matches must be derived from StoreKit/RevenueCat data or replaced with generic copy.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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
pricing-display.mdc
---
description: iOS development rule
globs: "**/*.swift"
alwaysApply: true
---

# Pricing Display Rules

Use these rules for an app's own subscriptions and in-app purchases.

## Source Of Truth

Paywall, upgrade prompts, onboarding price mentions, and subscription metadata must use live StoreKit or RevenueCat data. Do not hardcode price, period, trial duration, or savings claims in Swift.

## Banned Patterns

```swift
let yearlyPrice: Decimal = 29.99
Text("$29.99")
Text("$2.50 / month")
Text("Save 60%")
Text("7-day free trial")
Text("Was $59.99").strikethrough()
String(format: "$%.2f / mo", monthly)
```

## Allowed Patterns

```swift
Text(package.storeProduct.localizedPriceString)

if let trial = package.storeProduct.freeTrialDescription {
    Text(trial)
}

if let savings = annual.savingsPercent(comparedTo: weekly) {
    Text("Save \(savings)%")
}
```

The helper methods may compute values from StoreKit/RevenueCat package data, but the view layer should not invent pricing strings.

## Release Audit

Before submission, scan Swift source for:

- Numeric price literals.
- Hardcoded currency symbols in paywall copy.
- Hardcoded `/mo`, `/month`, `/yr`, `/year`, `/week` labels attached to prices.
- Hardcoded savings percentages.
- Hardcoded trial durations.

All matches must be derived from StoreKit/RevenueCat data or replaced with generic copy.

## Metadata Copy

App Store metadata should avoid price literals unless the team is prepared to verify and update them before every release. Prefer generic copy such as "Choose annual for the best per-month value" over specific numbers.

## Apple Review

Auto-renewing subscriptions must clearly disclose subscription length, price, and renewal terms. The safest implementation is to display the values returned by StoreKit or RevenueCat for the current storefront.

Download now (ZIP)

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.