Explain step-by-step how to write a custom ESLint rule for [PROJECT_TYPE] that enforces [SPECIFIC_CODE_STYLE_OR_PATTERN]. Include details on: 1. Setting up the ESLint plugin structure 2. Writing the rule logic using [AST_TYPE] (Abstract Syntax Tree) traversal 3. Testing the rule with [TESTING_LIBRARY] 4. Integrating it into an existing [BUILD_TOOL] workflow Provide code examples for a rule that catches [COMMON_MISTAKE_OR_ANTI_PATTERN] in [FRAMEWORK_OR_LIBRARY] projects, with configuration options for [SEVERITY_LEVEL] and [CUSTOM_OPTIONS].