Stats
Actions
Tags
From service-domain-map
Cross-product orchestration map for the Orryx Group. Triggers on "what does X depend on", "which MCP should I call for Y", "/SERVICE_DOMAIN_MAP", or any question about which service-domain MCP serves which capability across products. Materialises the implicit cross-repo map from Brain into a single maintained doc.
How this skill is triggered — by the user, by Claude, or both
Slash command
/service-domain-map:service-domain-mapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The Orryx Group's 11+ service-domain MCPs (HR, sales, product, customer, strategy, accounting, UI-design, data-analytics, AI-automation, risk-compliance, security, engineering) serve cross-cutting capabilities to the products (Triora, Pillarworks, Flow, Brain, etc.). This skill provides the **canonical map**: which MCP serves which capability, which product currently consumes it, and what data ...
The Orryx Group's 11+ service-domain MCPs (HR, sales, product, customer, strategy, accounting, UI-design, data-analytics, AI-automation, risk-compliance, security, engineering) serve cross-cutting capabilities to the products (Triora, Pillarworks, Flow, Brain, etc.). This skill provides the canonical map: which MCP serves which capability, which product currently consumes it, and what data flows where.
Originally an implicit map maintained in Brain's /SERVICE_DOMAIN_MAP slash command; materialised here in Wave 3.
| Capability | Routes to | Consumed by |
|---|---|---|
| boq-generation | orryx-data-analytics + orryx-ai-automation | Pillarworks |
| material-pricing | orryx-data-analytics | Pillarworks |
| project-estimation | orryx-ai-automation | Pillarworks |
| takeoff-detection | orryx-ai-automation + orryx-ui-design | Pillarworks |
| Domain | Port | Key endpoints | Consumed by |
|---|---|---|---|
| risk-compliance | 9001 | /log-audit-event, /check-compliance-control, /compute-risk-score | All products |
| security | 9002 | /check-vulnerability, /sync-incident-state, /log-security-event | All products |
| product | 9003 | (TBD) | (TBD) |
| customer | 9004 | (TBD) | (TBD) |
| strategy | 9005 | (TBD) | (TBD) |
| hr | 9006 | /get-employee-record, /list-active-projects | Brain, Pillarworks |
| accounting | 9007 | /create-invoice, /log-time-entry | Brain |
| ui-design | 9008 | /get-design-token, /sync-figma-update | All products |
| ai-automation | 9009 | /run-workflow, /list-active-jobs | Pillarworks |
| data-analytics | 9010 | /compute-metric, /sync-warehouse | Pillarworks, Brain |
| sales | 9011 | (TBD) | (TBD) |
| engineering | 9012 (proposed) | (TBD) | Brain |
When a product starts consuming a new MCP capability:
@orryx/core/domain-mcp-base GatewayRegistrationorchestration/SERVICE_DOMAIN_MAP.md (the operational state file)D:\orryx-governance\compliance/<entity>.md for compliance implications/SERVICE_DOMAIN_MAP slash commandThe original implicit map. In Wave 3, this becomes:
orchestration/SYNC_STATE.md: real-time state (which MCPs are healthy)Clinical_trials/.claude/ directly). Cross-product communication goes through the gateway via documented MCP capabilities..mcp.json.http://localhost:9000. Don't hardcode either; use ORRYX_MCP_GATEWAY_URL env var.foundation/mcp-builder — for authoring new domain MCPs@orryx/core/domain-mcp-base — the base class every domain MCP extendsorryx-mcp-gateway repo — the routing layerorryx-brain/orchestration/SERVICE_DOMAIN_MAP.md — operational stateorchestration/3-lane-parallel — for cross-product sprint coordinationProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub alexmclaren/orryx-knowledge --plugin service-domain-map