{
  "context": "This criteria evaluates how well the engineer uses CoffeeScript's module system and Node.js's Module API to implement multi-dot extension handling. The focus is on proper patching of Module.load or Module._extensions, correct extension parsing logic, and appropriate use of CoffeeScript's registration patterns.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Module patching",
      "description": "Correctly patches Node.js's Module.prototype.load or hooks into Module._extensions to intercept module loading, following patterns similar to CoffeeScript's register() implementation",
      "max_score": 25
    },
    {
      "name": "Extension parsing",
      "description": "Implements logic to split filename by dots and check extensions from longest to shortest (e.g., '.test.js' before '.js'), mirroring CoffeeScript's multi-dot extension algorithm",
      "max_score": 25
    },
    {
      "name": "Handler registration",
      "description": "Properly stores and retrieves custom extension handlers in Module._extensions or similar registry, using the same pattern as CoffeeScript.register()",
      "max_score": 20
    },
    {
      "name": "Fallback behavior",
      "description": "Implements correct fallback to check shorter extensions and ultimately Node.js's default handlers when longer extensions aren't registered",
      "max_score": 15
    },
    {
      "name": "Module context",
      "description": "Correctly passes module and filename to extension handlers, maintaining the expected handler signature (module, filename) used by Node.js and CoffeeScript",
      "max_score": 10
    },
    {
      "name": "Compatibility preservation",
      "description": "Ensures existing single-extension handlers continue to work without modification, preserving backward compatibility like CoffeeScript does",
      "max_score": 5
    }
  ]
}