linshenkx/prompt-optimizer

★ 34,803⑂ 0

An AI prompt optimizer for writing better prompts and getting better AI results.

About linshenkx/prompt-optimizer

linshenkx/prompt-optimizer is an open-source project on GitHub, mainly written in TypeScript. An AI prompt optimizer for writing better prompts and getting better AI results. It currently holds 34,803 stars and 0 forks with 0 open issues, and was last pushed on an unknown date (repository created unknown).

Project Overview

AI Homed tracks it on the AI Models & LLM Tools board.

GitHub Repository Details

Repository linshenkx/prompt-optimizer · default branch - · size 0 KB · watchers 0 · source: GitHub REST API and repository README

README

Prompt Optimizer 🚀

English | 中文

GitHub stars Chrome Web Store Users

https://github.com/linshenkx/prompt-optimizer/blob/HEAD/linshenkx%2Fprompt-optimizer | Trendshift

License Docker Pulls GitHub forks Deploy with Vercel

Website | Online Optimizer | Prompt Garden | Docs | Quick Start | Chrome Extension | 💖 Support

Development Docs | Vercel Deployment Guide | Cloudflare Deployment Guide | MCP Deployment Guide | DeepWiki Docs | ZRead Docs

📖 Project Introduction

Prompt Optimizer is a powerful AI prompt optimization tool that helps you write better AI prompts and improve the quality of AI outputs. It supports four usage methods: web application, desktop application, Chrome extension, and Docker deployment.

Prompts can start from manual writing, templates, local imports, or sources such as Prompt Garden. Prompt Optimizer is where those prompts are optimized, tested, evaluated, and saved as reusable prompt assets.

🎥 Feature Demonstration

1. Hard-Nosed Reviewer: Turn Agreement into Useful Critique

Starting from a minimal English role prompt, optimization pushes a small model away from generic pushback and toward a clearer, more structured review that surfaces weak assumptions, evidence gaps, and concrete revision advice.

https://github.com/linshenkx/prompt-optimizer/blob/HEAD/Hard-nosed reviewer full-page demo

2. Marketplace Bargaining Reply: Let Variables Change the Strategy

With a single reusable prompt template, you can swap in item details, price anchors, buyer offers, tone, and negotiation goals for different marketplace conversations. After optimization, the same small model does a better job turning those variables into a clearer, more transaction-ready reply instead of a generic helper-style response.

https://github.com/linshenkx/prompt-optimizer/blob/HEAD/Marketplace bargaining reply variable-mode demo

3. Text-to-Image: Optimize a One-Line Idea into a More Directable Key Visual Prompt

This is not just prompt expansion. Starting from a vague one-line idea, Prompt Optimizer adds clearer subject cues, spatial relationships, and mood anchors. The left side is simply “a floating library in the night sky,” while the optimized version gives the model a more directed fantasy composition that feels closer to a reusable key visual than a lucky generic image.

https://github.com/linshenkx/prompt-optimizer/blob/HEAD/Floating library text-to-image demo

✨ Core Features

🚀 Advanced Features

Image Generation Mode

Prompt Sources & Smart Favorites

Advanced Testing Mode

For detailed usage instructions, please refer to the Image Mode Documentation

Quick Start

1. Use Online Version (Recommended)

Direct access: https://prompt.always200.com

This is a pure frontend project with all data stored locally in your browser and never uploaded to any server, making the online version both safe and reliable to use.

2. Web Deployment

Vercel Deployment

Method 1: One-click deployment to your own Vercel: Deploy with Vercel

Method 2: Fork the project and import to Vercel (Recommended):

For more detailed deployment steps and important notes, please check:

Cloudflare Deployment

Deploy to Cloudflare

Use the Deploy to Cloudflare button for the quickest public-repository setup. It creates a repository under your GitHub/GitLab account and deploys with Workers Builds. For private repositories or stricter repository-access control, import your own repository manually; keep the default deploy commands and clear the build command if Cloudflare auto-fills pnpm run build, because wrangler.jsonc builds the Web frontend and publishes packages/web/dist as static assets.

For access control and analytics on Cloudflare, configure Cloudflare Access and Cloudflare Web Analytics in the Cloudflare dashboard. No frontend dependency or application-code change is required.

3. Download Desktop Application

Download the latest version from GitHub Releases. We provide both installer and archive formats for each platform. Core Advantages of Desktop Application:

4. Install Chrome Extension

1. Install from Chrome Web Store (may not be the latest version due to approval delays): Chrome Web Store 2. Click the icon to open the Prompt Optimizer

5. Docker Deployment

Click to view Docker deployment commands
# Run container (default configuration)
docker run -d -p 8081:80 --restart unless-stopped --name prompt-optimizer linshen/prompt-optimizer

Run container (with API key configuration and password protection)

docker run -d -p 8081:80 \ -e VITE_OPENAI_API_KEY=your_key \ -e ACCESS_USERNAME=your_username \ # Optional, defaults to "admin" -e ACCESS_PASSWORD=your_password \ # Set access password --restart unless-stopped \ --name prompt-optimizer \ linshen/prompt-optimizer

6. Docker Compose Deployment

Click to view Docker Compose deployment steps
# 1. Clone the repository
git clone https://github.com/linshenkx/prompt-optimizer.git
cd prompt-optimizer

2. Create .env file for API keys and authentication

cat > .env << EOF

API Key Configuration

VITE_OPENAI_API_KEY=your_openai_api_key VITE_GEMINI_API_KEY=your_gemini_api_key VITE_DEEPSEEK_API_KEY=your_deepseek_api_key VITE_GROK_API_KEY=your_xai_api_key VITE_ZHIPU_API_KEY=your_zhipu_api_key VITE_SILICONFLOW_API_KEY=your_siliconflow_api_key

Basic Authentication (Password Protection)

ACCESS_USERNAME=your_username # Optional, defaults to "admin" ACCESS_PASSWORD=your_password # Set access password EOF

Because the compose file is under docker/, pass the root .env explicitly.

3. Start the service

docker compose --env-file .env -f docker/docker-compose.yml up -d

4. View logs

docker compose --env-file .env -f docker/docker-compose.yml logs -f

5. Access the service

Web Interface: http://localhost:8081 MCP Server: http://localhost:8081/mcp

You can also directly edit the docker/docker-compose.yml file to customize your configuration:

Click to view docker/docker-compose.yml example

services:
  prompt-optimizer:
    # Use Docker Hub image
    image: linshen/prompt-optimizer:latest
    container_name: prompt-optimizer
    restart: unless-stopped
    ports:
  • "8081:80" # Web application port (MCP server accessible via /mcp path)
environment:
  • VITE_OPENAI_API_KEY=your_openai_key
  • VITE_GEMINI_API_KEY=your_gemini_key
  • VITE_GROK_API_KEY=your_xai_key
# Access Control (Optional)
  • ACCESS_USERNAME=admin
  • ACCESS_PASSWORD=your_password

7. MCP Server Usage Instructions

Click to view MCP Server usage instructions

Prompt Optimizer now supports the Model Context Protocol (MCP), enabling integration with AI applications that support MCP such as Claude Desktop.

When running via Docker, the MCP Server automatically starts and can be accessed via http://ip:port/mcp.

Environment Variable Configuration

MCP Server requires API key configuration to function properly. Main MCP-specific configurations:

# MCP Server Configuration
MCP_DEFAULT_MODEL_PROVIDER=openai  # Options: openai, gemini, anthropic, deepseek, grok, siliconflow, zhipu, dashscope, openrouter, modelscope, custom
MCP_LOG_LEVEL=info                 # Log level

Using MCP in Docker Environment

