What problem does it solve? Deciding where new code belongs in an Electron multi-process codebase is error-prone: placing renderer code in the main process (or vice versa) causes runtime crashes, and inconsistent naming or oversized directories degrade maintainability. This Skill provides deterministic rules for file placement, naming, and structure. ## Core Features & Use Cases - Placement Decision Tree: Routes new code to the correct location (renderer, bridge, services, agent, worker, common, preload, webserver, channels, extensions) based on its role. - Process Boundary Enforcement: Defines hard rules for what APIs each process (main, renderer, worker, preload) may use, preventing cross-process import crashes. - Naming & Structure Conventions: Specifies PascalCase vs lowercase directory rules, file naming patterns, the 10-children directory limit, and test file mirroring. - Use Case: When adding a new IPC bridge or React component, consult the decision tree and checklists to place it correctly, name it per convention, and wire it through preload. ## Quick Start Ask the assistant to determine where a new feature file should go in the Electron project and verify it follows the architecture conventions.
