Browser automation for the DotCraft in-app browser. Use to open, navigate, inspect, test, click, type, screenshot, or verify local targets such as localhost, 127.0.0.1, ::1, file://, dotcraft-viewer:, the current app browser tab, and approved http/https pages.
Use the user's existing Chrome browser through the DotCraft Chrome extension backend. Use for authenticated/profile-dependent pages, existing Chrome tabs, cookies-backed sessions, installed extensions, and workflows where the Desktop embedded browser is not…
Find and export DotCraft session, trace, and memory context for external coding agents or DotCraft Doctor troubleshooting. Use when a user needs to locate related sessions from an error, provider message, tool failure, symptom, or thread id, then produce a…
Use Playwright CLI to inspect and interact with a running CDP-enabled DotCraft Desktop.
DotCraft development conventions. Use when changing protocols or shipping user-facing functionality.
Write, revise, and validate DotCraft user or developer documentation, including documentation-site pages, repository and sample READMEs, SDK/API guides, protocol references, lifecycle docs, and integration guides. Does not cover release notes or code comments.
Route DotCraft troubleshooting requests to failure diagnosis, context handoff, or issue reporting. Use when DotCraft Doctor is invoked for Hub, AppServer, startup, process, provider, tool, agent, or session problems without a more focused skill.
Diagnose DotCraft Hub, AppServer, startup, process, request, provider, agent, tool, context, or session failures from operational logs and workspace evidence. Use when DotCraft fails to start or stay running, a request or turn errors, a thread cannot resume,…