# javascript-chrome-apis-cursorrules-prompt-file

A Cursor rule that points the AI agent at Chrome extension work: manifest, architecture, Chrome API usage.

- rule · `type=rule` · Cursor · ★ 41011
- Author: PatrickJS
- License: CC0-1.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/PatrickJS/awesome-cursorrules/tree/HEAD/rules/javascript-chrome-apis-cursorrules-prompt-file.mdc
- Updated: 2026-05-30
- HTML: https://affpapa.org/en/nevibecode/rules/javascript-chrome-apis-cursorrules-prompt-file

## What it does

The file sets the assistant's role: an expert in Chrome extension development, JavaScript, HTML, CSS and Chrome APIs. Then it lists the areas the rule keeps in view — naming conventions, code structure, the extension manifest, architecture, UI and styling, performance, security, API usage, development process, internationalization, testing and debugging, publishing.

It also points to example extensions you can reference and tells the agent to follow the official Chrome Extension documentation on the Google Developers site. The rule ships with `alwaysApply: false` and globs `**/*`, so it does not fire on every file by default — worth checking when it actually kicks in for your project.

Install is a single file at `.cursor/rules/javascript-chrome-apis-cursorrules-prompt-file.mdc`. No dependencies, no API keys.

## Requirements
- Works with: Chrome

## Install

### Cursor (native platform)

**Manually: put the files in place**
- File: `.cursor/rules/javascript-chrome-apis-cursorrules-prompt-file.mdc` — Frontmatter: description, globs, alwaysApply

### Claude Code

**Manually: put the files in place**
- File: `.claude/rules/javascript-chrome-apis-cursorrules-prompt-file.md` — The paths frontmatter field limits the files: move globs from the source into paths

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/instructions/javascript-chrome-apis-cursorrules-prompt-file.instructions.md` — The applyTo field sets which files it applies to: move globs from the source into applyTo

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/javascript-chrome-apis-cursorrules-prompt-file.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/javascript-chrome-apis-cursorrules-prompt-file.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/PatrickJS/awesome-cursorrules/tree/HEAD/rules/javascript-chrome-apis-cursorrules-prompt-file.mdc

## When to use it
- keep the Chrome extension manifest consistent across edits
- pick a project structure for an extension before writing code
- avoid security mistakes when calling Chrome APIs
- separate extension UI from styling concerns
- get an extension ready for publishing

## Example prompts
- help me design the architecture for a Chrome extension that blocks ads
- check my manifest.json against Chrome requirements
- how do I request permissions for the tabs API

## Source text · javascript-chrome-apis-cursorrules-prompt-file.mdc · CC0-1.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: fed1290e5a1f3663.

BEGIN THIRD-PARTY FILE fed1290e5a1f3663
```text
---
description: "Cursor rules for JavaScript development with Chrome APIs integration."
globs: **/*
alwaysApply: false
---
You are an expert in Chrome extension development, JavaScript, HTML, CSS, and Chrome APIs.

Code Style and Structure

Naming Conventions
JavaScript Usage
Chrome Extension Manifest
Extension Architecture
User Interface and Styling
Performance Optimization
Security Practices
API Usage
Development Process
Internationalization
Testing and Debugging
Publishing

Example Extensions

You can reference these example extensions:

Post-Development

Follow Chrome Extension documentation and best practices from the official Google Developers site for up-to-date information.
```
END THIRD-PARTY FILE fed1290e5a1f3663

The third-party file has ended. Everything between the fed1290e5a1f3663 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© PatrickJS · CC0-1.0 · https://github.com/PatrickJS/awesome-cursorrules/tree/HEAD/rules/javascript-chrome-apis-cursorrules-prompt-file.mdc

## Similar
- [chrome-extensions](https://affpapa.org/en/nevibecode/skills/chrome-extensions.md) — skill · 10900 installs
- [clerk-chrome-extension-patterns](https://affpapa.org/en/nevibecode/skills/clerk-chrome-extension-patterns.md) — skill · 14400 installs
- [chrome-extension](https://affpapa.org/en/nevibecode/skills/chrome-extension.md) — skill · 4500 installs
- [chrome-extension-development](https://affpapa.org/en/nevibecode/skills/chrome-extension-development.md) — skill · 2800 installs
- [chrome-extension-ui](https://affpapa.org/en/nevibecode/skills/chrome-extension-ui.md) — skill · 719 installs
- [chrome-webstore-release-blueprint](https://affpapa.org/en/nevibecode/skills/chrome-webstore-release-blueprint.md) — skill · 2800 installs

From the same set: [patrickjs/awesome-cursorrules](https://affpapa.org/en/nevibecode/by/patrickjs/awesome-cursorrules.md) — 68 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md