A Chrome extension that transforms your prompts into genius-level writing with AI assistance.
- Enhance prompts for different contexts (creative, technical, business, educational)
- Adjustable creativity settings
- Advanced mode for more detailed enhancements
- Conversation history
- Copy-to-clipboard functionality
- Template-based prompt suggestions
This project is built with:
- React
- TypeScript
- Vite
- ShadCN UI
- TailwindCSS
- Clone the repository
- Install dependencies:
npm install
- Set up environment variables:
- Copy
.env.example
to.env
- Replace the placeholder with your actual Claude API key
cp .env.example .env
- Copy
- Start the development server:
npm run dev
To build the extension for production:
npm run build
This will create a dist
directory with the built extension.
Follow these steps to publish your extension to the Chrome Web Store:
-
Create proper icons for your extension:
- icon-16.png (16x16 pixels)
- icon-48.png (48x48 pixels)
- icon-128.png (128x128 pixels)
Place these in the
public/icons
directory. -
Build your extension:
npm run build
-
Create a ZIP file of the
dist
directory:cd dist zip -r ../genius-prompt-enhancer.zip *
- Go to the Chrome Web Store Developer Dashboard
- Sign in with your Google account
- Pay the one-time developer registration fee ($5)
-
Click "New Item" in the Developer Dashboard
-
Upload your ZIP file
-
Fill in the required information:
- Name: Genius Prompt Enhancer
- Description: Transform your prompts into genius-level writing with AI assistance
- Category: Productivity
- Language: English
- Screenshots: Add at least one screenshot of your extension in action
- Promotional images (optional)
- Privacy policy URL (required if you collect user data)
-
Submit for review
The review process typically takes a few business days. You'll receive an email when your extension is approved or if there are issues to address.
To update your extension:
- Make your changes
- Increment the version number in
public/manifest.json
- Build and create a new ZIP file
- Upload the new ZIP in the Developer Dashboard
- The extension uses environment variables for API keys, improving security
- API keys are included in the build but not hardcoded in the source code
- For a production version with real API calls, you should:
- Use a backend service for API calls to avoid exposing keys in the client
- Implement proper authentication and authorization
- Add rate limiting to prevent abuse
- Consider using a proxy service to handle API requests
The following environment variables are used in this project:
Variable | Description | Required |
---|---|---|
VITE_CLAUDE_API_KEY |
Your Claude API key | Yes |
To set up environment variables:
- Copy
.env.example
to.env
- Replace the placeholder values with your actual API keys
- The
.env
file is ignored by git to prevent accidental exposure of sensitive information
MIT
Created by Firas Latrach