Browse

Chrome's storage API .cursorrules prompt files

Chrome's storage API allows web applications to store and retrieve data on a user's device, enhancing offline functionality and improving load times by reducing dependence on remote servers.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

dataclasses

Hono

Kong

AWS Lambda

AWS CloudWatch

RQ

Azure Functions

OAuth2

AWS API Gateway

microservices architecture

eslint

Deno

ServeMux

expo-localization

HTTPS

Detox

React Native Testing Library

fetch

RSC

Server Actions

Sentry

Server Components

React Query

Expo Router

CSS frameworks

Istio

js-yaml

mime-types

uuid

node-gyp

Ruby

poetry

next/image

Formik

Framer Motion

Linux

Netlify

Less

MDX

Sass

WordPress

Paraglide.js

PHPUnit

Alpine.js

Livewire

Dusk

JSON Web Tokens

Mongoose ODM

React.js

SEO

fetch API

React.ReactNode

React.FC

WCAG

Supabase Auth

react-dom

postcss

framer-motion

prisma

@types/node

Next.Js

@types/react

bcryptjs

autoprefixer

Material UI

yarn

WebAssembly

Composer

Biome

Cairo

Tailwind CSS.

Kotlin

Rell

React Server Components (RSC)

Angular

Next.js 14 App Router

Next.js SSR.

Axios

Cypress

Kubernetes

NoSQL

AWS

pytest-django

WhiteNoise

unittest

Django REST Framework

pip

python-dotenv

NumPy

joblib

Flask

tqdm

PyTorch

dask

virtual environments

Pytest-Recording

CliRunner

Pytest

VCRPy

Loguru

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: