different-ai/openwork.

browser-setup-devtools

Guide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.

daytona-electron-test

Test the real Electron app on Daytona: create sandbox, start services, connect via CDP, create workspaces, drive sessions, and verify settings. Use when the user says 'test on Daytona', 'run the app on Daytona', 'Daytona dry run', 'test Electron remotely', or 'reproduce on Daytona'.

get-started

Guide users through the get started setup and Chrome DevTools demo.

opencode-bridge

Bridge between OpenWork UI and OpenCode runtime

opencode-mirror

Maintain the local OpenCode mirror for self-reference

opencode-primitives

Reference OpenCode docs when implementing skills, plugins, MCPs, or config-driven behavior.

openwork-core

Core context and guardrails for OpenWork native app

openwork-debug

Debug OpenWork sidecars, config, and audit trail

openwork-orchestrator-npm-publish

|

run-evals

Run OpenWork UI evals on a Daytona sandbox or local Electron instance. Handles sandbox creation, service startup, and eval execution via CDP browser tools.

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

workspace-guide

Workspace guide to introduce OpenWork and onboard new users.