architecting-multi-application-solutions
Skill from gopigment/ai-plugins
Install
npx skills add gopigment/ai-plugins --skill architecting-multi-application-solutions
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install pigment@pigment
This skill is part of the plugin “pigment”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the architecting-multi-application-solutions skill do?
Description from the SKILL.md in the source repository.
Questions about architecting-multi-application-solutions
What does the architecting-multi-application-solutions skill do?
Planning skill. Use when deciding how to split work across Pigment applications, designing Hub-and-spoke data flows, or planning Test & Deploy across environments.
How do I install architecting-multi-application-solutions?
In a terminal: npx skills add gopigment/ai-plugins --skill architecting-multi-application-solutions. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use architecting-multi-application-solutions?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is architecting-multi-application-solutions safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from gopigment/ai-plugins
Execution skill. Use when configuring an application calendar — choosing calendar type, fiscal year, date range, and time dimensions.
Planning skill. Supply chain use cases: demand planning, inventory management, procurement planning, S&OP alignment. Each use case has inline guidance.
Planning skill. Sales performance use cases: quota planning, commission calculations, territory assignment, attainment tracking, pipeline coverage. Each use case has inline guidance.
Planning skill. FP&A use cases: budget/expense planning, revenue forecasting, P&L reporting, multi-currency, financial consolidation. Each use case has inline guidance; load sub-files only for advanced patterns.
Execution skill. Use when sharing metrics or lists between Pigment Applications via Libraries and cross-Application formula references.
Execution skill. Use when investigating slow inputs, slow calculations, or timeouts with the Performance Insights tools (performance_profile_change, performance_profile_change_scope_details, performance_slowest_changes, performance_changes_statistics, get_top_blocks_by_performance). Covers which tool to call, the includeAllExecutions default, reading change profiles (X/Y scope, contention, impacted viewed data), drilling into the scoped dimensions of some executions, locating the bottleneck, and comparing timings before/after a fix. Always profile before formula changes; never optimize from assumptions.
Execution skill. Use when writing PREVIOUS, PREVIOUSOF, or PREVIOUSBASE formulas, configuring iterative calculation cycles, or debugging circular dependency errors.
Execution skill. Use when naming or organizing Pigment Applications, folders, and blocks so models stay navigable, formula-safe, and consistent across teams.
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.