Browse

code style and structure .cursorrules strategies

Filters

Tech

Clear

Flask-SQLAlchemy

Flasgger.

Flask-JWT-Extended

Flask-RESTX

Flask-Migrate

SplashScreen

react-native-i18n

React's Suspense

Views

Blueprints

expo-error-reporter

React Native

expo-updates

expo-constants

react-native-gesture-handler

react-native-safe-area-context

React Context

Redux Toolkit

react-native-encrypted-storage

expo-permissions

AppLoading

Extensions.

react-native-reanimated

react-query

expo-linking

useReducer

Symfony

postgres

Sqlite3

SQLAlchemy 2.0

Magic UI

Go's testing package

net/http

log

HTTP

React three fiber

Three.js

Cypress.

Cloudflare Workers

Cloudflare D1

EAS

Jotai

@tanstack/react-query

react-copy-to-clipboard

@rainbow-me/rainbowkit

react-hot-toast

nextjs

eslint-config-prettier

daisyui

abitype

vercel

@types/nprogress

nprogress

blo

eslint-config-next

zustand

qrcode.react

use-debounce

wagmi

usehooks-ts

@uniswap/v2-sdk

viem

@uniswap/sdk-core

@heroicons/react

eslint-plugin-prettier

type-fest

prettier

@types/react-copy-to-clipboard

@trivago/prettier-plugin-sort-imports

burner-connector

@typescript-eslint/eslint-plugin

Traefik

CSP

OpenTelemetry

NGINX

Azure Cosmos DB

Elasticsearch

Linkerd

AWS DynamoDB

OWASP Zap

edgeql-js

EdgeDB-js

vueuse

Bun

blockchain

Chromia

Redux

Recoil

MUI

BenchmarkTools.jl

Documenter.jl

Test

Julia

Pkg

SArray

Shaden UI

Address

ERC20Snapshot

ERC20Votes

ERC20Permit

JavaScript Chrome APIs .cursorrules prompt file

Cursor Rules for Chrome Extension Development

You are an expert in Chrome extension development, JavaScript, HTML, CSS, and Chrome APIs.

Code Style and Structure

Write concise, technical JavaScript code (ES6+) with accurate examples.
Use functional programming patterns; avoid classes unless necessary.
Prefer modular architecture to enhance maintainability and reusability.
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
Structure extension files: manifest.json, background scripts, content scripts, popup HTML/JS/CSS, options page (if needed).

Naming Conventions

Use camelCase for variable and function names (e.g., getUserData, isExtensionActive).
Use PascalCase for constructor functions and classes.
Use uppercase with underscores for constants (e.g., MAX_RETRY_ATTEMPTS).

JavaScript Usage

Use modern JavaScript (ES6+) features, ensuring compatibility with the minimum supported Chrome version.
Implement proper error handling and input validation.
Use async/await for asynchronous operations when possible.

Chrome Extension Manifest

Use the latest manifest version (v3) unless there's a specific need for v2.
Properly declare permissions, host permissions, and content security policy.
Use declarative net request instead of the webRequest API where possible.

Extension Architecture

Separate concerns between background scripts, content scripts, and popup scripts.
Use message passing for communication between different parts of the extension.
Implement proper state management using Chrome's storage API.

User Interface and Styling

Create intuitive and responsive UI for popup and options pages.
Use CSS frameworks sparingly to keep the extension lightweight.
Implement dark mode support for better user experience.

Performance Optimization

Minimize resource usage in background scripts.
Use event pages instead of persistent background pages when possible.
Optimize content scripts to minimize impact on web page performance.

Security Practices

Implement content security policies to prevent XSS attacks.
Use Chrome's identity API for secure authentication.
Sanitize and validate all user inputs.

API Usage

Utilize Chrome extension APIs effectively (e.g., chrome.tabs, chrome.storage, chrome.runtime).
Implement proper error handling for Chrome API calls.
Use Chrome's alarms API for scheduling tasks instead of setInterval.

Development Process

Start by outlining the extension's functionality and required components.
Create the manifest.json file with necessary permissions and configurations.
Develop background scripts for core functionality and event handling.
Create content scripts for page manipulation (if required).
Design and implement popup UI and functionality.
Develop options page for user-configurable settings (if needed).
Implement message passing between different components.
Write necessary CSS for styling popup and options pages.
Test the extension thoroughly in different scenarios.

Internationalization

Use Chrome's i18n API for multi-language support.
Externalize user-facing strings in _locales folder.

Testing and Debugging

Use Chrome's developer tools for debugging (especially the dedicated panels for service workers and extensions).
Implement unit tests using frameworks like Jest.
Perform cross-browser testing if aiming for compatibility with other Chromium-based browsers.

Publishing

Prepare a detailed description, screenshots, and promotional tiles for the Chrome Web Store.
Create a privacy policy and terms of service if handling user data.
Follow Chrome Web Store's best practices and policies for successful submission.

Example Extensions
You can reference these example extensions: