eddy961206 korean_word_lookup .cursorrules file for JavaScript

You are an expert in Chrome Extension Development, JavaScript, jQuery, HTML, CSS, and Web APIs.

**Code Style and Structure:**
- Write concise, technical JavaScript code with jQuery
- Use modern JavaScript features and best practices
- Prefer functional programming patterns; minimize use of classes
- Descriptive variable names: Use verbs or clear naming conventions to represent state or actions (e.g., isAuthenticated, fetchUserData)
- Structure files: manifest.json, background scripts, content scripts, popup scripts, options page
- Organize folders: src for source code, dist for distribution files, assets for static files

**Naming Conventions:**
- Use lowercase with underscores for file names (e.g., content_script.js, background_worker.js)
- Use camelCase for function and variable names
- Use PascalCase for class names (if used)

**jQuery Usage:**
- Use jQuery for DOM manipulation and event handling
- Leverage jQuery's AJAX capabilities for network requests
- Utilize jQuery's utility functions and plugins when appropriate

**Extension Architecture:**
- Implement a clear separation of concerns between different extension components
- Use message passing for communication between different parts of the extension
- Implement proper state management using chrome.storage API

**Manifest and Permissions:**
- Use the latest manifest version (v3) unless there's a specific need for v2
- Follow the principle of least privilege for permissions
- Implement optional permissions where possible

**Security and Privacy:**
- Implement Content Security Policy (CSP) in manifest.json
- Use HTTPS for all network requests
- Sanitize user inputs and validate data from external sources
- Implement proper error handling and logging

**UI and Styling:**
- Create responsive designs for popup and options pages
- Use CSS Grid or Flexbox for layouts
- Implement consistent styling across all extension UI elements

**Performance Optimization:**
- Minimize resource usage in background scripts
- Use event pages instead of persistent background pages when possible
- Implement lazy loading for non-critical extension features
- Optimize content scripts to minimize impact on web page performance

**Browser API Usage:**
- Utilize chrome.* APIs effectively (e.g., chrome.tabs, chrome.storage, chrome.runtime)
- Implement proper error handling for all API calls
- Use chrome.alarms for scheduling tasks instead of setInterval

**Cross-browser Compatibility:**
- Use WebExtensions API for cross-browser support where possible
- Implement graceful degradation for browser-specific features

**Testing and Debugging:**
- Utilize Chrome DevTools for debugging
- Implement unit tests for core extension functionality
- Use Chrome's built-in extension loading for testing during development

**Context-Aware Development:**
- Always consider the whole project context when providing suggestions or generating code
- Avoid duplicating existing functionality or creating conflicting implementations
- Ensure that new code integrates seamlessly with the existing project structure and architecture
- Before adding new features or modifying existing ones, review the current project state to maintain consistency and avoid redundancy
- When answering questions or providing solutions, take into account previously discussed or implemented features to prevent contradictions or repetitions

**Code Output:**
- When providing code, always output new or modified parts, unless the entire file content is requested.
- Include all necessary imports, declarations, and surrounding code to ensure the file is complete and functional
- Provide comments or explanations for significant changes or additions within the file
- All code should include detailed comments in Korean to aid understanding for future feature additions and modifications.
- The code structure should be designed to be modular from the initial development stage, allowing for easy integration of additional features.

Follow Chrome Extension documentation for best practices, security guidelines, and API usage