hemelion_clarity_decision — Hemelion Decision and Pattern Reflection MCP Prompt

hemelion_clarity_decision is one of 3 prompts on the Hemelion Decision and Pattern Reflection MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke hemelion_clarity_decision from your client

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

Other prompts on this server

• hemelion_choose_path
• hemelion_mindscan_episode

Hemelion Decision and Pattern Reflection also offers 4 resources — data you attach as context, where a prompt is something you run.

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.