openwebf-app
DEPRECATED umbrella Skill (backward compatibility). Use only for cross-cutting orchestration across multiple WebF app tasks when a request spans several capabilities (dev loop + debugging + testing + release). Prefer focused openwebf-app-* Skills.
$ 安裝
git clone https://github.com/archview-ai/webf-plugin /tmp/webf-plugin && cp -r /tmp/webf-plugin/webf-plugin/skills/openwebf-app ~/.claude/skills/webf-plugin// tip: Run this command in your terminal to install the skill
name: openwebf-app description: DEPRECATED umbrella Skill (backward compatibility). Use only for cross-cutting orchestration across multiple WebF app tasks when a request spans several capabilities (dev loop + debugging + testing + release). Prefer focused openwebf-app-* Skills. allowed-tools: Read, Grep, Glob, Bash, Edit, Write, mcp__openwebf__docs_search, mcp__openwebf__docs_get_section, mcp__openwebf__docs_related, mcp__openwebf__docs_get_page
OpenWebF App Skill
Deprecated
Prefer these focused Skills (more reliable auto-discovery, fewer conflicts):
openwebf-app-webf-goopenwebf-app-devserver-networkopenwebf-app-debugging-devtoolsopenwebf-app-testing-vitestopenwebf-app-performance-js
Instructions
If this umbrella Skill is active, immediately route to the most relevant focused Skill based on the user’s trigger terms (e.g. “WebF Go”, “Vitest”, “DevTools”, “performance.mark”, “--host”), then follow that Skill’s playbook.
Keep changes minimal and ask one clarifying question when the request spans multiple areas.
If repo context is missing, start with /webf:doctor and then route to the focused Skill that best matches the user’s trigger terms.
Examples
- “Set up Vitest in this WebF app project and add one unit test and one component test.”
- “Help me debug why WebF Go loads a blank screen from my dev server.”
Repository
