OpenWebF Help

Use this as the main entry point for the webf plugin.

Steps

1. If the user passed $ARGUMENTS, treat it as the directory to inspect; otherwise use the current working directory.
2. Call mcp__openwebf__project_profile with { "cwd": "<dir>" } and summarize:
   • Type + confidence
   • Top 3 findings (if any)
3. Summarize what the plugin can do (very briefly):
   • WebF app workflow (Vite/React/TS + WebF Go)
   • Flutter host integration (controllers/bundles/routing/theming/caching/perf)
   • Bridge modules + hybrid UI
   • Offline docs search via MCP
4. Based on detected type, present a short ordered list of “start here” commands:
   • Always include /webf:init and /webf:doctor
   • Include the top 3 track-specific commands
5. Call mcp__openwebf__recommendations with { "cwd": "<dir>", "goals": [] } and show the top recommendations as:
   • severity
   • title
   • nextCommands
   • templates (ids only)
6. Call mcp__openwebf__templates_list and show available template IDs grouped by category prefix:
   • host/*, routing/*, bridge-module/*, hybrid-ui/*, app/*, perf/*, security/*
7. Ask the user one question to route them:
   • “Are you working on the WebF app layer, the Flutter host layer, or both?”