architecture

Electron multi-process project file organization is enforced by defining a canonical layout across renderer, main, worker, and shared layers. This establishes directory conventions and validates module placement to maintain a scalable architecture.

Correct renderer and main process code structure separates modules into distinct renderer, main, worker, and shared layers. This centralized approach provides cross-reference guidance and best-practice checks for bridges, services, and patterns.

Migrating single-file components to directories in Electron is guided by applying centralized architecture references. This process validates the target layout and enforces correct file-placement rules for the refactored modules.

Shared services and bridges in an Electron app should be placed in defined shared layers following canonical layout rules. This skill validates directory structures and provides best-practice checks for correct module organization.

Yes, this architecture guidance works for existing codebase refactors as well as new applications. It validates directory layouts, bridges, services, and patterns through centralized references to enforce correct file placement.