review-prompt_skill

Overview

This skill generates a smart App Store review prompt infrastructure in Swift with configurable trigger conditions, platform detection, and timing logic. It produces core files, integration snippets, and testing guidance for iOS and macOS apps distributed via the App Store. The goal is reliable, policy-compliant prompts while avoiding user annoyance.

How this skill works

The generator inspects project context (platform, distribution method, existing prompt code) and optionally asks whether the macOS app is distributed through the Mac App Store. It creates three core Swift files for logic, conditions, and persistence, places them in an appropriate folder based on project layout, and adds platform guards (macOS receipt checks). It exposes APIs to increment sessions, record positive actions, and request reviews when configured thresholds are met.

When to use it

• When you want to add in-app rating prompts using StoreKit (iOS/macOS App Store apps).
• When you need configurable trigger conditions (sessions, days since install, positive actions, feature usage).
• When you want safe timing logic and a cool-down to limit prompts per Apple guidelines.
• When you need a drop-in manager + storage files and integration examples for Swift apps.
• When you want to replace or improve an existing review prompt implementation.

Best practices

• Only use StoreKit reviews for App Store-distributed builds; offer an in-app feedback form for other distributions.
• Avoid prompting on first launch and never prompt immediately after a negative event.
• Use multi-condition triggers (session count + positive action) to improve conversion and reduce annoyance.
• Respect a cool-down (default 60 days) and Apple’s effective limit (~3 prompts/year).
• Include a debug override and a reset helper to test flows without waiting long periods.

Example use cases

• Increment session count on app launch and prompt after 5 sessions and a positive action.
• Prompt users after they use a key feature three times, with a 30–90 day cool-down.
• Integrate into App lifecycle (onAppear) to auto-track sessions and request review when appropriate.
• For macOS, check store receipt presence; otherwise open App Store review URL for direct distribution.
• Replace an existing simple requestReview call with this manager to add threshold logic and persistence.