architecture

Enforce hexagonal architecture boundaries across ESPlotter main, preload, renderer, and shared layers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ESPlotter/ESPlotter --skill architecture-esplotter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ESPlotter/ESPlotter/tree/main/.github/skills/architecture
Command: npx skills add https://github.com/ESPlotter/ESPlotter --skill architecture-esplotter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a rigorous framework to assess ESPlotter's architecture and enforce hexagonal boundaries across main, preload, renderer, and shared layers, preventing leakage of business logic.

Core Features & Use Cases

  • Enforces layering rules for main, preload, renderer, and shared to preserve domain boundaries.
  • Guides architecture reviews and refactors to maintain consistency and extensibility.
  • Includes a clear baseline for IPC flow, feature placement, and module responsibilities to support scalable development.

Quick Start

Apply the architecture baseline during code reviews to ensure compliance with the designed boundaries.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I enforce hexagonal architecture to prevent business logic leakage in Electron?

To enforce hexagonal architecture in Electron, apply strict layering rules across main, preload, renderer, and shared layers to prevent business logic leakage. This baseline codifies domain separation and module responsibilities to maintain clear boundaries.

What is the correct IPC flow and feature placement for scalable Electron applications?

The correct IPC flow and feature placement relies on a clear architecture baseline that defines module responsibilities and domain separation. This supports scalable development by ensuring strict compliance with layering rules across application layers.

How do I conduct an architecture review for an Electron main and preload codebase?

Conduct an architecture review for an Electron main and preload codebase by applying a strict hexagonal architecture baseline. This framework assesses compliance with layering rules, IPC flow, and domain separation to prevent logic leakage.

Can I use hexagonal architecture to guide refactors and feature onboarding in a renderer process?

Yes, you can use hexagonal architecture to guide refactors and feature onboarding in a renderer process. The framework ensures consistency and extensibility by enforcing strict domain separation and layering rules during development.

When do I need strict layering rules for shared layers in Electron software design?

You need strict layering rules for shared layers in Electron software design when preventing business logic leakage during architecture reviews. Applying these rules preserves domain boundaries and supports lazy feature loading for scalable development.