openwebf-host-bundle-loading

Choose and implement WebFBundle loading in a Flutter host (remote URL, assets, localhost dev, inline) and diagnose bundle load failures (bad URL, missing assets, network errors). Use when the user mentions WebFBundle, bundle URL/path, remote vs assets vs localhost vs inline, or “bundle won’t load”.

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

When & Why to Use This Skill

This Claude skill streamlines the integration of OpenWebF bundles into Flutter applications. It assists developers in selecting and implementing the most effective WebFBundle loading strategies—including remote URLs, local assets, localhost for development, and inline content—while providing automated diagnostics for common loading failures like network errors or missing assets to ensure a robust hybrid app experience.

Use Cases

  • Scenario 1: Implementing remote WebFBundle loading to enable over-the-air (OTA) updates for web content within a Flutter app.
  • Scenario 2: Configuring local asset loading to ensure offline availability and compliance with strict app store policies.
  • Scenario 3: Setting up a localhost development environment to facilitate rapid iteration and real-time debugging of WebF content.
  • Scenario 4: Troubleshooting 'bundle won't load' errors by diagnosing incorrect paths, network constraints, or malformed URLs in the Flutter host-side code.
nameopenwebf-host-bundle-loading
descriptionChoose and implement WebFBundle loading in a Flutter host (remote URL, assets, localhost dev, inline) and diagnose bundle load failures (bad URL, missing assets, network errors). Use when the user mentions WebFBundle, bundle URL/path, remote vs assets vs localhost vs inline, or “bundle won’t load”.
allowed-toolsRead, Grep, Glob, Bash, Edit, Write, mcp__openwebf__project_profile, mcp__openwebf__docs_search, mcp__openwebf__docs_get_section, mcp__openwebf__docs_related, mcp__openwebf__templates_get, mcp__openwebf__templates_render

OpenWebF Host: Bundle Loading (WebFBundle)

Instructions

  1. Identify the bundle mode (remote URL, assets, localhost dev, inline) and the constraints (release cadence, store policy, offline needs).
  2. Use mcp__openwebf__project_profile to detect what the repo already has (controller manager, bundle loading, caching).
  3. Use MCP docs to confirm correct WebFBundle usage and safe defaults.
  4. Provide minimal, copy-pastable host-side code changes and verification steps.

More: