javascript-chrome-apis-cursorrules-prompt-file — Cursor rule: Chrome
A Cursor rule that points the AI agent at Chrome extension work: manifest, architecture, Chrome API usage.
.cursor/rules/javascript-chrome-apis-cursorrules-prompt-file.mdcWhat javascript-chrome-apis-cursorrules-prompt-file 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.
What it helps with
- 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 for the agent
- 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
How to install javascript-chrome-apis-cursorrules-prompt-file
Manually: put the files in place
.cursor/rules/javascript-chrome-apis-cursorrules-prompt-file.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/javascript-chrome-apis-cursorrules-prompt-file.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/javascript-chrome-apis-cursorrules-prompt-file.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/javascript-chrome-apis-cursorrules-prompt-file.mdManually: put the files in place
.clinerules/javascript-chrome-apis-cursorrules-prompt-file.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about javascript-chrome-apis-cursorrules-prompt-file
How do I install javascript-chrome-apis-cursorrules-prompt-file in Cursor?
Create .cursor/rules/javascript-chrome-apis-cursorrules-prompt-file.mdc in your project root and paste the rule contents into it.
What does this rule do?
It configures the Cursor agent as a Chrome extension expert and covers the manifest, architecture, Chrome APIs, security, testing and publishing.
Does the rule apply to every file?
It sets alwaysApply: false with globs **/*, so it does not run automatically on every file.
Source text
javascript-chrome-apis-cursorrules-prompt-file.mdc · CC0-1.0
--- 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.
© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules