verify

Builds, launches, and drives the VuaAssistant app with Playwright to verify changes end-to-end.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/360org/vuaassistant --skill verify-360org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/360org/vuaassistant/tree/main/.agents/skills/verify
Command: npx skills add https://github.com/360org/vuaassistant --skill verify-360org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve? Verifying that a code change actually works in the running VuaAssistant app requires manually building the project, launching the UI, and clicking through onboarding, chat, agents, and integrations flows, which is slow and error-prone. ## Core Features & Use Cases - End-to-end UI verification: Builds the app (tsc + vite, cargo check), launches the Vite dev server on port 1420, and drives the interface with headless Playwright Chromium. - Engine IPC contract testing: Exercises the desktop-to-engine SQLite queue contract cross-process via an engine stub, without Docker or real credentials. - Flow coverage: Walks onboarding OAuth, chat streaming, provider switching, agent install, skills, knowledge upload, integrations, persistence across reload, and responsive mobile layouts. - Use Case: Before committing a nontrivial diff, run this Skill to confirm the sign-in screen, chat streaming, and agent install flows still behave correctly in the running app. ## Quick Start Verify my latest changes by building the app, launching the dev server, and driving the main UI flows with Playwright.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify UI changes in a Tauri app without opening a desktop window?▼

Run the Vite dev server with npm run dev, which serves the full product UI at http://localhost:1420, then drive it with headless Playwright Chromium. No Tauri window is needed to verify UI changes.

How to test desktop-to-engine IPC without Docker or credentials?▼

Run cargo run --example ipc_check in src-tauri with VUA_ENGINE_DIR pointing to the engine stub script. It exercises the SQLite inbound/outbound queue contract cross-process, printing check lines for engine attach, sync, and chat round-trips.

What dependencies are needed to run Playwright and Tauri checks on Linux?▼

You need Node.js 20+ and Playwright with Chromium for UI driving. The Rust shell check additionally requires pkg-config, libgtk-3-dev, libwebkit2gtk-4.1-dev, and librsvg2-dev installed via apt-get.

Why does getByText match multiple nodes in Playwright chat tests?▼

The user message text is echoed inside the assistant reply, so getByText on the sent message resolves to two nodes. Scope the locator or use .first(), and use exact: true on getByRole since many labels are substrings of each other.

How do I reset app state to re-run onboarding in tests?▼

Clear the localStorage key vuaassistant-state-v1 or use Settings then Reset in the app. After clearing, reloading the page restarts the onboarding flow instead of skipping to Home.