DBX CLI for database schema exploration and read-only queries. When the user needs to list connections, explore tables, describe schemas, run queries, or generate AI-friendly schema context from DBX-managed databases. Do NOT use for write operations unless the user explicitly confirms with --allow-writes.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Bump the KamehaDB app version across all 6 package files (package.json, desktop/sidecar/shared package.json, tauri.conf.json, Cargo.toml) and update CHANGELOG.md. Use when the user wants to release a new version, bump the version, cut a release tag, or update the changelog.
Use when preparing, validating, tagging, or publishing a KamehaDB desktop release, including version bumps, release changelogs, release artifacts, and GitHub release workflow checks.
Generates a self-contained Python experiment client that uses the ddtrace.llmobs SDK. Emits either a runnable .py script or a Jupyter .ipynb notebook matching the canonical DataDog reference notebook style. Use when the user says "generate Python experiment", "write an SDK experiment", "create a ddtrace experiment"…
Diagnose and fix Single Step Instrumentation (SSI) issues on Kubernetes — SSI automatically instruments applications for APM without code changes. Only use if the agent and SSI are already configured but traces are missing or instrumentation is not working.
Core guidelines and instruction pointers for the mysql-mcp server. Use when interacting with the mysql-mcp server, configuring tool filtering, using Code Mode (mysqlexecutecode), setting up database infrastructure, configuring observability, recovering from failures, or when you need to review its tools and…