End-to-end solution design — system integration, channel orchestration, identity management, observability, and cross-cutting concerns. [EXPLICIT] Use when the user asks to "design the full solution", "integrate multiple systems", "plan API gateway strategy", "define identity and security architecture", "set up observability", or mentions C4 containers, BFF, Zero Trust, SLI/SLO, circuit breaker, or migration planning. [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/solutions-arch-patterns.mdtemplates/output.docx.mdtemplates/output.htmlSolutions architecture designs the complete system that solves a business problem — how multiple systems connect, how users interact, how data flows, how security is enforced, and how the solution is observed and operated. It bridges business requirements and technical implementation. [EXPLICIT]
Una solución es más que la suma de sus sistemas. La arquitectura de solución diseña cómo múltiples componentes — APIs, canales, identidad, datos, observabilidad — se integran para resolver un problema de negocio completo. Cada integración es un contrato. Cada contrato es un punto de fallo. Cada punto de fallo necesita un plan B.
The user provides a system or project name as $ARGUMENTS. Parse $1 as the solution/project name used throughout all output artifacts. [EXPLICIT]
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40% — S1 solution view + S2 integration + S4 security) | técnica (full 7 sections, default)Before generating architecture, detect the codebase context:
!find . -name "*.ts" -o -name "*.java" -o -name "*.py" -o -name "*.go" -o -name "*.yaml" | head -30
If reference materials exist, load them:
Read ${CLAUDE_SKILL_DIR}/references/integration-patterns.md
Read ${CLAUDE_SKILL_DIR}/references/security-models.md
High-level diagram showing all systems, boundaries, external dependencies, and integration points. [EXPLICIT]
Includes:
Key decisions:
How systems connect, exchange data, and coordinate. [EXPLICIT]
Includes:
Trade-offs:
How end-users and external systems interact with the solution. [EXPLICIT]
Includes:
Key decisions:
How users are authenticated, authorized, and how data is protected. [EXPLICIT]
Authentication (AuthN):
Authorization (AuthZ):
Zero Trust:
API Security:
Data Protection:
How the solution is monitored, debugged, and operated in production. [EXPLICIT]
Logging: Structured, centralized, correlation IDs, retention policy Metrics: Application (RPS, error rate, latency p50/p95/p99), infrastructure (CPU, memory), business (transactions, revenue) Tracing: OpenTelemetry, trace spans, sampling strategy Alerting: Conditions, on-call escalation, alert fatigue management Dashboards: Executive (business), operational (latency, errors), debugging (traces, slow queries)
SLI/SLO/SLA:
Technical patterns applied across multiple components. [EXPLICIT]
How to move from current state to target state without disrupting operations. [EXPLICIT]
Migration Strategy: Strangler fig, parallel running, cutover (flag day vs. phased), rollback plan Data Migration: Schema evolution, dual-write, verification (checksums, counts), rollback Phased Rollout: Dark launch -> canary 5% -> 25% -> 50% -> 100%; rollback criteria Team Readiness: Documentation, training, on-call, capacity planning Risk Management: Data loss (backup, RTO), service unavailability, performance degradation, security exposure, compliance approval
| Decision | Enables | Constrains | When to Use |
|---|---|---|---|
| Synchronous Integration | Immediate consistency, simple errors | Tight coupling, latency, availability risk | Simple workflows, strong consistency |
| Asynchronous (Event-Driven) | Decoupling, resilience, independent scaling | Eventual consistency, complex debugging | High-scale, distributed, domain-driven |
| API Gateway | Central security, rate limiting, monitoring | Single point of failure, added latency | Multi-channel, external API exposure |
| BFF | Optimized API per channel, client flexibility | Duplication, consistency challenges | Multi-channel with divergent needs |
| OAuth2/OIDC | Industry standard, social login, delegation | More complex than basic auth | External users, enterprise SSO |
| Centralized Logging | Complete audit trail, easy debugging | Overhead, privacy, storage cost | Compliance-heavy, production troubleshooting |
| Distributed Tracing | End-to-end visibility, latency identification | Instrumentation overhead, sampling complexity | Multi-service, debugging latency |
| Caching (Redis) | Dramatic latency reduction | Invalidation complexity, memory cost, stale data | High-load, read-heavy workloads |
| Circuit Breaker | Fail-fast, prevent cascades | False positives, added latency | Systems calling unreliable dependencies |
Greenfield Multi-System Solution: No existing integration patterns. Risk: over-designing for scale that doesn't exist. Start simple (sync APIs), add async/caching when metrics show need. [EXPLICIT]
Legacy Mainframe Integration: Impedance mismatch (batch vs. real-time, EBCDIC vs. UTF-8, CICS vs. REST). Solution: integration layer (adapter, translator), strangler fig, eventual retirement timeline. [EXPLICIT]
High-Latency or Unreliable Networks: Offline-first architecture required: local cache, sync when connected. Conflict resolution for eventual consistency. [EXPLICIT]
Real-Time, Low-Latency Requirements: Financial trading, gaming, autonomous systems. Synchronous preferred; async trade-offs documented. Infrastructure must support global distribution and failover. [EXPLICIT]
Highly Regulated System: GDPR, HIPAA, PCI-DSS, SOX: compliance non-negotiable. Every decision maps to compliance requirement. Audit trails, encryption, data residency, consent management built-in from start. [EXPLICIT]
Before finalizing delivery, verify:
| Format | Default | Description |
|---|---|---|
markdown | Yes | Rich Markdown + Mermaid diagrams. Token-efficient. |
html | On demand | Branded HTML (Design System). Visual impact. |
dual | On demand | Both formats. |
Default output is Markdown with embedded Mermaid diagrams. HTML generation requires explicit {FORMATO}=html parameter. [EXPLICIT]
Primary: A-02_Solutions_Architecture_Deep.html — Executive summary, solution view, integration architecture, channel architecture, identity/security, observability, cross-cutting concerns, transition plan.
Secondary: C4 diagram (PNG/SVG), integration contract specs, observability config templates, security checklist, transition runbooks.
Author: Javier Montaño | Last updated: 2026-03-18
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.