architecture
SolidProject 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.
Install
Quality Score: 85/100
Skill Content
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
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.
architecture
Use for architecture decisions, module boundaries, coupling, layering, system shape.
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