mastermind-cross-client-setup

星标11

分支0

更新时间2026年7月18日 21:17

Install portable Mastermind workflow adapters and configure, inspect, update, or remove MCP registration for Claude Code, Cursor, Codex, Continue, or an explicit generic config. Use when a user asks to install Mastermind in an AI coding client, choose project/user scope, preview a safe config change, troubleshoot setup, or verify workflow/MCP parity with doctor.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

xcrft

xcrft/mastermind

打开 GitHub 仓库查看创作者相关仓库

下载

Mastermind Cross-Client Setup

Use the built-in adapter. Do not hand-edit client configuration unless the adapter reports an unsupported case.

Workflow

Separate the workflow bundle from MCP registration. For Claude or Codex workflow skills, use mastermind install --client CLIENT; use --client all for both. Claude also receives spawnable subagents. Verify installed ownership and SHA-256 content parity with mastermind doctor --workflow --client CLIENT.
Resolve MCP client and scope from the request. Respect the capability matrix: Codex is user-scope only; Generic requires an explicit config path; Continue owns its standalone Mastermind YAML file.

Run an MCP dry-run first:

mastermind setup CLIENT --scope SCOPE --root . [--config PATH]

Explain only the redacted action summary. Never print existing config, environment values, unknown fields, or subprocess output.
If the user authorized installation/update/removal and the preview matches, repeat with --write. Add --remove only for removal.
Use --force only after explicitly showing that a customized Mastermind entry will be backed up and replaced/removed. Never use force to imply write.
Run mastermind doctor ROOT, using the same root passed to setup, and report structural config status separately from the trusted current-binary MCP handshake. On a new project without .mastermind/mmcg.db, explain that the config can be canonical while the overall doctor exits nonzero and skips the handshake; index the project before requiring an all-green doctor.

Preserve unrelated servers/settings. Stop on malformed/duplicate configs, symlinks, concurrent edits, unsupported scope, missing native CLI, or unsafe path resolution. Do not execute the command stored in client configuration.

同仓库更多 Skills

同仓库

mastermind-design-intake

xcrft/mastermind

Turn a design handoff into a task contract that can actually be checked — named source, resolved components, token names instead of raw values, and an explicit list of what stays unverifiable. Use when a Figma frame, mockup, or design spec is handed over for implementation.

2026-07-3111

mastermind-product-intake

xcrft/mastermind

Convert a PRD, ticket, or feature request into a task contract that can fail — behaviour split from outcome, product nouns resolved to symbols that exist, unspecified cases surfaced as questions, and success metrics parked where a merge gate cannot wave them through. Use when product writing is handed over for implementation.

2026-07-3111

mastermind-security-research

xcrft/mastermind

Enumerate what a change can reach and what enforces it — privileged operations and their callers, guards and the sites that apply them, and every module that reads a secret — before designing an auth, permission, or secrets change. Feeds the security review; produces a population and a gap list, never a verdict.

2026-07-3011

mastermind-test-audit

xcrft/mastermind

Read-only review of whether the tests in a finished change actually prove its behaviour — changed code no test reaches, a test exercising a different path than the one that changed, an assertion edited to match the new output, and a suite that ran nothing. Use after implementation, and whenever a change claims to be covered.

2026-07-3011

mastermind-runtime-research

xcrft/mastermind

Gather who already depends on a service, handler, or state owner before changing it, and name the runtime gaps the codegraph cannot span. Use before designing a change to an API, queue consumer, background job, migration, or shared state; it feeds the architecture review rather than replacing it.

2026-07-3011

mastermind-frontend-audit

xcrft/mastermind

Read-only review of a finished UI change against the codegraph — a component nothing renders, a props contract changed without its callers, a reinvented component, or a raw value where the design system has a token. Use after implementing React or Vue work; triggers "review this UI change", "check the component", or a finished frontend diff.

2026-07-3011

name	mastermind-cross-client-setup
description	Install portable Mastermind workflow adapters and configure, inspect, update, or remove MCP registration for Claude Code, Cursor, Codex, Continue, or an explicit generic config. Use when a user asks to install Mastermind in an AI coding client, choose project/user scope, preview a safe config change, troubleshoot setup, or verify workflow/MCP parity with doctor.
metadata	{"version":"0.2.0","authors":["mastermind"],"tags":["workflow","mcp","setup"]}

Mastermind Cross-Client Setup

Use the built-in adapter. Do not hand-edit client configuration unless the adapter reports an unsupported case.

Workflow

Separate the workflow bundle from MCP registration. For Claude or Codex workflow skills, use mastermind install --client CLIENT; use --client all for both. Claude also receives spawnable subagents. Verify installed ownership and SHA-256 content parity with mastermind doctor --workflow --client CLIENT.
Resolve MCP client and scope from the request. Respect the capability matrix: Codex is user-scope only; Generic requires an explicit config path; Continue owns its standalone Mastermind YAML file.

Run an MCP dry-run first:

mastermind setup CLIENT --scope SCOPE --root . [--config PATH]

Explain only the redacted action summary. Never print existing config, environment values, unknown fields, or subprocess output.
If the user authorized installation/update/removal and the preview matches, repeat with --write. Add --remove only for removal.
Use --force only after explicitly showing that a customized Mastermind entry will be backed up and replaced/removed. Never use force to imply write.
Run mastermind doctor ROOT, using the same root passed to setup, and report structural config status separately from the trusted current-binary MCP handshake. On a new project without .mastermind/mmcg.db, explain that the config can be canonical while the overall doctor exits nonzero and skips the handshake; index the project before requiring an all-green doctor.