different-ai

Warn when user-facing UI changes drift from DESIGN.md. Advisory only; findings never gate Warden clearance.

Flag concrete bugs introduced by a merged diff. Used only by the post-merge sweep (warden-sweep.yml); never gates clearance.

Flag UI code in a diff that breaks the pinned UI Skills rule sets (baseline UI, accessibility, motion performance, Web Interface Guidelines). Used by the post-merge sweep; never gates clearance.

Open a PR, write or rewrite a PR description, "the PR body is too long", or check whether a PR description is readable. Use whenever a PR is created or its body is edited.

Review a fork PR, review an external contributor PR, check provenance (DCO) and ee/ CLA, run /test, carry a fork commit into a same-repo branch, is this PR safe to merge. Checklist for pull requests from forks before a human approves or merges them.

Validate the release, check the released binaries, is 0.18.x safe to roll out, prove a published desktop release. Checks the RELEASED mac-arm64 enterprise and cloud binaries' signing and notarization and the updater manifests, and publishes evidence.

Prove an OpenWork change works on the real product before calling it done. Start the product, drive the change the way a user or client would, capture screenshots, and show the proof fails on dev and passes on your branch. Use before opening a PR, when a…

Extend a core journey in evals/core or write a one-off proof in evals/proofs that proves a PR's change to a human reviewer. Use when a PR changes user-visible behaviour, when a reviewer asks "show me", or when the coverage decision says a journey is missing.

Drive the OpenWork dev renderer with Chrome MCP and verify workspace UI flows. Triggers when user mentions: - "use Chrome MCP with OpenWork" - "hook up to pnpm dev renderer" - "add an OpenWork workspace through the UI"

Create a PR with structured evidence: build verification, UI screenshots uploaded to an ephemeral host, API test results, and a verification comment. No screenshots committed to the repo. Triggers when user mentions: - "create a pr" - "make a pr" - "open a…

Boot up the Den dev stack and the OpenWork desktop app locally, then test common flows like sign-in, dashboard, and telemetry. Triggers when user mentions: - "test den" - "test the app locally" - "boot up den" - "den dev flow" - "test sign in"

Generate or update the internal OpenWork release changelog tracker as plain markdown release sections. Triggers when user mentions: - "generate changelog markdown" - "track this release" - "add a changelog entry"

CUPID app architecture guidance for apps/app/src/app/**

Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"

Fetch and fast-forward the OpenWork enterprise repo and its subrepos to their latest remote heads when it is safe to do so. Triggers when user mentions: - "get latest changes" - "update context repo to latest" - "pull all subrepos"

Recover or verify Chrome MCP before UI-flow testing. Triggers when user mentions: - "chrome mcp is broken" - "chrome mcp bootstrap" - "browser broker missing" - "cannot connect to chrome mcp"

Debug production issues on Vercel using logs, database inspection, and proper deployment waiting

Make features testable by design. Testing pyramid from fast (local) to slow (UI). Expose APIs securely for testing.

Manage DNS records for domains hosted on Vercel using the Vercel CLI

Workspace guide to introduce OpenWork and onboard new users.

Access and update company administrative information stored in Notion

Create and register new OpenCode skills in this repo

Keep the 0 Finance CLI aligned with product capabilities.

Create new OpenCode skills with valid SKILL.md frontmatter.

Create new OpenCode agents with a gpt-5.2-codex default.

Create OpenCode custom commands for repeatable tasks.

Create targeted Cal links for specific people or teams

Use Chrome MCP to verify OpenWork UI flows, especially any feature that touches remote behavior. Triggers when user mentions: - "test with chrome mcp" - "ui verification" - "remote behavior test"

Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP. Triggers when user mentions: - "dev-up.sh" - "docker dev stack" - "verify in chrome mcp" - "test the real flow"

Run owpenbot/openwrk integration tests with Telegram test tokens. Triggers when user mentions: - "owpenbot tests" - "telegram test tokens" - "openwrk integration test"

Create OpenCode plugins and know where to load them.

Fast preflight for sandbox lifecycle work: sync pins, create a worktree, and run the standard Docker + Chrome MCP verification path. Triggers when user mentions: - "sandbox lifecycle" - "sandbox stuck" - "docker + chrome mcp"

Add a new lead to your Notion CRM with PULL analysis. You provide the context, the skill structures it and creates the entry.

Draft a personalized outreach message for a lead. Fetches lead data from Notion, reads Feedback Insights for what's working, and applies the 5-element framework.

Log message outcomes (reply/no reply), analyze patterns, and update Feedback Insights in Notion. This is the learning engine of the CRM.

Bootstrap your AI-powered CRM. Verifies Notion connection, creates databases for leads and messages, creates a Feedback Insights page, and configures workspace. Run this first.

Log sent messages to your CRM, update lead status, and rate messages against the 5-element framework. Use after sending a message.

Reliable browser automation through explicit Chrome DevTools Protocol endpoints.

Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.