mjasin
06f8c823a6
- Fix #16: Implement D3.js transitions and active state badges for Knowledge Graph. - Fix #12: Implement Immersive Reader Layout with Merriweather typography. - Fix #20: Professional code block styling with high contrast and monospace fonts. - Resolve DI runtime error in WASM by adding dummy services. - Replace generic 'Not Found' message with Nexus preloader. - Enforce 'no async void' architecture across UI services.
2.0 KiB
name, description, tags, version
| name | description | tags | version | ||||||
|---|---|---|---|---|---|---|---|---|---|
| nexus-architecture-standards | Guidelines and automated checks for maintaining Clean Architecture and SaaS standards in the NexusReader project. |
|
1.0.0 |
NexusReader Architecture Standards
This skill defines the architectural guardrails for the NexusReader project to ensure consistency, scalability, and security.
Core Rules
1. Clean Architecture Layers
- Domain: Pure business logic, entities, and enums. Zero dependencies on other layers.
- Application: Use cases, MediatR handlers, and interfaces. Depends ONLY on Domain.
- Infrastructure: Implementation details (DB context, AI services, Auth). Depends on Application and Domain.
- Web/Mobile: Presentation layer. Depends on Application (and Infrastructure for DI setup).
Caution
Application MUST NOT depend on Infrastructure. This is a common failure mode. Always use abstractions (interfaces) in Application and implement them in Infrastructure.
2. Multi-Tenancy (Tenant Isolation)
- Every entity related to user data MUST have a
TenantIdproperty. - Every query MUST filter by
TenantIdto prevent data leakage. - Default
TenantIdis "global" for shared resources.
3. Error Handling
-
Use
FluentResults(Result<T>) for all Application services and handlers. -
Avoid throwing exceptions for expected business failures; use
Result.Fail(). -
Commands: State-changing operations. Should return
ResultorResult<T>.
+### 5. Async Operations (Zero Tolerance for async void)
+- All asynchronous operations MUST return Task or ValueTask.
+- Event handlers MUST use Func<Task> or async-compatible patterns.
+- UI components MUST await all service calls and use InvokeAsync(StateHasChanged) for state updates within async contexts.
Audit Scripts
- ArchCheck.sh: A shell script to scan for illegal cross-layer imports.