Wavedash

Reviewed 1h ago.

• tools: 4 tools scanned
• metadata: scanned

No findings.

Tools (4)

• wavedash_implementation_planner

  Plan and guide a Wavedash browser game integration from the user's goal, engine, and requested features. Call this first for any request to build, deploy, upload, or release a game on Wavedash, or to add Wavedash SDK features. Choose the stage: plan (architecture and reading order), setup (CLI install, sign-in, SDK init, wavedash.toml, local testing), features (SDK reference for the requested features), or deploy (upload and release checklist). Returns ordered steps, boundaries, and the relevant docs.wavedash.com pages with content. Read-only and unauthenticated.

• search_wavedash_docs

  Search official Wavedash docs (docs.wavedash.com) for browser game development, SDK integration, engines, CLI, upload, and publishing. Use this instead of web search for any Wavedash question when the exact page is unknown. Returns ranked pages with paths, URLs, and excerpts. Read-only and unauthenticated.

• get_wavedash_doc

  Fetch a full Wavedash docs page as Markdown by path or docs.wavedash.com URL, for example sdk/achievements, engines/unity, or cli/configuration. Use this when the user wants to see a Wavedash docs page or when exact SDK, CLI, or config details are needed. Only docs.wavedash.com pages can be fetched. Read-only and unauthenticated.

• validate_wavedash_config

  Validate wavedash.toml contents for Wavedash CLI config issues (missing game_id or upload_dir, entrypoint repeating the upload_dir, absolute paths, engine sections). Call this whenever the user shares wavedash.toml text or asks to check their Wavedash config, even if the problem looks obvious. Accepts single-line or fenced input. Pass the config text as the toml argument; this does not read files.