openwebf-security-store-guidelines

Ensure store compliance for WebF apps (remote updates, interpreters, rollout/rollback constraints). Use when the user mentions App Store/Play Store, store compliance, remote updates, or publishing WebF-hosted content.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 20, 2025

When & Why to Use This Skill

This Claude skill ensures OpenWebF applications maintain App Store and Play Store compliance by analyzing remote update models, interpreter usage, and deployment strategies. It provides developers with actionable checklists and rollout strategies to mitigate risks during the publishing process, specifically focusing on security constraints and store guidelines.

Use Cases

  • Validating if a WebF app's remote update logic complies with App Store Review Guidelines regarding external code loading and interpreters.
  • Developing a safe and compliant rollout/rollback strategy for mobile applications using remote bundles to ensure stability and policy adherence.
  • Conducting a security and compliance audit for WebF-hosted content before submitting updates to the Google Play Store to prevent rejection.
nameopenwebf-security-store-guidelines
descriptionEnsure store compliance for WebF apps (remote updates, interpreters, rollout/rollback constraints). Use when the user mentions App Store/Play Store, store compliance, remote updates, or publishing WebF-hosted content.
allowed-toolsRead, Grep, Glob, mcp__openwebf__docs_search, mcp__openwebf__docs_get_section

OpenWebF Security: Store Guidelines & Compliance

Instructions

  1. Identify the update model (assets vs remote bundles) and what can change after review.
  2. Use MCP docs (“Store Guidelines”, “Deployment”) as the baseline for constraints.
  3. Provide a compliant rollout/rollback strategy and the risks to watch.
  4. Do not modify code by default; produce a clear checklist and next steps.

More: