More screenshots

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Subscription App UI Architect

    2

    Designs complete, transparent, accessible, and implementation-ready subscription experiences for SaaS products, mobile apps, AI tools, membership platforms, and digital services. Covers pricing, plan comparison, trials, paywalls, feature gates, usage limits, checkout, upgrades, downgrades, billing dashboards, failed-payment recovery, cancellation, ethical retention offers, expiration, reactivation, analytics, QA, and developer handoff.

    $7.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    Subscription App UI Architect

    Subscription App UI Architect

    Example session with this skill installed

    Product name
    NovaMind AI

    Product type
    Cross-platform AI productivity assistant

    Platforms
    Responsive web application
    iOS application
    Android application

    Primary users
    Freelancers
    Small-business owners
    Content creators
    Consultants
    Knowledge workers
    Small teams

    Primary user job
    Use AI to research, write, summarize, organize information, and automate repetitive knowledge work.

    Primary business goal
    Increase qualified trial starts, improve trial-to-paid conversion, reduce payment-related support requests, and make cancellation more transparent.

    Subscription model
    Freemium with three paid plans

    Plans
    Free
    Professional
    Team
    Enterprise

    Billing cadence
    Monthly and annual for Professional and Team
    Enterprise uses custom contracts

    Free plan
    Limited AI requests
    Limited file uploads
    Basic models
    Single user
    No advanced automation

    Professional plan
    Higher AI usage
    Advanced models
    Larger file limits
    Automation
    Priority processing
    Single user

    Team plan
    Professional features
    Multiple seats
    Shared workspace
    Admin controls
    Centralized billing
    Team usage reporting

    Enterprise plan
    Custom usage
    Single sign-on
    Advanced administration
    Security review
    Custom support
    Contract billing

    Exact limits
    Require verification

    Trial
    Professional trial may be available
    Exact eligibility, duration, payment-method requirement, and post-trial billing require verification

    Primary conversion
    Paid Professional subscription

    Secondary conversions
    Annual billing
    Team-plan upgrade
    Additional seats
    Reactivation

    Pricing-page problems
    Annual billing displays only a monthly equivalent.
    The total annual charge is visually weak.
    The recommended plan badge is overused.
    Feature differences are difficult to scan.
    Mobile users must horizontally scroll through the comparison table.
    Enterprise appears as a normal self-service checkout plan.
    Currency is not always visible.
    The current plan is not identified for signed-in users.

    Paywall problems
    The paywall appears before users see an AI result.
    The close control is visually weak.
    The same paywall appears repeatedly.
    The headline emphasizes limitations rather than value.
    Users are not returned to the gated feature after upgrading.

    Usage-limit problems
    Users receive no warning before reaching the AI limit.
    Usage resets are unclear.
    The app shows “Limit reached” without explaining the next reset.
    Team administrators cannot see member usage.

    Checkout problems
    Trial terms are incomplete.
    Amount due now and future charge are not separated.
    Annual billing is not clearly explained.
    Payment errors are generic.
    Repeated taps can create duplicate requests.
    Uncertain payment results appear as failures.

    Billing-dashboard problems
    Users cannot immediately find the renewal date.
    The billing source is not shown.
    App-store subscribers see web cancellation instructions.
    Invoices are difficult to find.
    Seat usage is separated from billing.
    Upcoming charges are missing.
    Payment-failure status appears only as a small banner.

    Cancellation problems
    Cancellation is hidden under Contact Support.
    The flow uses three retention screens.
    The final cancellation action is visually secondary.
    Feature loss and remaining access are unclear.
    Users cannot downgrade before cancelling.
    Cancellation reasons are mandatory.

    Retention options
    Downgrade to Free
    Switch from Team to Professional where eligible
    Reduce seats
    Pause may be considered but is not confirmed
    Contact support
    Continue cancellation

    App-store billing
    iOS subscriptions may be Apple managed.
    Android subscriptions may be Google Play managed.
    Web subscriptions are managed by the web payment provider.
    Entitlement synchronization requires verification.

    Markets
    United States
    Canada
    United Kingdom
    European Union
    Australia
    Brazil
    Japan

    Currencies
    USD
    CAD
    GBP
    EUR
    AUD
    BRL
    JPY

    Accessibility target
    WCAG 2.2 AA-oriented implementation review
    iOS and Android accessibility review
    Keyboard navigation
    Screen-reader support
    200% zoom
    Large text
    Reduced motion
    No color-only plan states

    Localization
    English
    German
    French
    Spanish
    Portuguese
    Japanese
    Right-to-left support planned later

    Technology stack
    Next.js
    React
    TypeScript
    Tailwind CSS
    shadcn/ui
    React Native
    Existing design system
    Web payment provider
    Apple subscription integration
    Google Play billing integration

    Need output
    Complete subscription UI architecture
    Subscription-state model
    Pricing-page redesign
    Plan-comparison system
    Monthly and annual billing presentation
    Trial flow
    Paywall system
    Feature-gate rules
    Usage-limit states
    Upgrade flow
    Downgrade flow
    Seat-management flow
    Subscription checkout
    Payment-state architecture
    Billing dashboard
    Invoice experience
    Failed-payment recovery
    Grace-period state
    Cancellation flow
    Ethical retention offers
    Expiration
    Reactivation
    Restore-purchase flow
    Cross-platform entitlement architecture
    Accessibility
    Localization
    Analytics event map
    Experiment roadmap
    Developer handoff
    Acceptance criteria
    Regression tests
    QA checklist
    Risk assessment

    Need variations
    Conversion-Focused Subscription Experience
    Trust-First Subscription Experience
    Mobile-First AI Subscription Experience

    Special constraints
    Do not invent prices.
    Do not invent usage limits.
    Do not invent trial duration.
    Do not invent proration.
    Do not invent refunds.
    Do not invent payment-retry timing.
    Do not present uncertain payments as failed.
    Do not hide annual charges.
    Do not hide cancellation.
    Do not use false urgency.
    Do not force users through retention offers.
    Do not encourage duplicate subscriptions.
    Do not weaken accessibility for conversion.

    • Read your context and instructions
    • Compiled the subscription app ui

    === SUBSCRIPTION APP UI ARCHITECTURE ===

    Product
    NovaMind AI

    Platforms
    Responsive web, iOS, and Android

    Subscription Model
    Freemium with Professional, Team, and Enterprise paid options

    Primary Conversion
    Qualified Professional subscription

    === EXECUTIVE SUMMARY ===

    NovaMind AI has a commercially viable subscription structure, but the current interface creates preventable uncertainty at several high-value moments.

    The most important problems are

    1. Annual billing obscures the full amount charged.
    2. The pricing comparison is difficult to scan.
    3. Mobile plan comparison requires horizontal scrolling.
    4. The paywall appears before sufficient value.
    5. Usage limits are communicated too late.
    6. Trial terms are incomplete.
    7. Uncertain payments are presented as failures.
    8. Billing source is not visible.
    9. App-store subscribers receive incorrect management guidance.
    10. Seat usage and workspace billing are separated.
    11. Payment-failure status lacks prominence.
    12. Cancellation is hidden and burdened with repeated retention screens.
    13. Cross-platform entitlement conflicts are not explained.

    Recommended subscription journey

    Product Value
    → Contextual Feature Gate
    → Plan Recommendation
    → Transparent Plan Review
    → Trial or Subscription Checkout
    → Payment Processing
    → Entitlement Confirmation
    → Return to Intended Feature
    → Billing Dashboard
    → Renewal, Upgrade, Downgrade, Cancellation, or Reactivation

    === SUBSCRIPTION STATE MODEL ===

    Free

    Access
    Verified free features and limits

    Primary Action
    Compare Plans

    Trial Eligible

    Access
    Free-plan access

    Primary Action
    Start Verified Trial

    Trial Active

    Display

    • Trial plan
    • Trial status
    • Verified end date
    • Included features
    • Usage
    • Future billing terms
    • Cancellation access

    Trial Expiring

    Display

    • Verified expiration or billing event
    • Current access
    • Future access
    • Payment method
    • Cancellation access

    Active

    Display

    • Current plan
    • Billing source
    • Cadence
    • Renewal or end date
    • Payment method
    • Usage
    • Seats
    • Invoices
    • Plan management

    Payment Failed

    Display

    • Affected subscription
    • Current access
    • Verified recovery action
    • Payment method
    • Support

    Cancelled With Access Remaining

    Display

    • Cancellation confirmed
    • Access end date
    • Available features
    • Reactivation option

    Expired

    Display

    • Current available access
    • Data state where verified
    • Reactivation
    • Export where supported

    === PRICING-PAGE ARCHITECTURE ===

    Hero

    Headline
    Choose the AI Workspace That Fits Your Work

    Supporting Copy
    Compare verified features, usage, collaboration, and billing options.

    Billing Control
    Monthly
    Annual

    Annual Presentation

    Show

    • Full annual amount charged
    • Currency
    • Billing cadence
    • Verified monthly equivalent
    • Verified savings where approved

    Do Not
    Use the monthly equivalent as the only prominent price.

    Plan Cards

    Free
    For individuals exploring NovaMind AI

    Professional
    For individuals using AI throughout their workday

    Team
    For teams sharing AI workflows and administration

    Enterprise
    For organizations requiring custom security, access, and support

    Enterprise Action
    Contact Sales

    Do not route Enterprise through standard self-service checkout unless supported.

    Signed-In State
    Identify the current plan and disable misleading purchase actions.

    === PLAN COMPARISON ===

    Primary Decision Categories

    Core AI Access
    Advanced Models
    Usage
    File Uploads
    Automation
    Collaboration
    Administration
    Security
    Support
    Billing

    Status Labels

    Included
    Limited
    Unavailable
    Available as Add-On
    Enterprise Only
    Requires Verification

    Mobile Pattern

    Use stacked plan summaries with expandable feature groups.

    Do not require page-level horizontal scrolling.

    Accessibility

    Do not rely only on checkmarks or color.
    Include visible text labels for every feature state.

    === TRIAL FLOW ===

    Entry
    Pricing page
    Contextual paywall
    Upgrade screen

    Required Trial Summary

    Plan
    Professional

    Trial Duration
    Verified value

    Payment Method
    Required or Not Required according to verified rules

    Amount Due Now
    Verified value

    Future Charge
    Verified price and cadence

    Billing Start
    Verified date or rule

    Cancellation
    Explain access and management path

    Flow

    Trial Summary
    → Account Verification
    → Payment Method Where Required
    → Final Review
    → Start Trial
    → Entitlement Confirmation
    → Return to Intended Feature

    Do not start the trial until the verified billing and entitlement systems confirm success.

    === PAYWALL SYSTEM ===

    Trigger
    A user selects a premium feature after receiving meaningful product value.

    Headline
    Unlock Advanced AI Workflows

    Supporting Copy
    Use advanced models, higher limits, larger files, and automation with the verified Professional plan.

    Display

    • Gated feature
    • Current plan
    • Recommended plan
    • Key value
    • Verified price and cadence
    • Trial availability
    • Close action
    • Compare Plans
    • Upgrade

    Frequency
    Do not repeatedly display the same full-screen paywall within an excessive interval.

    State Preservation
    Preserve the user's intended feature and return after successful entitlement confirmation.

    Do Not

    • hide the close control
    • use false countdowns
    • imply unavailable discounts
    • describe the user as losing work
    • repeat the paywall after dismissal without context

    === FEATURE-GATE SPECIFICATION ===

    Feature
    Advanced Automation

    Current Plan
    Free

    Required Plan
    Professional

    Trigger
    User selects Create Automation

    Primary Action
    View Professional Plan

    Secondary Action
    Continue With Free Features

    After Upgrade
    Return to Create Automation

    Analytics
    feature_gate_viewed
    feature_gate_upgrade_started
    feature_gate_return_completed

    === USAGE-LIMIT ARCHITECTURE ===

    Usage Stages

    Normal
    Show current usage in account context.

    Approaching Limit
    Notify before the final allowance is consumed.

    Limit Reached
    Explain the current limit, reset rule, and available actions.

    Reset Pending
    Show the verified reset date or rule.

    Team Overage
    Show organization-level usage only to authorized roles.

    Usage Message

    You have used [verified amount] of your [verified limit] for this billing period.

    Required

    • current usage
    • limit
    • remaining usage
    • reset date or rule
    • upgrade option
    • support where appropriate

    Do not display estimated usage as final billing.

    === UPGRADE FLOW ===

    Current Plan
    Free

    Target Plan
    Professional

    Review

    • features gained
    • usage change
    • billing cadence
    • price
    • currency
    • amount due now
    • future charge
    • trial context
    • payment method
    • cancellation access

    Flow

    Upgrade Entry
    → Plan Review
    → Payment
    → Processing
    → Entitlement Confirmation
    → Return to Intended Feature

    Uncertain Payment
    Do not grant or deny access until entitlement status is confirmed.

    === DOWNGRADE FLOW ===

    Current Plan
    Team

    Target Plan
    Professional

    Review

    • collaboration loss
    • seat impact
    • workspace impact
    • usage impact
    • automation impact
    • effective date
    • billing impact
    • data behavior

    Conflict
    If multiple active members remain, explain the verified seat-resolution process.

    Do not silently remove members or data.

    === SEAT MANAGEMENT ===

    Display

    • purchased seats
    • assigned seats
    • available seats
    • pending invitations
    • current price
    • cadence
    • billing owner

    Add Seats
    Show quantity, price impact, effective date, and verified billing calculation.

    Remove Seats
    Explain whether removal is immediate or scheduled and how assigned members are handled.

    Do not invent proration.

    === SUBSCRIPTION CHECKOUT ===

    Required Summary

    Plan
    Professional

    Billing
    Monthly or Annual

    Price
    Verified amount

    Currency
    Verified currency

    Amount Due Now
    Verified amount

    Future Charge
    Verified amount and cadence

    Trial
    Verified terms

    Payment Method
    Selected method

    Cancellation
    Visible access

    Final Action
    Accurately describe the commitment.

    Payment States

    • Validating
    • Ready
    • Submitting
    • Authentication Required
    • Processing
    • Completed
    • Declined
    • Failed
    • Cancelled
    • Uncertain
    • Duplicate Prevented

    === UNCERTAIN PAYMENT ===

    Heading
    Confirming Your Subscription

    Message
    The final payment status has not been confirmed. Do not submit another payment while NovaMind checks the transaction.

    Required System Behavior

    • preserve transaction reference
    • prevent duplicate submission
    • check payment status
    • check entitlement status
    • preserve checkout context
    • display final result when confirmed
    • provide support after the verified threshold

    Do not show Payment Failed without confirmed failure.

    === BILLING DASHBOARD ===

    Primary Summary

    • current plan
    • status
    • billing source
    • price
    • currency
    • cadence
    • renewal or end date
    • payment method
    • upcoming charge
    • usage
    • seats
    • cancellation state

    Sections

    1. Subscription
    2. Usage
    3. Seats
    4. Payment Method
    5. Invoices
    6. Plan Management
    7. Support

    Billing Source

    Web
    Manage subscription in NovaMind.

    Apple
    Manage through Apple subscription settings.

    Google Play
    Manage through Google Play.

    Enterprise
    Contact the verified billing administrator.

    Do not show an incorrect management action.

    === FAILED-PAYMENT RECOVERY ===

    Banner Priority
    High

    Heading
    Payment Method Needs Attention

    Display

    • affected plan
    • current access state
    • verified payment status
    • update-payment action
    • retry action where safe
    • support

    Do not

    • hide the issue in a secondary billing section
    • invent the next retry date
    • imply immediate cancellation
    • remove unrelated account access without verified rules

    === CANCELLATION FLOW ===

    Entry
    Billing Dashboard
    → Manage Plan
    → Cancel Subscription

    Step 1:
    Show current plan, billing source, and verified cancellation consequences.

    Step 2:

    Offer relevant optional alternatives

    • Downgrade to Free
    • Reduce Seats
    • Switch Plan
    • Contact Support
    • Continue Cancellation

    Pause
    Show only if verified and supported.

    Step 3:
    Optional cancellation reason

    Step 4:
    Final confirmation with a visually clear cancellation action

    Step 5:
    Cancellation result

    Display

    • cancellation confirmed
    • access end date
    • remaining access
    • billing status
    • reactivation option

    Rules

    • no mandatory survey
    • no repeated retention screens
    • no hidden final action
    • no emotional pressure
    • no false urgency

    === ETHICAL RETENTION OFFERS ===

    Reason
    Too Expensive

    Relevant Options

    • Downgrade
    • Reduce Seats
    • Switch cadence where appropriate
    • Continue cancellation

    Reason
    Not Using Enough

    Relevant Options

    • Downgrade
    • Usage education
    • Continue cancellation

    Reason
    Technical Problem

    Relevant Options

    • Support
    • Troubleshooting
    • Continue cancellation

    Every offer must preserve the cancellation path.

    === EXPIRATION AND REACTIVATION ===

    Expired State

    Display

    • previous plan
    • current available access
    • verified data state
    • usage state
    • reactivation eligibility
    • current pricing

    Reactivation Flow

    Expired
    → Review Current Plan
    → Review Current Commercial Terms
    → Payment
    → Processing
    → Entitlement Confirmation
    → Restored Access

    Do not imply that old pricing or previous features remain available.

    === RESTORE PURCHASE ===

    Platforms
    iOS and Android where supported

    Flow
    Restore Purchases
    → Billing Account Check
    → Processing
    → Entitlement Verification
    → Success or No Eligible Purchase

    States

    • restored
    • no purchase found
    • wrong platform account
    • expired
    • entitlement pending
    • provider unavailable
    • support required

    Do not encourage another purchase before checking for an existing entitlement.

    === CROSS-PLATFORM ENTITLEMENT ===

    Required Identifiers

    • NovaMind account
    • billing source
    • provider subscription
    • entitlement state

    Conflict Examples

    • web subscription active but mobile access missing
    • Apple subscription active under another app-store account
    • Google Play purchase restored to a different product account
    • two active subscriptions
    • cancelled billing but entitlement still pending

    Required Actions

    • check account identity
    • check billing provider
    • check entitlement
    • restore where supported
    • prevent duplicate purchase
    • escalate unresolved conflicts

    === ACCESSIBILITY REQUIREMENTS ===

    • Semantic pricing sections
    • Accessible plan names
    • Accessible feature-state labels
    • Keyboard-operable cadence selector
    • Visible focus
    • Persistent form labels
    • Error associations
    • Non-color subscription states
    • Accessible comparison tables
    • Mobile reflow
    • Large text
    • 200% zoom
    • Touch-target compliance
    • Accessible dialogs and bottom sheets
    • Screen-reader payment status
    • Reduced motion
    • No claim of conformance without testing

    === LOCALIZATION REQUIREMENTS ===

    • Show currency consistently.
    • Support local price formats.
    • Localize billing terminology.
    • Localize trial and renewal language.
    • Recompose long plan names.
    • Support text expansion.
    • Support Japanese layout requirements.
    • Test right-to-left readiness.
    • Verify regional payment methods.
    • Verify regional disclosures.
    • Avoid concatenated billing sentences.

    === ANALYTICS EVENT MAP ===

    pricing_viewed

    Properties

    • platform
    • market
    • currency
    • current_plan

    billing_cadence_changed

    Properties

    • selected_cadence
    • previous_cadence

    trial_started

    Properties

    • entry_source
    • billing_source
    • payment_required

    paywall_viewed

    Properties

    • gated_feature
    • current_plan
    • entry_source

    usage_warning_viewed

    Properties

    • usage_stage
    • plan
    • user_role

    upgrade_completed

    Properties

    • previous_plan
    • target_plan
    • cadence
    • billing_source

    cancellation_started

    Properties

    • current_plan
    • billing_source
    • account_type

    retention_offer_accepted

    Properties

    • offer_category
    • cancellation_reason_category

    reactivation_completed

    Properties

    • previous_plan
    • new_plan
    • billing_source

    Privacy
    Do not collect payment credentials, full billing addresses, private invoices, authentication secrets, or sensitive cancellation text.

    === EXPERIMENT ROADMAP ===

    Experiment 1:
    Transparent Annual Pricing

    Hypothesis
    Displaying both the full annual charge and monthly equivalent will improve qualified annual-plan selection.

    Primary Metric
    Annual plan purchase

    Guardrails
    Checkout abandonment
    Billing-related support contact
    Early cancellation

    Experiment 2:
    Post-Value Paywall

    Hypothesis
    Showing the paywall after a successful AI result will improve qualified upgrade engagement.

    Primary Metric
    Upgrade start

    Guardrail
    Core-task completion

    Experiment 3:
    Early Usage Warning

    Hypothesis
    Showing usage before the final limit will reduce unexpected task interruption.

    Primary Metric
    Successful plan decision before limit

    Guardrail
    Paywall dismissal

    Experiment 4:
    Single Ethical Retention Screen

    Hypothesis
    One relevant retention step will preserve qualified saves without obstructing cancellation.

    Primary Metric
    Relevant alternative selected

    Guardrails
    Cancellation completion
    Support contact
    Repeated cancellation attempts

    === DEVELOPER HANDOFF ===

    Required Modules

    • PricingPage
    • BillingCadenceSelector
    • PlanCard
    • PlanComparison
    • TrialSummary
    • Paywall
    • FeatureGate
    • UsageMeter
    • UsageWarning
    • UpgradeFlow
    • DowngradeFlow
    • SeatManager
    • SubscriptionCheckout
    • PaymentStatus
    • BillingDashboard
    • InvoiceList
    • PaymentRecovery
    • CancellationFlow
    • RetentionOffer
    • ExpirationState
    • ReactivationFlow
    • RestorePurchase
    • EntitlementStatus

    Required State Domains

    • account
    • plans
    • pricing
    • trial
    • subscription
    • billing
    • payment
    • entitlement
    • usage
    • seats
    • invoices
    • cancellation
    • reactivation
    • app-store
    • analytics

    === ACCEPTANCE CRITERIA ===

    Annual Pricing

    Given annual billing is selected,
    when plan prices are displayed,
    then the full annual amount, currency, billing cadence, verified monthly equivalent, and approved savings are visible.

    Trial

    Given a user starts a trial,
    when the final action is presented,
    then verified trial duration, payment requirement, amount due now, future charge, billing cadence, renewal, and cancellation access are visible.

    Paywall

    Given a user reaches a premium feature,
    when the paywall appears,
    then the gated feature, unlocked value, required plan, verified price, close action, and alternative path are understandable.

    Usage Limit

    Given a user approaches the plan limit,
    when the warning appears,
    then current usage, verified limit, reset rule, and available actions are visible.

    Uncertain Payment

    Given the payment result is inconclusive,
    when the checkout returns,
    then the interface shows an uncertain state, blocks unsafe resubmission, and verifies payment and entitlement status.

    Billing Source

    Given an Apple-managed subscriber opens Billing,
    when management actions appear,
    then the interface directs the user to the verified Apple management path rather than web cancellation.

    Cancellation

    Given a user chooses cancellation,
    when the flow begins,
    then verified access, billing, data, and effective-date consequences are explained without hiding the final cancellation action.

    Restore Purchase

    Given a mobile user may have an existing purchase,
    when Restore Purchases is selected,
    then the product verifies the platform purchase and account entitlement before suggesting another purchase.

    === REGRESSION TEST MATRIX ===

    Plans

    • Free
    • Professional
    • Team
    • Enterprise

    Cadence

    • Monthly
    • Annual
    • Custom

    Subscription States

    • Trial Eligible
    • Trial Active
    • Active
    • Payment Failed
    • Grace Period
    • Cancelled With Access
    • Expired
    • Enterprise Managed

    Billing Sources

    • Web
    • Apple
    • Google Play
    • Enterprise

    Payments

    • Card
    • Wallet
    • App-Store Purchase
    • Invoice Billing
    • Declined
    • Failed
    • Uncertain

    Usage

    • Normal
    • Approaching Limit
    • Limit Reached
    • Reset Pending
    • Overage

    Platforms

    • Desktop Web
    • Mobile Web
    • iOS
    • Android
    • Tablet
    • 200% Zoom
    • Large Text

    Localization

    • English
    • German
    • French
    • Spanish
    • Portuguese
    • Japanese
    • Long Currency Value
    • Right-to-Left Readiness

    === QA CHECKLIST ===

    Pricing

    • Verify plan names.
    • Verify prices.
    • Verify currencies.
    • Verify cadence.
    • Verify annual charge.
    • Verify savings.
    • Verify current plan.
    • Verify Enterprise action.

    Trial

    • Verify eligibility.
    • Verify duration.
    • Verify payment requirement.
    • Verify future charge.
    • Verify cancellation.

    Paywall

    • Verify trigger.
    • Verify close action.
    • Verify frequency.
    • Verify state preservation.
    • Verify post-upgrade return.

    Usage

    • Verify current usage.
    • Verify limits.
    • Verify reset.
    • Verify warnings.
    • Verify team visibility.

    Checkout

    • Verify plan.
    • Verify amount due now.
    • Verify future charge.
    • Verify payment method.
    • Verify processing.
    • Verify declines.
    • Verify uncertain states.
    • Verify duplicate prevention.

    Billing

    • Verify status.
    • Verify source.
    • Verify renewal.
    • Verify payment method.
    • Verify invoices.
    • Verify upcoming charge.
    • Verify seats.
    • Verify cancellation state.

    Cancellation

    • Verify discoverability.
    • Verify consequences.
    • Verify alternatives.
    • Verify optional reasons.
    • Verify final action.
    • Verify confirmation.
    • Verify remaining access.

    Entitlement

    • Verify web access.
    • Verify mobile access.
    • Verify restore.
    • Verify platform mismatch.
    • Verify duplicate-subscription prevention.
    • Verify pending states.

    Accessibility

    • Verify semantics.
    • Verify focus.
    • Verify keyboard.
    • Verify screen readers.
    • Verify contrast.
    • Verify non-color states.
    • Verify zoom.
    • Verify reflow.
    • Verify large text.
    • Verify touch targets.

    === RISKS ===

    Risk
    Annual pricing hides the actual amount charged.

    Mitigation
    Show the full annual charge prominently with the monthly equivalent as secondary context.

    Risk
    The paywall appears before users understand product value.

    Mitigation
    Use contextual post-value gating where commercially and technically appropriate.

    Risk
    Users reach usage limits without warning.

    Mitigation
    Create staged usage communication before the limit is reached.

    Risk
    An uncertain payment is treated as a failure.

    Mitigation
    Use a separate uncertain state with payment and entitlement reconciliation.

    Risk
    Users purchase duplicate subscriptions across platforms.

    Mitigation
    Verify account identity, billing source, restore eligibility, and existing entitlement before purchase.

    Risk
    Cancellation uses manipulative retention patterns.

    Mitigation
    Limit retention to relevant optional offers and preserve a clear cancellation action.

    Risk
    App-store subscribers receive incorrect management instructions.

    Mitigation
    Display actions according to the verified billing source.

    Risk
    Analytics collect sensitive billing information.

    Mitigation
    Track approved categories and outcomes without payment credentials or private records.

    === KNOWN LIMITATIONS ===

    • Commercial terms require product and finance verification.
    • Billing behavior requires provider validation.
    • App-store requirements require current platform review.
    • Entitlement synchronization requires backend testing.
    • Trial eligibility requires historical-account validation.
    • Proration and refunds require authoritative billing logic.
    • Cancellation consequences require verified product and legal rules.
    • Accessibility requires implementation testing.
    • Localization requires professional review.
    • Experiment conclusions require sufficient traffic.
    • The architecture does not guarantee trial conversion, revenue, retention, reduced cancellation, or lower support volume.

    === FINAL INTEGRITY NOTE ===

    All prices, currencies, billing cadences, trials, eligibility, usage limits, discounts, renewals, proration, refunds, payment outcomes, grace periods, suspension rules, cancellation consequences, data-retention behavior, app-store requirements, entitlement states, taxes, and regional disclosures must be verified before implementation.

    Never describe a subscription as active, renewed, cancelled, expired, refunded, restored, or reactivated unless the billing and entitlement systems confirm that state.

    Never hide recurring billing, future charges, cancellation access, plan limitations, usage restrictions, or material feature loss.

    The subscription architecture is designed to improve clarity, trust, payment confidence, entitlement accuracy, accessibility, and implementation readiness. It does not guarantee increased conversion, revenue, annual-plan adoption, retention, or reduced churn.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Map out state transitions for failed payments and grace periods.Design comparison tables for tiered SaaS pricing models.Draft cancellation flows with step-by-step retention offers.Create developer handoff specs for usage-based billing meters.

    About this skill

    Subscription App UI Architect helps SaaS founders, mobile app creators, AI-product teams, membership platforms, digital-product businesses, product designers, growth teams, and developers build clear, trustworthy, and commercially effective subscription experiences.

    The skill supports web applications, responsive SaaS products, iOS apps, Android apps, desktop applications, AI tools, creator platforms, education products, fitness applications, productivity tools, media services, premium communities, marketplaces, B2B platforms, B2C products, and usage-based software.

    It creates complete subscription journeys from initial plan discovery to trial activation, payment, entitlement, renewal, upgrades, downgrades, cancellation, expiration, and reactivation.

    The agent begins by defining

    Product type Target audience User roles Subscription model Plan structure Billing owner Primary conversion Trial eligibility Usage model Entitlement rules Payment channels Billing platforms Renewal behavior Cancellation rules Refund context Markets Currencies Accessibility requirements Technical constraints Verified commercial terms

    The skill can architect

    Pricing pages Plan-comparison tables Subscription cards Trial-entry flows Trial-status screens Paywalls Soft paywalls Hard paywalls Feature gates Usage-limit warnings Upgrade prompts Downgrade flows Add-on purchases Seat management Usage-based billing Subscription checkout Payment-method selection Billing dashboards Invoice libraries Renewal notices Payment-failure states Grace periods Account suspension states Cancellation flows Pause options Retention offers Expiration states Reactivation flows Restore-purchase flows App-store billing interfaces Web-billing interfaces Cross-platform entitlement states Customer-support escalation Analytics Experiment plans Developer handoff Acceptance criteria Regression tests QA checklists Risk assessments

    The skill distinguishes product access from billing status.

    A user may have different states such as

    Free Trial Eligible Trial Active Trial Expiring Trial Ended Subscription Pending Subscription Active Renewal Upcoming Payment Processing Payment Failed Grace Period Cancelled With Access Remaining Paused Expired Suspended Refunded Charge Disputed Enterprise Managed App-Store Managed Web Managed Restore Required Reactivation Available

    Each state can include

    Available features Restricted features Message Primary action Secondary action Billing source Renewal or expiration context Recovery Notification Analytics Support path

    The agent can design subscription models including

    Free and paid Freemium Single premium plan Tiered plans Monthly and annual plans Per-seat pricing Usage-based pricing Credit-based pricing Metered billing Feature bundles Membership levels Creator subscriptions Content subscriptions Hybrid plans Add-ons Enterprise plans Custom contracts Platform-managed subscriptions

    All pricing, limits, billing cadence, proration, trials, discounts, refunds, renewal terms, grace periods, and cancellation rules must come from verified business requirements.

    Pricing-page architecture can cover

    Primary value proposition Target audience Plan names Plan descriptions Monthly and annual billing Price Currency Billing cadence Equivalent monthly price Savings claims Included features Usage limits Seat limits Support levels Add-ons Enterprise contact Recommended plan Trial eligibility Current-plan state Upgrade action

    Faq

    Trust information Billing disclosures Cancellation access

    The skill avoids presenting every feature with equal weight.

    It prioritizes the plan differences that affect the buying decision, such as:

    Who the plan is for Primary outcome Core limits Premium capabilities Collaboration Automation Storage Usage Support Security Administration Commercial terms

    Plan-comparison architecture can use

    Plan cards Feature matrices Segmented comparisons Expandable feature groups Audience-based recommendations Interactive selectors Usage estimators Seat calculators Mobile comparison views

    Comparison tables should remain understandable on small screens and should not require users to remember information across distant sections.

    The agent can distinguish

    Included Limited Unavailable Available as add-on Requires approval Enterprise only Usage dependent Platform dependent

    It avoids ambiguous symbols without labels.

    Billing-cadence interfaces can compare monthly and annual plans while clearly communicating:

    Actual price Currency Billing interval Amount charged Renewal behavior Verified savings Future billing Tax context Cancellation access

    Savings claims must be mathematically correct and approved.

    The skill does not use deceptive annual-price presentation, such as displaying only a monthly equivalent while hiding that the full annual amount is charged upfront.

    Trial architecture can include

    Trial eligibility Trial value proposition Trial length Payment method requirement Amount due now Future price Billing cadence Trial start Trial progress Trial reminders Feature availability Usage limits Trial expiration Conversion Cancellation Post-trial access

    The trial-entry screen should explain

    What the user receives What is required Whether payment details are needed When billing begins What amount will be charged How renewal works How cancellation works

    The agent does not invent trial duration or eligibility.

    Paywall architecture can support

    Hard paywall Soft paywall Feature gate Content gate Usage-limit paywall Trial-ending paywall Premium upgrade screen Contextual upsell Post-value paywall Account-limit paywall Team upgrade prompt

    A paywall should explain

    The value unlocked Why the user encountered it Which plan solves the limitation Current access Future access Price and cadence Trial terms Cancellation access Alternative actions

    The skill avoids aggressive repetition, full-screen interruption without context, misleading close controls, false countdowns, artificial scarcity, and hidden recurring billing.

    Feature-gate architecture can define

    Trigger Restricted feature Current plan Required plan User value Upgrade action Alternative path Dismiss behavior Frequency State preservation Post-upgrade return Analytics

    Users should return to the intended feature after successful upgrade when technically supported.

    Usage-limit architecture can cover

    Seats Storage Projects Messages Exports AI generations Credits Tokens Minutes Uploads Bandwidth API calls Automations Collaborators Transactions Bookings Content access

    Usage-limit communication can include

    Current usage Maximum usage Remaining allowance Reset date Overage behavior Upgrade options Add-on options Grace behavior Blocked actions Data-retention impact

    The agent avoids waiting until a critical task fails before explaining a predictable limit.

    Recommended usage communication stages may include

    Informational Approaching Limit Limit Reached Overage Reset Pending Billing Review Required

    Upgrade flows can define

    Entry point Current plan Target plan Feature differences Limit differences Seat changes Effective date Immediate charge Future charge Credit Proration Billing cadence Payment method Confirmation Processing Success Failure Return destination

    The skill never invents proration.

    Downgrade flows can define

    Current plan Target plan Effective date Feature loss Usage conflicts Seat conflicts Storage conflicts Data impact Automation impact Billing impact Reversibility Confirmation Post-downgrade access

    If the current account exceeds the target plan's limits, the interface should explain the verified resolution path rather than silently removing data.

    Add-on architecture can support

    Additional seats Storage Credits Usage packs Premium support Advanced analytics Security modules Integrations Content bundles Regional access

    Every add-on should explain

    Price Cadence Quantity Included allowance Compatibility Renewal Removal Effective date Refund context

    Seat-management architecture can include

    Purchased seats Assigned seats Available seats Pending invitations Role eligibility Add seats Remove seats Billing owner Effective date Proration Minimum commitment Enterprise restrictions

    Usage-based billing interfaces can show

    Current usage Estimated charge Included allowance Overage rate Billing period Usage history Threshold alerts Spending controls Invoice status Data delay Calculation limitations

    Estimated charges must be labeled as estimates when final billing has not been calculated.

    Subscription checkout can cover

    Plan review Billing cadence Seats Add-ons Trial Discount Taxes Payment method Billing details Terms Amount due now Future charges Order review Processing Confirmation

    The final subscription action should accurately communicate the commitment.

    Possible action structures include

    Start Verified Trial Subscribe for Verified Price Confirm Plan Change Add Verified Seats Reactivate Subscription

    Exact language depends on approved commercial terms.

    Payment-method architecture can support

    Cards Digital wallets Bank debit Bank transfer Platform billing Invoice billing Stored methods Backup methods Local payment methods Gift cards Credits

    Payment states can include

    Idle Validating Ready Submitting Authentication Required Processing Completed Declined Failed Cancelled Pending Uncertain Duplicate Prevented

    The skill gives special attention to uncertain payment states.

    When the final payment result is unknown, the interface should not present the subscription as failed or encourage repeated submission without safe duplicate prevention.

    Billing-dashboard architecture can include

    Current plan Subscription status Billing cadence Renewal date Expiration date Payment method Billing contact Usage Seats Add-ons Invoices Credits Discounts Upcoming charge Cancellation state Billing source Support

    The dashboard should answer

    Which plan am I on? What access do I have? How much am I paying? When is the next billing event? Which payment method is used? Where can I find invoices? How do I change or cancel? Who controls billing? Is billing managed by the web, an app store, or an organization?

    Invoice architecture can include

    Invoice number Issue date Amount Currency Status Billing period Payment method Tax information Download Receipt Credit note Refund relationship Failure state Empty state

    Sensitive payment information must remain masked.

    Failed-payment architecture can cover

    Payment decline Expired payment method Authentication failure Insufficient funds Provider error Network failure Bank failure Invoice overdue Retry pending Grace period Access restriction

    The interface should explain

    What happened Which subscription is affected Whether access is currently available What the user can do Whether retrying is safe Whether another attempt is scheduled Where support is available

    Retry timing must not be invented.

    Grace-period architecture can show

    Grace-period status Access retained Access restricted End date Payment recovery Required action Final consequence Support

    Suspension should be separated from cancellation and expiration.

    Cancellation architecture can include

    Subscription summary Cancellation effective date Remaining access Feature impact Data impact Seat impact Usage impact Add-on impact Billing impact Pause option Downgrade option Retention offer Reason collection Final confirmation Completion Reactivation

    The skill makes cancellation discoverable and avoids unnecessary barriers.

    It rejects

    Hidden cancellation Mandatory support contact when self-service cancellation is supported Repeated confirmation screens Emotional manipulation Confirm-shaming Misleading button colors Forced surveys False warnings Offers that obscure the final cancellation action

    Retention offers should be ethical, relevant, and optional.

    Possible retention options include

    Pause subscription Switch billing cadence Downgrade Reduce seats Remove an add-on Use a lower-usage plan Receive product education Resolve a technical issue Contact support Continue cancellation

    Retention offers should address a real cancellation reason and should never block the user's chosen action.

    Pause architecture can define

    Eligibility Pause duration Billing behavior Feature access Data access Resume date Manual resume Automatic resume Notifications Cancellation during pause

    The agent does not invent pause behavior.

    Expiration architecture can cover

    Access ending Read-only mode Data retention Downloads Exports Team access Public content Integrations Automations Reactivation Deletion

    Reactivation architecture can include

    Previous plan Current eligibility Current pricing Payment method Updated terms Restored access Unavailable features Data state Confirmation Failure Post-reactivation destination

    Restore-purchase flows for mobile apps can cover

    Eligible platform Billing account Previous purchase Restore action Processing Success No purchase found Wrong platform account Expired subscription Family or shared purchase context Support

    The skill distinguishes

    Web-billed subscription Apple-managed subscription Google Play-managed subscription Enterprise-managed subscription Partner-managed subscription

    Users should receive the correct management path for their billing source.

    Cross-platform entitlement architecture can define

    Account identity Billing source Entitlement source Synchronization Pending state Conflict Restore Platform mismatch Web-to-mobile access Mobile-to-web access Multiple subscriptions Duplicate subscription risk

    The agent avoids encouraging users to purchase another subscription when an existing entitlement may already exist.

    Notification architecture can cover

    Trial started Trial ending Renewal upcoming Payment failed Payment recovered Plan changed Usage approaching limit Usage limit reached Cancellation confirmed Access ending Subscription expired Reactivation Invoice ready Price change

    Timing, channels, consent, and required disclosures must be verified.

    Accessibility guidance covers

    Semantic pricing structures Accessible plan cards Table headers Keyboard navigation Visible focus Screen-reader labels Persistent form labels Error relationships Touch targets Contrast Non-color status Zoom Reflow Large text Reduced motion Dialogs Bottom sheets Payment-method selection Accessible toggles Timeouts Mobile keyboards

    Plan comparison should remain understandable without relying exclusively on color, checkmarks, or visual positioning.

    Localization and internationalization planning covers

    Currencies Billing terms Tax terminology Price formats Decimal separators Date formats Trial language Renewal language Cancellation language Pluralization Right-to-left layouts Text expansion Local payment methods App-store terminology Regional disclosures Long plan names Large currency values

    Analytics recommendations can include

    pricing_viewed billing_cadence_changed plan_selected trial_started paywall_viewed paywall_dismissed feature_gate_viewed usage_warning_viewed upgrade_started upgrade_completed downgrade_started downgrade_completed payment_failed payment_recovered cancellation_started retention_offer_viewed retention_offer_accepted cancellation_completed subscription_expired reactivation_started reactivation_completed restore_purchase_started restore_purchase_completed

    Analytics must not contain payment credentials, full billing addresses, private account data, sensitive cancellation reasons, or authentication secrets.

    Experiment roadmaps can test

    Pricing-page hierarchy Plan naming Monthly versus annual presentation Recommended-plan emphasis Feature grouping Trial-entry timing Paywall timing Paywall copy Usage-warning timing Upgrade layout Cancellation clarity Pause presentation Retention-offer relevance Billing-dashboard structure Mobile comparison behavior

    Every experiment should define

    Observation Hypothesis Control Variation Primary variable Primary metric Guardrail Audience Duration logic Sample requirement Risk Decision rule

    The skill does not treat trial-to-paid conversion, reduced cancellation, increased annual-plan adoption, or higher revenue as guaranteed outcomes.

    It can create

    Complete subscription UI architectures Pricing-page specifications Plan-comparison systems Trial flows Paywall systems Usage-limit experiences Upgrade and downgrade flows Checkout specifications Billing dashboards Payment-recovery flows Cancellation systems Ethical retention plans Expiration and reactivation flows App-store billing flows Entitlement state machines Subscription audits Conversion-leak reports Analytics plans Experiment roadmaps Developer handoffs Acceptance criteria Regression tests QA checklists Risk assessments Structured JSON specifications

    It prioritizes commercial clarity, billing transparency, user control, entitlement accuracy, safe payments, accessible comparison, ethical retention, recoverable failures, and implementation readiness.

    The core commercial promise is: design subscription interfaces that help users understand value, compare plans, start trials, upgrade, manage billing, recover failed payments, and cancel or reactivate without confusion, manipulation, or hidden consequences.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 2 months ago

    • Passed all security checks, Safe to install

    Listed2 months ago

    What's inside

    Frequently Asked Questions