ucsandman

dashclaw-ship

The single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist. Lands feature branches on main (rebase, gate, merge, push so Vercel deploys), bumps the unified platform+SDK version, and realigns every *description* of the system with the live code: README, PROJECT_DETAILS, SDK READMEs, /docs, generated artifacts (API inventory, OpenAPI, download bundles), plugins/skills/hooks/MCP, marketing/landing pages, the drift-prone hardcoded counts (routes, SDK methods, MCP tools/resources, guard policies) and stale freshness date-stamps. The one step it can't finish itself is the credential-gated SDK publish (`npm run release:sdks`). Use whenever the user wants to ship, land, or finish a change — get it on main, make it live, cut a release, bump the version, refresh all the docs, make everything accurate, fix wrong counts or old dates. Not for building or debugging the feature itself.

dashclaw-weekly

Compile the week's maintainer-log entries + git history into ONE pasteable Reddit-ready DashClaw update. Drafts only — publishing stays human (MAINTAINER.md §4 spirit). Use when Wes asks for the weekly update, a Reddit digest, or "what happened this week".

gitnexus-cli

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

Code & Development Featured

gitnexus-debugging

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

gitnexus-exploring

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

gitnexus-guide

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"

gitnexus-impact-analysis

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

Code & Development Featured

gitnexus-refactoring

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

repro

Turn a bug symptom into a structured, reproducible bug report — summary, environment, exact repro steps, actual vs expected, and evidence (logs, error text, failing route/test) — and then optionally scaffold a failing regression test that pins it. Use this the moment a bug, defect, crash, 500, wrong count, broken page, or "this used to work" is reported and you're about to start fixing it, even if the user just pastes an error or says "X is broken". A structured report makes a far better fix prompt than a raw symptom and becomes the regression test that stops the bug coming back. Trigger on: repro, reproduce, bug report, file a bug, "X is broken", "getting a 500", "why is this failing", regression test for a bug, write up this bug.

dashclaw-governance

Governance behavior for AI agents governed by DashClaw. Teaches the governance protocol: when to call guard (risk thresholds), how to interpret decisions (allow/warn/block/require_approval), when to record actions, how to wait for approvals, and session lifecycle management. Loads org-specific policies and capabilities from MCP resources at session start. Use with @dashclaw/mcp-server. Trigger on: governed agent, dashclaw governance, guard policy, approval wait, governed capability, risk threshold, action recording, session lifecycle.

291 Updated 1 months ago

audio-track

Use when the user wants music, voiceover, narration, or a soundtrack added to a video asset, OR wants standalone generated audio for any purpose (e.g. "/audio-track", "add music to the launch video", "narrate the demo", "make a 30 second music sting", "generate a voiceover mp3", "jingle for the intro").

de-vibe

Audit and fix the tells that software was vibe-coded / AI-generated, then give it a small distinctive identity, so it ships looking handcrafted and professional. Use whenever the user says "de-vibe", "does this look AI-generated / vibe coded?", "make this look shippable / handcrafted / professional", "remove the AI slop", "polish before launch", asks why their site "looks like every other AI site", or is about to ship/demo/hand off a project that was built largely with AI assistance — even if they don't use the word "vibe". Pairs naturally before /ship.

Web & Frontend Featured

frontend-verify

Verify frontend changes end to end after editing a web app, instead of manually clicking through pages. Use this whenever you have changed UI code and need to confirm nothing broke: "verify my frontend", "check the site after these edits", "did my UI break", "did my changes break anything", "make sure these routes still work", "smoke test the app", "check for console errors", "validate the pages I touched". Works with Next.js (app and pages router), React, Vite, and any local dev server. Built to be token cheap: it reads console errors and failed network requests first and writes full page state to disk, so it only pulls a snapshot or a screenshot into context when a route actually fails. Use it before saying a frontend change is done.

Code & Development Featured

launch-video

Use when the user wants a full launch video / hero video / 30-90s product announcement composing demo footage, logo, and copy (e.g. "/launch-video", "make the launch video for DashClaw").

launch

Use when a product or feature is ready to go public — after shipping, when the user says "launch it", "announce it", "go live", or wants a release marketed end to end.

marketing-studio