In a Docker environment, the MCP Server runs alongside the web application. You can access the MCP service through the same port as the web application at the /mcp path.

For example, if you map the container's port 80 to port 8081 on the host:

docker run -d -p 8081:80 \
  -e VITE_OPENAI_API_KEY=your-openai-key \
  -e MCP_DEFAULT_MODEL_PROVIDER=openai \
  --name prompt-optimizer \
  linshen/prompt-optimizer

The MCP Server will then be accessible at http://localhost:8081/mcp.

Claude Desktop Integration Example

To use Prompt Optimizer in Claude Desktop, you need to add the service configuration to Claude Desktop's configuration file.

1. Find Claude Desktop's configuration directory:

  • Windows: %APPDATA%\Claude\services
  • macOS: ~/Library/Application Support/Claude/services
  • Linux: ~/.config/Claude/services
2. Edit or create the services.json file, adding the following content:

{
  "services": [
    {
      "name": "Prompt Optimizer",
      "url": "http://localhost:8081/mcp"
    }
  ]
}

Make sure to replace localhost:8081 with the actual address and port where you've deployed Prompt Optimizer.

Available Tools

  • optimize-user-prompt: Optimize user prompts to improve LLM performance
  • optimize-system-prompt: Optimize system prompts to improve LLM performance
  • iterate-prompt: Iteratively improve mature prompts based on specific requirements
For more detailed information, please refer to the MCP Server User Guide.

⚙️ API Key Configuration

Click to view API key configuration methods

Method 1: Via Interface (Recommended)

1. Click the "⚙️Settings" button in the upper right corner 2. Select the "Model Management" tab 3. Click on the model you need to configure (such as OpenAI, Gemini, DeepSeek, Grok, etc.) 4. Enter the corresponding API key in the configuration box 5. Click "Save"

Supported models: OpenAI, Gemini, DeepSeek, Grok, Zhipu AI, SiliconFlow, Custom API (OpenAI compatible interface)

In addition to API keys, you can configure advanced LLM parameters for each model individually. These parameters are configured through a field called llmParams, which allows you to specify any parameters supported by the LLM SDK in key-value pairs for fine-grained control over model behavior.

Advanced LLM Parameter Configuration Examples:

  • OpenAI/Compatible APIs: {"temperature": 0.7, "max_tokens": 4096, "timeout": 60000}
  • Gemini: {"temperature": 0.8, "maxOutputTokens": 2048, "topP": 0.95}
  • DeepSeek: {"temperature": 0.5, "top_p": 0.9, "frequency_penalty": 0.1}
For more detailed information about llmParams configuration, please refer to the LLM Parameters Configuration Guide.

Method 2: Via Environment Variables

Configure environment variables through the -e parameter when deploying with Docker:
-e VITE_OPENAI_API_KEY=your_key
-e VITE_GEMINI_API_KEY=your_key
-e VITE_DEEPSEEK_API_KEY=your_key
-e VITE_GROK_API_KEY=your_key
-e VITE_ZHIPU_API_KEY=your_key
-e VITE_SILICONFLOW_API_KEY=your_key

Multiple Custom Models Configuration (Unlimited Quantity)

-e VITE_CUSTOM_API_KEY_ollama=dummy_key -e VITE_CUSTOM_API_BASE_URL_ollama=http://localhost:11434/v1 -e VITE_CUSTOM_API_MODEL_ollama=qwen2.5:7b
📖 Detailed Configuration Guide: See Multiple Custom Models Documentation for complete configuration methods and advanced usage

Local Development

For detailed documentation, see Development Documentation
Click to view local development commands
# 1. Clone the project
git clone https://github.com/linshenkx/prompt-optimizer.git
cd prompt-optimizer

2. Install dependencies

pnpm install

3. Start development server

pnpm dev # Main development command: build core/ui and run web app pnpm dev:web # Run web app only pnpm dev:fresh # Complete reset and restart development environment

