openwebf-bridge-module-codegen

Build a WebF bridge module/native plugin using the module-codegen workflow (*.module.d.ts → codegen → Dart implementation → registration → JS usage). Use when the user mentions module-codegen, bridge module, native plugin, *.module.d.ts, or registering a module.

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

When & Why to Use This Skill

This Claude skill automates the end-to-end development of OpenWebF bridge modules and native plugins. By leveraging a specialized module-codegen workflow, it streamlines the transition from TypeScript definitions (*.module.d.ts) to Dart implementations. It ensures type safety, reduces manual boilerplate, and accelerates the integration of native platform capabilities into OpenWebF-powered applications, making it an essential tool for Flutter and Web developers.

Use Cases

  • Developing custom native plugins to expose Flutter or platform-specific APIs (like camera, sensors, or local storage) to the OpenWebF JavaScript environment.
  • Automating the generation of Dart bridge code from TypeScript interface definitions to maintain strict type synchronization between the frontend and native layers.
  • Scaffolding and registering new bridge modules within the OpenWebF host application using standardized templates and official architectural patterns.
  • Implementing complex cross-language communication logic with built-in guardrails for availability checks and error handling.
nameopenwebf-bridge-module-codegen
descriptionBuild a WebF bridge module/native plugin using the module-codegen workflow (*.module.d.ts → codegen → Dart implementation → registration → JS usage). Use when the user mentions module-codegen, bridge module, native plugin, *.module.d.ts, or registering a module.
allowed-toolsRead, Grep, Glob, Bash, Edit, Write, mcp__openwebf__docs_search, mcp__openwebf__docs_get_section, mcp__openwebf__docs_related, mcp__openwebf__templates_get, mcp__openwebf__templates_render

OpenWebF Bridge: Module Codegen Workflow

Instructions

  1. Confirm the desired API surface and keep it minimal, typed, and versioned.
  2. Follow the official flow:
    • TypeScript *.module.d.ts
    • webf module-codegen
    • Dart module implementation
    • Registration in the host
    • JS usage example
  3. Add guardrails: availability checks, permission handling, explicit errors.
  4. Use MCP docs for authoritative steps and templates for scaffolding.

More: