h0x91b/dev-3.0

Artifact Sharing folds a multi-file report into one self-contained HTML file, publishes it as a secret GitHub gist, and checks the preview URL before returning it. Use it when you need to share a report link from an agent workflow.

Ask Dev3 routes questions about using dev3 to the right workflow and explains the intended steps instead of guessing. Use it when someone asks how to do something in dev3, including onboarding, verification, tmux, multi-agent work, or troubleshooting.

Ask Dev3 answers how-to questions about dev3 by pointing users to the intended flow, relevant decisions, and light troubleshooting steps. It is used when someone asks how a dev3 feature is done or why it works that way.

Debug UI drives the dev-3.0 app in headless Chromium to verify UI changes, reproduce visual bugs, take screenshots, and check console errors. Use it when you need to test the running interface instead of guessing from code.

Dev3 Bug Hunter runs read-only bug-hunting sessions with a seeded starting area and analysis style. It reports findings in a terminal-friendly format and can turn critical or medium issues into follow-up tasks that must reproduce the bug first.

Dev3 Refactor Shrink cuts the token footprint of the Dev3 Claude skill by removing duplicated protocol, shortening the invoke output, and densifying the shared skill body. Use it when you need the Dev3 agent instructions to fit into fewer tokens.

Feature AI Title Generation adds instructions for generating concise 5–8 word task titles during a dev3 session. Use it after `dev3 current` when the auto-generated title is truncated or too long, then run `dev3 task update --title`.

UX Create Manifest audits an existing app repository and generates a project-specific UX bible, architecture YAML, and decision notes from observed code. Use it when a repo needs a baseline UX manifest or the current one is stale or disconnected from implementation.

UX Principal decides where a UI feature belongs before implementation. It reads and updates UX manifest docs, classifies the feature, and returns a placement and implementation brief without coding unless asked.

Verify Changes explains how to test and verify work in dev-3.0, including which Vitest config covers each area, how to mock RPC and i18n providers, and what coverage is expected. Use it when writing tests, investigating failures, or preparing a change for review.

Verify Changes covers what to test for code changes, including vitest scope, mocking patterns, flake reproduction, and coverage expectations. Use it when validating a change against repo-specific verification gates and browser QA requirements.