Define architecture guidelines for Electron and React projects.
npx skills add https://github.com/mitchlabeetch/Largarda --skill architecture-mitchlabeetch
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/mitchlabeetch/Largarda/tree/main/.agents/skills/architecture Command: npx skills add https://github.com/mitchlabeetch/Largarda --skill architecture-mitchlabeetch
Solves project-structure challenges by defining clear architecture guidelines for Electron apps.
Place a new module following the architecture guidelines to determine its correct location in src/, or reorganize an existing module to conform to the conventions described in references/project-layout.md and references/process.md.
High-intent search queries and answers about installing and using this skill.
Structure your Electron and React project by establishing per-process boundaries between Renderer and Main, enforcing naming conventions, and organizing directories for bridges, services, and workers.
Separate Main and Renderer processes by defining clear directory layouts and per-process boundaries, ensuring specific code stays within its designated process to reduce development confusion.
Decide new module placement by applying a structured decision framework that evaluates file responsibilities and assigns them to the correct location within the src/ directory layout.
Yes, you can use the guidelines to modularize single-file components and migrate existing modules toward a scalable directory structure that conforms to documented project layout conventions.
You need defined naming conventions during new module creation, code reviews, team onboarding, or migrations to align developers on project architecture and prevent structural inconsistencies.
Code organization fails without strict process boundaries because overlapping Renderer and Main logic creates confusion, making directory structure and naming conventions difficult to enforce during development.
TbK0ngInitialize Trellis AI workflow scaffolding with .trellis structure, memory, and CLI hooks.
Rafael-RuedaDiagnose codebase architecture by mapping folder structures and module boundaries.
Gentleman-ProgrammingEnforce hexagonal architecture boundaries across Java Domain, Application, and Infrastructure layers.
lv416eAnalyze repository structure, technology stack, and documentation quality.
