Skip to main content
prompt GP ChatGPT

Browser Extension taste — ChatGPT prompt: what it does, how to install

Browser Extension taste — a prompt for ChatGPT and Claude Code defines best practices for building cross-browser extensions on Manifest V3. It guides the AI when designing extension architecture.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Browser Extension taste does

This prompt sets architectural standards for developing Manifest V3 browser extensions with a focus on service worker lifecycles. It directs the AI to use frameworks like WXT or Plasmo, request minimal permissions, isolate UI with Shadow DOM, and handle storage securely via chrome.storage.

The guidelines cover scheduling background tasks with chrome.alarms, validating messages from content scripts, and applying declarativeNetRequest for network modifications without unsafe code evaluation.

To apply the rules, provide the prompt text to your AI session or save it as .claude/commands/prompts.csv.md for Claude Code.

What it helps with

  • design a Manifest V3 browser extension architecture
  • configure secure storage with chrome storage APIs
  • isolate extension UI inside a Shadow DOM
  • validate messages from untrusted content scripts
  • set up Playwright end to end tests for extensions

Example prompts for the agent

  • Review our extension architecture following the Browser Extension taste guidelines
  • Help me implement background alarms using chrome alarms instead of setInterval
  • Refactor our content script injection to use chrome scripting safely

How to install Browser Extension taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Browser Extension taste

How to install Browser Extension taste in Claude Code?

Create a file named .claude/commands/prompts.csv.md and save the prompt text inside it.

What does Browser Extension taste do?

It provides architectural standards and coding patterns for developing cross-browser extensions on Manifest V3.

What tools and frameworks are referenced?

The prompt mentions Manifest V3, WXT, Plasmo, TypeScript, Vite, Shadow DOM, Playwright, and browser extension APIs.

Source text

prompts.csv · CC0-1.0
# Browser Extension taste of a cross-browser extension developer
- Build on Manifest V3 and plan around service workers that can be stopped at any time. Confidence: 0.95
- Use a framework like WXT or Plasmo with TypeScript and Vite to handle builds, reloads and cross-browser manifests. Confidence: 0.80
- Request the fewest permissions possible, and prefer activeTab and optional_permissions over broad host access. Confidence: 0.95
- Never request the all_urls host permission unless the core feature truly needs every site. Confidence: 0.90
- Keep no important state in service worker globals and persist it with chrome.storage instead. Confidence: 0.95
- Use chrome.storage.session for temporary secrets and chrome.storage.local or sync for user settings, with a typed wrapper and defaults. Confidence: 0.85
- Use chrome.alarms for scheduled work instead of setInterval in the background. Confidence: 0.90
- Register all event listeners at the top level of the service worker so they survive restarts. Confidence: 0.90
- Keep content scripts small and inject them programmatically with chrome.scripting when possible. Confidence: 0.85
- Isolate injected UI in a Shadow DOM so page styles and extension styles cannot collide. Confidence: 0.90
- Treat every message from content scripts and web pages as untrusted and validate it with a schema. Confidence: 0.95
- Define message types in one shared module and use typed request and response helpers for runtime messaging. Confidence: 0.85
- Never inject remote code or use eval, and keep a strict Content Security Policy. Confidence: 0.95
- Use declarativeNetRequest for blocking or modifying requests instead of trying to intercept them in code. Confidence: 0.85
- Use the webextension-polyfill or a framework layer so the same code runs on Chrome, Firefox, Edge and Safari. Confidence: 0.80
- Collect as little user data as possible and explain clearly in the store listing what is stored and why. Confidence: 0.90
- Handle install and update events to migrate stored settings between versions. Confidence: 0.85
- Test popup and options pages as normal web UI, and run end-to-end tests with Playwright loading the unpacked extension. Confidence: 0.80
- Automate builds, version bumps and store uploads in CI, with one zip artifact per browser. Confidence: 0.80
- Keep the popup fast by loading heavy data lazily and showing cached state first. Confidence: 0.80
- Write a short permission justification for each permission before submitting to the store. Confidence: 0.85

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Frontend and UI →

From the same set218

The whole set →
.NET Web API taste .NET Web API taste — a prompt for ChatGPT defines .NET Web API standards for a pragmatic C# engineer. Runs during backend design and code generation. GP ChatGPT ★ 178,201repo stars Laravel App taste The Laravel App taste ChatGPT prompt sets practical conventions for building Laravel and PHP apps. It guides work on controllers, validation, queues, tests, and deployment. GP ChatGPT ★ 178,201repo stars Flutter App taste Flutter App taste — a prompt for ChatGPT that defines architectural standards for cross-platform mobile apps on Flutter. Used when structuring codebases and setting up projects. GP ChatGPT ★ 178,201repo stars Webhook Integration taste The Webhook Integration taste ChatGPT prompt sets rules for reliable webhook integrations. It covers event intake, processing, and delivery to customer endpoints. GP ChatGPT ★ 178,201repo stars Rails App taste Rails App taste is a prompt for ChatGPT, Claude.ai, and Claude Code that sets pragmatic Ruby on Rails development standards. Use it before starting an app or planning its architecture. GP ChatGPT ★ 178,201repo stars Authentication taste Authentication taste — a prompt for ChatGPT, Claude.ai, and Claude Code that defines security standards for backend development. It guides agents in evaluating authentication architecture. GP ChatGPT ★ 178,201repo stars Realtime WebSocket taste Realtime WebSocket taste — a prompt for ChatGPT with engineering guidance for real-time WebSocket systems. It covers transport choices, connection security, reconnects, and message delivery. GP ChatGPT ★ 178,201repo stars Serverless Functions taste Serverless Functions taste — a prompt for ChatGPT and Claude Code defines design rules for serverless functions to cut cold starts and optimize database connections. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open