openwebf-bridge

Route OpenWebF bridge tasks to focused module codegen workflows.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/archview-ai/webf-plugin --skill openwebf-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openwebf-bridge
Source: https://github.com/archview-ai/webf-plugin/tree/main/webf-plugin/skills/openwebf-bridge
Command: npx skills add https://github.com/archview-ai/webf-plugin --skill openwebf-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecated umbrella; route to focused bridge module codegen skill for a tighter workflow.

Core Features & Use Cases

  • Keep APIs minimal with explicit error handling
  • Direct users to module-codegen workflows and safe bridging patterns

Quick Start

If this umbrella Skill is active, route to openwebf-bridge-module-codegen and follow its workflow.

Frequently Asked Questions about openwebf-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up backward-compatible bridge routing for OpenWebF codegen workflows?

OpenWebF bridge routing orchestrates backward-compatible delegation across codegen, Dart, module registration, and JavaScript usage. Route to the focused openwebf-bridge-module-codegen workflow for tighter, specialized bridge patterns, or fall back to /webf:doctor when repository context is unavailable.

What's the difference between the umbrella bridge and module-codegen bridge workflows?

The umbrella bridge maintains minimal APIs with explicit error handling and deprecation guidance. Module-codegen is the focused downstream workflow for tighter bridge codegen. Use module-codegen for most new work; the umbrella routes you there and provides fallback diagnostics.

Can I use OpenWebF bridge for TypeScript and Dart codegen together?

Yes. OpenWebF bridge orchestrates codegen across TypeScript, Dart, module registration, and JavaScript. It routes to module-codegen for coordinated bridge patterns or /webf:doctor for diagnosis when repository context is missing.

What permission checks does OpenWebF bridge enforce?

OpenWebF bridge implements explicit permission checks alongside minimal APIs and robust error handling to maintain compatibility. Checks are enforced at delegation points to specialized workflows and fallback diagnostics.

How do I troubleshoot bridge routing when repository context is unavailable?

When repository context is missing, OpenWebF bridge falls back to /webf:doctor for diagnostics. This maintains the workflow while directing you to the right path for module codegen or permission resolution.