paywall-generator

Generate StoreKit 2 paywall UI and purchase-management Swift files for iOS projects.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/venomez-viper/PathWise --skill paywall-generator-venomez-viper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paywall-generator
Source: https://github.com/venomez-viper/PathWise/tree/main/.claude/skills/generators/paywall-generator
Command: npx skills add https://github.com/venomez-viper/PathWise --skill paywall-generator-venomez-viper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a StoreKit 2 paywall and purchase-management scaffold for iOS apps, removing repetitive boilerplate and ensuring a clean, ready-to-integrate structure.

Core Features & Use Cases

  • Generates core files: StoreKitManager.swift, SubscriptionStatus.swift, PaywallView.swift, and SubscriptionButton.swift to manage products, purchases, and UI.
  • Creates a configuration layer: Products.swift with product IDs and constants for testing and integration.
  • Determines file placement based on project structure (Sources/, App/, or Store/) and outputs files in conventional locations to simplify integration.

Quick Start

Provide your project context and run the paywall-generator to generate core StoreKit files and integration scaffolding.

Frequently Asked Questions about paywall-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a StoreKit 2 paywall in SwiftUI?

Generating a StoreKit 2 paywall in SwiftUI is done by producing Swift files like PaywallView.swift and SubscriptionButton.swift that provide the UI and purchase-management scaffold for iOS apps.

What files are needed for a StoreKit 2 subscription flow?

A StoreKit 2 subscription flow requires core files like StoreKitManager.swift, SubscriptionStatus.swift, PaywallView.swift, SubscriptionButton.swift, and a Products.swift configuration layer for product IDs.

Can I use this scaffolding for iOS apps on older versions than iOS 15?

This scaffolding targets iOS apps using StoreKit 2, which requires iOS 15 or later. It is not designed for older iOS versions or legacy StoreKit implementations.

Where should I place StoreKit 2 purchase-management files in my iOS project?

StoreKit 2 purchase-management files are placed in conventional locations based on detected repository structure, such as Sources/, App/, or Store/ directories to simplify integration.

What is the best way to remove boilerplate when setting up an iOS paywall?

The best way to remove boilerplate when setting up an iOS paywall is to auto-generate a complete scaffold with core Swift files and configuration constants, ensuring a clean and ready-to-integrate structure.

Does the generated paywall scaffold include testing configuration?

Yes, the generated paywall scaffold includes a Products.swift configuration layer with product IDs and constants, along with a recommended testing and integration workflow for iOS apps.