mcpField
M
mobile-app-product-systems

mobile-app-product-systems

github.com/sylphxaiDevelopment153 installsUpdated today
Repository

About mobile-app-product-systems

mobile-app-product-systems is a skill for designing mobile monetization and retention systems with attention to user trust, edge cases, and store-policy risks. It guides work from user states and business models through state machines, events, and safeguards.

Key features

  1. 01Classifies commerce and engagement surfaces
  2. 02Maps user states and business models
  3. 03Designs entitlement and failure states
  4. 04Defines events and edge cases
  5. 05Applies trust and policy guardrails

Use cases

  1. 01Designing subscription and purchase flows
  2. 02Planning promotions and eligibility rules
  3. 03Reviewing ad and notification strategies
  4. 04Mapping refunds, restores, and cancellations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill mobile-app-product-systems

After installing, type/mobile-app-product-systemsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
mobile-systems-rules.md
promotion-system-patterns.md
refund-and-entitlement-patterns.md

Details

From the project README

Mobile App Product Systems

Use this skill to design mobile app systems that monetize and retain without becoming manipulative, brittle, or store-policy risky.

Resolve the surface

Classify the request into one or more surfaces:

  • Commerce: refunds, subscriptions, IAP, entitlements, restore purchases, receipts.
  • Promotion: discounts, bundles, limited-time offers, win-back, campaign targeting.
  • Ads: IAA placement, rewarded ads, frequency, mediation, ad fatigue.
  • Retention: daily check-in, streaks, missions, rewards, lifecycle messaging.
  • Notifications: push permission, transactional, lifecycle, promotional, quiet hours.
  • Trust: receipts, support, cancel flow, refund clarity, parental/age-sensitive UX.

Then read only the relevant references:

  • General systems: references/mobile-systems-rules.md
  • Refunds, revocation, repurchase, and abuse handling: references/refund-and-entitlement-patterns.md
  • Promotions, offers, eligibility, placement, and campaign measurement: references/promotion-system-patterns.md

Workflow

  1. Identify the user state: new, activated, payer, subscriber, lapsed, refunded, churn-risk, or high-value.
  2. Identify the business model: paid app, subscription, consumable IAP, non-consumable IAP, ads, hybrid, or game economy.
  3. Apply the trust gate before recommending monetization or engagement tactics.
  4. Design the state machine, not just the screen: eligibility, entitlement, cooldown, failure, restore, refund, and support states.
  5. Produce UX, events, edge cases, and policy/trust guardrails together.
  6. For refund or promotion work, include a decision table or state machine rather than generic advice.

Guardrails

Do not propose a tactic unless it passes all checks:

  • The user can understand the cost, benefit, and renewal/expiry state.
  • The system has a clear path for restore, refund help, cancellation, and support.
  • Promotions do not fake scarcity or hide material terms.
  • Notifications are permission-aware, relevant, and rate-limited.
  • Rewards and streaks do not punish healthy breaks or exploit compulsion.
  • Ads do not interrupt critical tasks or degrade first-run trust.

Output format

System: <commerce | promotion | ads | retention | notifications | trust>
User states: <states>

Recommended design:
- <flow/state/rule>

Events to track:
- <event_name> { properties }

Edge cases:
- <case and expected behavior>

Risks:
- <policy/trust/product risk and mitigation>

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Comments

Markdown supported