opencode-effect-enforcer 0.2.2 → 0.2.4

package/patterns/vm-in-wrong-file.md

@@ -1,51 +0,0 @@
----
-action: context
-tool: (edit|write)
-event: after
-name: vm-in-wrong-file
-description: View Model definitions must be in .vm.ts files - detected VM pattern outside of proper location
-glob: '**/!(*.vm).{ts,tsx}'
-pattern: (interface\s+\w+VM\s*\{|Context\.(Service|GenericTag)<\w*VM>|Layer\.(effect|scoped)\(\s*\w+VM)
-level: critical
-suggestSkills:
-    - effect-react-vm
----
-
-# VM Code in Wrong File
-
-```haskell
--- File structure convention
-data ComponentFiles = ComponentFiles
-  { component :: "Component.tsx"      -- pure renderer
-  , viewModel :: "Component.vm.ts"    -- VM definition
-  , index     :: "index.ts"           -- re-exports
-  }
-
--- VM file structure
-data VMFile a = VMFile
-  { interface :: Interface a          -- type contract
-  , tag       :: GenericTag a         -- DI tag
-  , layer     :: Layer a              -- implementation
-  }
-```
-
-```haskell
--- Anti-pattern: VM in component file
-bad :: "Component.tsx"
-bad = do
-  interface ComponentVM { ... }       -- ✗ wrong file
-  ComponentVM = Context.Service       -- ✗ wrong file
-  layer = Layer.effect(...)           -- ✗ wrong file
-
--- Correct: VM in dedicated file
-good :: "Component.vm.ts"
-good = do
-  ComponentVM = Context.Service       -- ✓ correct file (Effect v4 beta.46)
-  layer = Layer.effect(...)           -- ✓ correct file
-  export default { service, layer }   -- ✓ clean export
-
--- Import in component
-import ComponentVM from "./Component.vm"
-```
-
-VMs must be in `.vm.ts` files. Mixing rendering and state management breaks organization. Invoke `react-vm` skill for guidance.