Steal My Prompt & Build Chrome Extensions Using Only AI

[@ishan.girdhar]

Thank you, subscribed.

[@ai_monika]

Thank you for your support 💕

[@Nardevchoudhary]

amazing video loved it, can you attach the prompt file in the description!!!

[@ishan.girdhar]

Here:
1. Extension Name: [Provide a name for your extension]
2. Purpose: [Describe the main purpose or functionality of the extension]
3. Target Users: [Specify the intended audience or users of the extension]
4. Key Features:
- [List the main features you want in the extension]
- [Add as many bullet points as needed]
5. User Interface:
- [Describe how the extension should appear (e.g., popup, toolbar icon,
options page)]
- [Specify any design preferences or requirements]
6. Permissions: [List any specific permissions the extension might need (e.g.,
storage, tabs, activeTab)]
7. Integration: [Describe how the extension should interact with web pages or
other browser features]
8. Additional Requirements:
- [Include any other specific requirements or preferences)
- [Such as performance considerations, compatibility, etc.]
9. Code Preferences:
- JavaScript Variant: [Specify if you prefer vanilla JavaScript, TypeScript, or any
other compile-to-JS language]
- Framework: [Indicate if you want to use any framework like React, Vue, or
vanilla JS]
- Build Tools: (Specify if you want to use any build tools like Webpack, Parcel,
or none]
- Coding Style: [Mention any specific coding standards, linting rules, or style
guides to follow]
- Module System: [Specify preference for ES6 modules, CommonS, or any
other module system]
- Browser API Usage: [Indicate any preferences for using specific Chrome
extension APIs]
10. File Structure: Please include the following files as needed for the
extension. (Note: You can remove any files that aren't necessary for your
specific extension)
a) manifest.json
- Purpose: The configuration file for your extension. Always required.
- Include: Yes/No (Always Yes)
b) background.js
- Purpose: Runs in the background and manages extension behavior.
- Include: Yes/No API
- Note: Include if your extension needs to perform actions even when not
actively used.
C) content.js
- Purpose: Interacts directly with web pages the user visits.
- Include: Yes/No Pull up for
- Note: Include if your extension needs to modify or interact with web page
content.
d) popup.html and popup.js
- Purpose: Creates a popup interface when the extension icon is clicked.
- Include: Yes/No
- Note: Include if you want a popup menu or interface for your extension.
e) options.html and options.js
- Purpose: Provides a page for users to customize extension settings.
- Include: Yes/No
- Note: Include if your extension has configurable options.
f) CSS files
- Purpose: Styles the visual elements of your extension.
- Include: Yes/No
- Note: Include if you need custom styling for popup, options page, or injected
content.
g) Additional files
- Purpose: Any other files specific to your extension's functionality.
- Description: [Briefly describe any additional files you need]
11. Icons: I want to use an icon. However, the only sizes I can supply are 48x48
and 128x128.
12. Testing: [Describe any specific testing requirements or scenarios)
For each file you include, please provide:
For each file you include, please provide:
- A basic structure of the file
- Comments explaining key functionalities
- Any necessary connections or references to other files
Please provide all the files separately. Also, include comments in the code to
explain key functionalities.