design_specific_primers — workbench MCP Prompt

design_specific_primers is one of 4 prompts on the workbench MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke design_specific_primers from your client

• Claude Code workbench Prompt/design_specific_primers run in your project directory
• Claude Desktop workbench Prompt/design_specific_primers ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor workbench Prompt/design_specific_primers ~/.cursor/mcp.json
• VS Code workbench Prompt/design_specific_primers .vscode/mcp.json
• Zed workbench Prompt/design_specific_primers ~/.config/zed/settings.json
• Windsurf workbench Prompt/design_specific_primers ~/.codeium/windsurf/mcp_config.json
• Cline workbench Prompt/design_specific_primers ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI workbench Prompt/design_specific_primers ~/.gemini/settings.json
• Grok workbench Prompt/design_specific_primers .mcp.json (in your project root)
• ChatGPT workbench Prompt/design_specific_primers Settings → Connectors → Advanced → Developer mode
• Claude.ai workbench Prompt/design_specific_primers Settings → Connectors → Add custom connector
• LangChain workbench Prompt/design_specific_primers pip install langchain-mcp-adapters

Other prompts on this server

• verify_clone_batch
• domesticate_for_golden_gate
• identify_unknown_plasmid

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.