Modern StoreKit 2 implementation for in-app purchases, subscriptions, and paywalls on iOS 16+.
Works with
Covers all product types (consumable, non-consumable, auto-renewable, non-renewing) with purchase flows, transaction verification, and entitlement checking
Provides SubscriptionStoreView and StoreView for building paywalls with automatic product loading, localized pricing, and purchase UI
Includes Transaction.updates listener pattern for handling mid-session changes, Family Sharing, Ask to
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstorekitExecute the skills CLI command in your project's root directory to begin installation:
Fetches storekit from dpearson2699/swift-ios-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate storekit. Access via /storekit in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
372
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
372
stars
Implement in-app purchases, subscriptions, and paywalls using StoreKit 2 on
iOS 26+. Use the modern Product, Transaction, StoreView, and
SubscriptionStoreView APIs. Avoid the older original StoreKit APIs
(SKProduct, SKPaymentQueue, SKStoreReviewController).
| Type | Enum Case | Behavior |
|---|---|---|
| Consumable | .consumable |
Used once, can be repurchased (gems, coins) |
| Non-consumable | .nonConsumable |
Purchased once permanently (premium unlock) |
| Auto-renewable | .autoRenewable |
Recurring billing with automatic renewal |
| Non-renewing | .nonRenewing |
Time-limited access without automatic renewal |
Define product IDs as constants. Fetch products with Product.products(for:).
import StoreKit
enum ProductID {
static let premium = "com.myapp.premium"
static let gems100 = "com.myapp.gems100"
static let monthlyPlan = "com.myapp.monthly"
static let yearlyPlan = "com.myapp.yearly"
static let all: [String] = [premium, gems100, monthlyPlan, yearlyPlan]
}
let products = try await Product.products(for: ProductID.all)
for product in products {
print("\(product.displayName): \(product.displayPrice)")
}
Call product.purchase(options:) and handle all three PurchaseResult cases.
Always verify and finish transactions.
func purchase(_ product: Product) async throws {
let result = try await product.purchase(options: [
.appAccountToken(userAccountToken)
])
switch result {
case .success(let verification):
let transaction = try checkVerified(verification)
await deliverContent(for: transaction)
await transaction.finish()
case .userCancelled:
break
case .pending:
// Ask to Buy or deferred approval -- do not unlock content yet
break
@unknown default:
break
}
}
func checkVerified<T>(_ result: VerificationResult<T>) throws -> T {
switch result {
case .verified(let value): return value
case .unverified(_, let error): throw error
}
}
Start at app launch. Catches purchases from other devices, Family Sharing changes, renewals, Ask to Buy approvals, refunds, and revocations.
@main
struct MyApp: App {
private var transactionListener: Task<Void, Error>?
init() {
transactionListener = listenForTransactions()
}
var body: some Scene {
WindowGroup { ContentView() }
}
func listenForTransactions() -> Task<Void, Error> {
Task.detached {
for await result in Transaction.updates {
guard case .verified(let transaction) = result else { continue }
await StoreManager.shared.updateEntitlements()
await transaction.finish()
}
}
}
}
Use Transaction.currentEntitlements for non-consumable purchases and active
subscriptions. Always check revocationDate.
@Observable
@MainActor
class StoreManager {
static let shared = StoreManager()
var purchasedProductIDs: Set<String> = []
var isPremium: Bool { purchasedProductIDs.contains(ProductID.premium) }
func updateEntitlements() async {
var purchased = Set<String>()
for await result in Transaction.currentEntitlements {
if case .verified(let transaction) = result,
transaction.revocationDate == nil {
purchased.insert(transaction.productID)
}
}
purchasedProductIDs = purchased
}
}
struct PremiumGatedView: View {
@State private var state: EntitlementTaskState<VerificationResult<Transaction>?> = .loading
var body: some View {
Group {
switch state {
case .loading: ProgressView()
case .failure: PaywallView()
case .success(let transaction):
if transaction != nil Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: storekit is the kind of skill you can hand to a new teammate without a long onboarding doc.
storekit has been reliable in day-to-day use. Documentation quality is above average for community skills.
storekit fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend storekit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
storekit has been reliable in day-to-day use. Documentation quality is above average for community skills.
storekit has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: storekit is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added storekit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in storekit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: storekit is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 57