architecture

Solid

Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.

AI & Automation 604 stars 115 forks Updated 3 days ago AGPL-3.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Architecture Skill Determine correct file placement and structure for an Electron multi-process project. ## Detailed References - **Renderer layer** (components, hooks, utils, pages, CSS): [references/renderer.md](references/renderer.md) - **Main process & shared layer** (bridges, services, worker, preload): [references/process.md](references/process.md) - **Project root & src/ layout** (directory structure, migration status): [references/project-layout.md](references/project-layout.md) --- ## Decision Tree - Where Does New Code Go? ``` Is it UI (React components, hooks, pages)? └── YES → src/renderer/ → see references/renderer.md Is it an IPC handler responding to renderer calls? └── YES → src/process/bridge/ → see references/process.md Is it business logic running in the main process? └── YES → src/process/services/ → see references/process.md Is it an AI platform connection (API client, message protocol)? └── YES → src/process/agent/<platform>/ Is it a background task that runs in a worker thread? └── YES → src/process/worker/ Is it used by BOTH main and renderer processes? └── YES → src/common/ Is it an HTTP/WebSocket endpoint? └── YES → src/process/webserver/ Is it a plugin/extension resolver or loader? └── YES → src/process/extensions/ Is it a messaging channel (Lark, DingTalk, Telegram)? └── YES → src/process/channels/ ``` --- ## Process Boundary Rules **Hard rules - violating them causes runtime crashes.** ...

Details

Author
FerroxLabs
Repository
FerroxLabs/wayland
Created
3 months ago
Last Updated
3 days ago
Language
TypeScript
License
AGPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

architecture

Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.

32,752 Updated 2 days ago
iOfficeAI
AI & Automation Listed

architecture

Use for architecture decisions, module boundaries, coupling, layering, system shape.

1 Updated 1 weeks ago
kreek
AI & Automation Featured

architecture-first

Decide the shape BEFORE the first file, and keep the boundaries honest afterwards: what the modules are, which way dependencies point, where state is owned, and what each module is allowed to know. Merges the layering rules (dependency rule, SOLID, component cohesion, Humble Object, entities vs use cases, frameworks-and-DB-as-details) with domain boundaries (ubiquitous language, bounded contexts, aggregates, domain events, repositories). Use when starting a project, service, site, API or new subsystem; when adding a feature that does not obviously belong to an existing module; when asked "where should this live", "how do we structure this", "what are the modules"; when writing an ARCHITECTURE.md or an ADR; when a dependency points the wrong way or a circular import appears. Do NOT use for a one-file script or a throwaway experiment, for a bug fix inside an existing seam, for word-level naming and function shape (use code-complexity), for splitting a module that is ALREADY too large (use refactoring-safely), o

150 Updated 3 days ago
AnastasiyaW