es:system-architecture

Provide structured decision frameworks for designing and migrating cross-platform systems.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/jangtrinh/demo-Lam --skill es-system-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: es:system-architecture
Source: https://github.com/jangtrinh/demo-Lam/tree/main/.claude/skills/system-architecture
Command: npx skills add https://github.com/jangtrinh/demo-Lam --skill es-system-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

es:system-architecture helps you make sound, trade-off-aware architecture decisions for cross-platform and distributed systems by providing structured frameworks, failure-mode awareness, and migration guidance.

Core Features & Use Cases

  • Architecture decision frameworks: Use checklists and pattern selection rules to justify choices and document trade-offs.
  • Web → desktop migration guidance: Plan practical paths for moving from web stacks to Tauri-style architectures, including IPC, offline storage, and update strategy considerations.
  • Distributed system pattern coverage: Cover common approaches like event-driven architectures, CQRS, saga workflows, outbox/idempotency patterns, observability, and scalability ladders—along with when not to use them.
  • Security and resilience review: Review threats (e.g., secrets handling, IPC abuse, XSS in rendering surfaces), define “ship-blocking” requirements, and plan for failure modes.

Quick Start

Use the skill to help you plan the architecture for a web app migration to a secure offline-first desktop app.

Frequently Asked Questions about es:system-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a web to desktop migration using a secure offline-first architecture?

Plan a web to desktop migration by using structured decision frameworks for Tauri-style architectures, evaluating IPC, offline storage, and update strategies while documenting trade-offs with architecture decision records.

When should I not use event-driven patterns in distributed system design?

Avoid event-driven patterns when constraints do not justify the complexity; use architectural checklists to evaluate failure modes, trade-offs, and specific scenarios when not to use CQRS, saga workflows, or outbox patterns.

What is the best way to document architecture trade-offs for cross-platform systems?

Document architecture trade-offs by creating ADR-style decisions that justify choices for cross-platform systems, applying pattern selection rules and checklists to record scalability, security, and reliability constraints.

How do I handle security design and failure modes for desktop app IPC?

Handle security design by reviewing threats like IPC abuse, secrets handling, and XSS in rendering surfaces, defining ship-blocking requirements and planning for failure modes to ensure production-grade reliability and safety.

Does this approach support multi-language orchestration for offline-first sync?

Yes, it provides structured decision frameworks for multi-language orchestration and offline-first sync, covering system architecture patterns, failure modes, and constraints for designing distributed systems.