🗺️ Roadmap

For detailed project status, see Project Status Document

📖 Related Documentation

Star History

https://github.com/linshenkx/prompt-optimizer/blob/HEAD/Star History Chart

FAQ

Click to view frequently asked questions

API Connection Issues

Q1: Why can't I connect to the model service after configuring the API key?

A: Most connection failures are caused by Cross-Origin Resource Sharing (CORS) issues. As this project is a pure frontend application, browsers block direct access to API services from different origins for security reasons. Model services will reject direct requests from browsers if CORS policies are not correctly configured.

Q2: How to solve Ollama connection issues?

A: Ollama fully supports the OpenAI standard interface, just configure the correct CORS policy: 1. Set environment variable OLLAMA_ORIGINS=* to allow requests from any origin 2. If issues persist, set OLLAMA_HOST=0.0.0.0:11434 to listen on any IP address

Q3: How to solve CORS issues with commercial APIs (such as Nvidia's DS API, ByteDance's Volcano API)?

A: These platforms typically have strict CORS restrictions. Recommended solutions:

1. Use Desktop Application (Most Recommended)

  • Desktop app has no CORS restrictions as a native application
  • Can directly connect to any API service, including locally deployed models
  • Provides the most complete and stable feature experience
  • Download from GitHub Releases
2. Use Self-deployed API Proxy Service (Professional solution)
  • Deploy open-source API aggregation/proxy tools like OneAPI, NewAPI
  • Configure as custom API endpoint in settings
  • Request flow: Browser → Proxy service → Model service provider
  • Full control over security policies and access permissions
Note: All web versions (including online version, Vercel deployment, Docker deployment) are pure frontend applications and subject to browser CORS restrictions. Only the desktop version or using an API proxy service can solve CORS issues.

Q4: I have correctly configured CORS policies for my local model (like Ollama), why can't I still connect using the online version?

A: This is caused by the browser's Mixed Content security policy. For security reasons, browsers block secure HTTPS pages (like the online version) from sending requests to insecure HTTP addresses (like your local Ollama service).

Solutions: To bypass this limitation, you need to have the application and API under the same protocol (e.g., both HTTP). We recommend the following approaches: 1. Use the desktop version: Desktop applications have no browser restrictions and are the most stable and reliable way to connect to local models 2. Use Docker deployment (HTTP): Access via http://localhost:8081, both the app and local Ollama use HTTP 3. Use Chrome extension: Extensions can bypass some security restrictions in certain situations

macOS Desktop Application Issues

Q5: macOS shows "damaged" or "unverified developer" when opening the app?

A: This is because the application has not been signed with an Apple Developer certificate. Due to the high cost of Apple Developer accounts, the desktop application is currently unsigned.

Solution: Run the following command in Terminal to remove the quarantine attribute:

```bash

For installed applications

xattr -rd com.apple.quarantine /Applications/PromptOptimizer.app

For downloaded .dmg files (run before installation)

GitHub Stars & Activity

34,803Stars
0Forks
0Open issues
TypeScriptLanguage

GitHub Popularity

GitHub stars34,803
Forks0
Open issues0
Primary languageTypeScript
License-
Stars gained today0
Created-
Last pushed-

Trending History

Trending statusnot on today's boards

Related AI Projects

1

firecrawl / firecrawl

TypeScript★ 180,977⑂ 0
2

langgenius / dify

TypeScript★ 155,892⑂ 0
3

thedotmack / claude-mem

TypeScript★ 93,998⑂ 0
4

OpenHands / OpenHands

TypeScript★ 88,068⑂ 0
5

upstash / context7

TypeScript★ 62,071⑂ 0
6

FlowiseAI / Flowise

TypeScript★ 55,466⑂ 0
7

janhq / jan

TypeScript★ 44,490⑂ 0
8

CopilotKit / CopilotKit

TypeScript★ 37,378⑂ 0

More AI Rankings