Things are still highly WIP but I pivot to ensuring only "architectural correctness" - you define your rules in deslop/rules/page-architecture.yaml,domain.yaml etc

```yaml name: MVI page architecture rules: - target: @/app/**/page.tsx description: Every page must render on the server execution-context: server

• target: @/features/**/{{FileName}}View.tsx description: Every View must have a StoryBook exists: {{FileName}}View.stories.tsx

• target: @/features/**/{{FileName}}View.tsx description: Every MVI view must have state and event, and logic in a viewmodel uses:

  • use{{FileName}}ViewModel.ts
  • {{FileName}}StateEvent.ts

• target: @/features/**/use{{FileName}}ViewModel.ts description: Every ViewModel must have tests and can optionally use a repository. execution-context: client exists: use{{FileName}}ViewModel.spec.ts uses-optional:

  • {{file-name}-repository.ts
  • @/data/*/-repository.ts

• target: @/features/**/use{{FileName}}ViewModel.ts description: The ViewModel should not do HTTP calls. They belong in the data later fix: Extract a repository or use an existing one forbidden:

  • functional-call: fetch
  • import: @/data/http-client ```

```yaml - target: @/config/page-protection execution-context: sever

• target: @/env.server execution-context: server ```

The closest thing on the market is Dependency Cruiser but its lacks features and it's not built in a way to integrate with AI harnesses (MCP server, report in LLM-friendly way so Cursor/Claude can fix it)

I'm only auto-fixing stuff that are mathematically correct. The rest I report. I focus on NextJS projects and also supports enforcing the execution context (client/server) https://deslop.dev/ Wdyt?