Implement Model Factory

.recurseml.yaml

@@ -0,0 +1 @@
+rules: .rules/

.rules/anti_dry.mdc

@@ -0,0 +1,17 @@
+---
+description: Don't DRY Your Code Prematurely
+globs: "**/*.{js,ts,py,go,java,rb,cs}"
+alwaysApply: false
+---
+
+Reference: https://testing.googleblog.com/2024/05/dont-dry-your-code-prematurely.html
+
+Consider carefully if code duplication is truly redundant or just superficially similar before applying DRY principles. Functions or classes may look the same but serve different contexts and business requirements that evolve differently over time. 
+
+Key principles to follow:
+- Avoid premature abstractions that couple behaviors which may need to evolve separately
+- When in doubt, keep behaviors separate until enough common patterns emerge over time that justify the coupling
+- Think about long-term evolution, not just making code shorter
+- Apply YAGNI principle - tolerate a little duplication in early development stages
+- Wait to abstract until clear patterns emerge
+

.rules/effective_comments.mdc

@@ -0,0 +1,20 @@
+---
+description: Effective Code Comments
+globs: "**/*.{js,ts,py,go,java,rb,cs}"
+alwaysApply: true
+---
+
+
+For more context read: https://blog.codinghorror.com/code-tells-you-how-comments-tell-you-why/
+
+- NEVER write comments for code that can be understood from the code itself
+- Avoid redundant comments that restate the obvious
+- Use comments to clarify the intent behind complex logic or decisions
+- Use comments when non-obvious assumptions are made
+- Keep TODO comments specific with assignees when possible
+- ALWAYS update comments when the underlying code changes
+
+# Solution
+
+Fix redundant comments by removing them completely.
+Never attempt to add additional clarification to the comments.