architecting-multi-application-solutions
Planning skill. Use when deciding how to split work across Pigment applications, designing Hub-and-spoke data flows, or planning Test & Deploy across environments.
Install
With your agent
Install OMGSkills skill "gopigment/ai-plugins:skills/architecting-multi-application-solutions" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/gopigment/ai-plugins /tmp/ai-plugins && ln -s /tmp/ai-plugins/skills/architecting-multi-application-solutions ~/.claude/skills/architecting-multi-application-solutionsFrom README
Architecting Multi-Application Solutions Decide When to Split into Multiple Applications Split when one or more drivers apply: Team ownership: One team owns and administers a domain exclusively (Sales Ops, HR, Finance). Security boundaries: Sensitive data (payroll, individual salaries) must be isolated with minimal user exposure. Release cycles: Domains need independent Test & Deploy cadences or structural change schedules. Size and complexity: Dozens of blocks serve one function but only one output metric is shared downstream. Dimension divergence: A business unit needs different time granularity, country lists, or version cadence. Planning cadence: Revenue plans daily with ten scenarios; OPEX plans monthly with one scenario. Multiple applications share data in real time via Libraries — no import/export latency. Place Shared Reference Data in a Hub Application The Hub is a central application holding shared reference data.