Use when generating any brand video, animation, image, or audio asset (logo reveal, social clip, product demo, launch video, OG image, README GIF, music, voiceover) for any product/repo, or when working inside C:\Projects\animations. Required background for /logo-reveal, /social-clip, /product-demo, /launch-video, /og-assets, /audio-track.

marketing

Use when the user wants the complete marketing asset suite for a product in one run — "/marketing", "build all the marketing assets", "generate everything for the launch", "all the animations and brand assets for X". Not for a single asset (use that asset's own skill) and not for launch copywriting alone (use /launch).

ship

Use when finished work needs to go out — the user says "ship it", "update docs commit and push", "commit and push", or asks "anything else we need to update?" before a release or at the end of a work session.

c--projects-dashclaw-route-changes

Make focused changes to API routes with verification.

AI & Automation Solid

logo-reveal

Use when the user wants a logo reveal / logo animation / brand intro video for any product (e.g. "/logo-reveal", "make a logo reveal for DashClaw", "animated logo for the landing page").

AI & Automation Solid

og-assets

Use when the user wants OG images, link-preview assets, animated OG loops, README GIFs, or social-card exports for any product (e.g. "/og-assets", "make an OG image and README gif").

AI & Automation Solid

product-demo

Use when the user wants a product demo video / screen recording with zooms and cursor / dashboard walkthrough clip for any product (e.g. "/product-demo", "record a demo of the app", "Screen-Studio style demo").

DevOps & Infrastructure Solid

social-clip

Use when the user wants a short social media video / feature announcement clip / X-LinkedIn-TikTok teaser for any product (e.g. "/social-clip", "make a clip announcing the new dashboard").

preflight

Run a product's final prelaunch readiness check; /preflight.

epic-infographics

Create infographic images or animated MP4/GIF infographics from data or a topic.

project-graveyard

Inspect abandoned local projects and git history to recommend which project to revive.

wes-voice

Required for anything Wes will post or send online; rewrite in his voice for /wes.

meditate

Nightly/weekly reflection loop for Claude Code - tests lessons against later behavior, with optional workbench work. Use as /meditate.

show-me

Use when the user asks to see something - "show me", "draw it", "diagram this", "what does the flow look like". Explains the current topic visually with pseudocode, call trees, file trees, Mermaid, diffs, or one focused HTML page.

adversarial-review

Multi-agent adversarial code review - parallel finders, verified by a skeptic. Use for "adversarial review" or "did the agents break anything".

deskclaw

Inspect the Windows desktop, screenshots, native apps, and dialogs.

fable-gpt

Use for heavy implementation, debugging, test fixing, or multi-file edits Codex could execute, or orchestrating Claude + Codex.

phone-gotchas

Apply sidetap iPhone guidance before tapping and when taps, scrolls, or sends fail.

phone

Control the user's iPhone, including apps and messaging.

team

Fan a task out to the Claude Code + OpenClaw (MoltFire) team. Use for /team <task> or "have both agents" handle something.

skillfind

Find existing skills before creating one or concluding none exists.

harness-health

Read-only health check of the Claude Code harness - hooks, MCP servers, plugins. Use after editing settings.json/.mcp.json or hooks misbehave.

dispatch-blocks

Use the established brief blocks when dispatching subagents or workflows.

landing-page-cro-expert

Improve landing-page conversion through headlines, hero copy, and calls to action.

treg

Find and call live-data APIs for SEO, social, enrichment, ads, and analytics through Treg.

iphone

Use when you need to window size in points; tap coordinates must stay inside this or other iphone operations from the shell. Run 'iphone describe' first.

moleresearch

Use when you need to ask a question of the user's local data or other moleresearch operations from the shell. Run 'moleresearch describe' first.

petstore

Use when you need to update an existing pet or other petstore operations from the shell. Run 'petstore describe' first.

interview

Use before implementing any non-trivial feature or change — when the user invokes /interview, when a spec has multiple plausible interpretations, when a request is vague ("make it better", "add auth"), or before committing to an architecture. Not for trivial mechanical edits.

secrets

Fill a repo's .env from the machine's credential stores without ever reading or printing a secret value. Use when the user says "/secrets", "fill in the .env", "get the keys", "wire up the credentials", "pull the secrets from offlocal", or when launch.py / a dev server refuses to start because keys are still on example values.