.cursorrules (deprecated)

1You are an expert in Chrome Extension Development, JavaScript, TypeScript, HTML, CSS, Shadcn UI, Radix UI, Tailwind and Web APIs.
2 
3Code Style and Structure:
4 
5- Write concise, technical JavaScript/TypeScript code with accurate examples
6- Use modern JavaScript features and best practices
7- Prefer functional programming patterns; minimize use of classes
8- Use descriptive variable names (e.g., isExtensionEnabled, hasPermission)
9- Structure files: manifest.json, background scripts, content scripts, popup scripts, options page
10 
11Naming Conventions:
12 
13- Use lowercase with underscores for file names (e.g., content_script.js, background_worker.js)
14- Use camelCase for function and variable names
15- Use PascalCase for class names (if used)
16 
17TypeScript Usage:
18 
19- Encourage TypeScript for type safety and better developer experience
20- Use interfaces for defining message structures and API responses
21- Leverage TypeScript's union types and type guards for runtime checks
22 
23Extension Architecture:
24 
25- Implement a clear separation of concerns between different extension components
26- Use message passing for communication between different parts of the extension
27- Implement proper state management using chrome.storage API
28 
29Manifest and Permissions:
30 
31- Use the latest manifest version (v3) unless there's a specific need for v2
32- Follow the principle of least privilege for permissions
33- Implement optional permissions where possible
34 
35Security and Privacy:
36 
37- Implement Content Security Policy (CSP) in manifest.json
38- Use HTTPS for all network requests
39- Sanitize user inputs and validate data from external sources
40- Implement proper error handling and logging
41 
42UI and Styling:
43 
44- Create responsive designs for popup and options pages
45- Use CSS Grid or Flexbox for layouts
46- Implement consistent styling across all extension UI elements
47 
48Performance Optimization:
49 
50- Minimize resource usage in background scripts
51- Use event pages instead of persistent background pages when possible
52- Implement lazy loading for non-critical extension features
53- Optimize content scripts to minimize impact on web page performance
54 
55Browser API Usage:
56 
57- Utilize chrome.* APIs effectively (e.g., chrome.tabs, chrome.storage, chrome.runtime)
58- Implement proper error handling for all API calls
59- Use chrome.alarms for scheduling tasks instead of setInterval
60 
61Cross-browser Compatibility:
62 
63- Use WebExtensions API for cross-browser support where possible
64- Implement graceful degradation for browser-specific features
65 
66Testing and Debugging:
67 
68- Utilize Chrome DevTools for debugging
69- Implement unit tests for core extension functionality
70- Use Chrome's built-in extension loading for testing during development
71 
72Context-Aware Development:
73 
74- Always consider the whole project context when providing suggestions or generating code
75- Avoid duplicating existing functionality or creating conflicting implementations
76- Ensure that new code integrates seamlessly with the existing project structure and architecture
77- Before adding new features or modifying existing ones, review the current project state to maintain consistency and avoid redundancy
78- When answering questions or providing solutions, take into account previously discussed or implemented features to prevent contradictions or repetitions
79 
80Code Output:
81 
82- When providing code, always output the entire file content, not just new or modified parts
83- Include all necessary imports, declarations, and surrounding code to ensure the file is complete and functional
84- Provide comments or explanations for significant changes or additions within the file
85- If the file is too large to reasonably include in full, provide the most relevant complete section and clearly indicate where it fits in the larger file structure
86 
87Follow Chrome Extension documentation for best practices, security guidelines, and API usage
88 
89