Loading...
Loading...
Found 6 Skills
When the user wants to optimize free trial conversion -- including trial length, trial type selection, expiry flows, or trial email sequences. Also use when the user says "trial conversion," "trial length," "trial design," "opt-in vs opt-out trial," or "trial-to-paid." For activation, see activation-metrics. For feature gating, see feature-gating.
Check whether a RevenueCat user currently has access to a paid feature via entitlements. Use when the user asks to gate a feature behind premium, check if the user has a pro subscription, read customerInfo active entitlements, show or hide a feature based on subscription status, react to entitlement changes, or 'is the user subscribed' on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
Implement subscription tier-based feature gating and usage limits. Centralized tier configuration, database usage tracking, and clean APIs for checking limits.
Skill for adding feature gating and usage tracking using Autumn.
RUNTIME skill — use when implementing the runtime side of Stigg — gating feature access (`hasAccess`, `getMeteredEntitlement`, `getBooleanEntitlement`, `getEntitlement`), reporting usage (`reportEvent` for raw events vs `reportUsage` for calculated measurements), promotional entitlements, and configuring local caching / fallback so checks stay reliable when Stigg is unreachable. Triggers include "gate this feature with Stigg", "check entitlement", "is the customer allowed to", "hasAccess", "feature flag with Stigg", "report usage to Stigg", "report a usage event", "increment usage", "events.report vs usage.report", "Stigg fallback strategy", "Stigg cache", "Stigg sidecar", "Stigg goes down", "Stigg offline", "stale entitlements", "promotional entitlement", "grant a one-off entitlement". Skip for catalog modeling (stigg-pricing-modeling), subscription lifecycle (stigg-subscriptions), or generic feature flags with no Stigg integration (e.g., LaunchDarkly).
Use when Stigg is being provisioned or has just been provisioned through Stripe Projects — `stripe projects add stigg/environment`, `stripe projects catalog`, `stripe projects rotate`/`remove` against Stigg, or when a `.env` already holds `STIGG_SERVER_API_KEY` / `STIGG_CLIENT_API_KEY` that Stripe Projects wrote. Also use when the user asks to add pricing, entitlements, feature gating, or usage metering to an app that is already using Stripe Projects, so the environment is provisioned from the terminal instead of by signing up in a browser. Covers what the provisioned credentials are and the first wiring of the server and client SDKs. Skip for Stigg work unrelated to Stripe Projects — load the `stigg` umbrella and its pillars instead.