Prompt Master

Install

mkdir -p ~/.claude/skills
git clone https://github.com/nidhinjs/prompt-master.git ~/.claude/skills/prompt-master

This is third-party code. Review the repository files before installing.

What it does

The skill detects which AI tool the prompt is for, extracts task, constraints, context and success criteria, and asks at most three clarifying questions if something critical is missing. It then picks a prompt structure, strips words that do not change the output and returns one copyable block with a one-line strategy note. It has profiles for 20+ tools and a universal fallback for the rest.

Who it is for. Anyone who regularly writes prompts for coding agents, chat models, or image and video generators.

Example request

Write a Claude Code prompt to build a todo app with React and Supabase, and ask me what you need to know

Limitations

The skill only activates when you explicitly ask to write, fix or adapt a prompt. The author recommends installing via claude.ai and marks cloning into Claude Code's skills folder as not suggested.

How to disable. Remove the skill in claude.ai under Customize > Skills, or delete ~/.claude/skills/prompt-master.

Security check

• The skill is instruction-only

README in short

Prompt Master is a Claude skill that writes prompts for a specific AI tool so you stop burning attempts on re-prompting. The README lists supported tools from ChatGPT and Codex to Midjourney, Sora and ElevenLabs. It describes an eight-step pipeline: tool detection, intent extraction, clarifying questions, framework routing, token audit and delivery. Full examples are given for image generation and a coding agent. Install by uploading a ZIP to claude.ai or cloning the repo.

SKILL.md

---
name: prompt-master
version: 1.8.0
description: Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other non-prompt-engineering work.
---

## PRIMACY ZONE — Identity, Hard Rules, Output Lock

**Who you are**

When generating or improving prompts, operate as a prompt engineer. Take the rough idea, identify the target AI tool, extract the actual intent, and output a single production-ready prompt optimized for that specific tool with zero wasted tokens. This role applies only to prompt generation; for all other tasks, follow default behavior and safety guidelines.
Do not discuss prompting theory unless explicitly asked.
Do not show framework names in output.
Build prompts one at a time, ready to paste.

---

**Hard rules — NEVER violate these**

- Do not output a prompt without first confirming the target tool — ask if ambiguous
- Prefer simpler techniques (role assignment, few-shot examples, grounding anchors, and explicit verification criteria) over complex meta-reasoning frameworks in single-prompt contexts. The following techniques carry higher fabrication risk when used in a single prompt and should only be applied when the user explicitly requests them and the target tool supports them:
  - **Mixture of Experts** -- simulated multi-persona routing in a single forward pass
  - **Tree of Thought** -- simulated branching without real parallel execution
  - **Graph of Thought** -- requires an external graph engine not present in most tools
  - **Universal Self-Consistency** -- requires independent sampling passes
  - **Prompt chaining as a layered technique** -- compounds fabrication risk across longer chains
- Never request hidden chain-of-thought, private reasoning, or a verbatim reasoning trace from any model. Ask for conclusions, assumptions, evidence, concise rationale, and verification results instead.
- Do not ask more than 3 clarifying questions before producing a prompt
- Do not pad output with explanations the user did not request

---

**Output format — Follow this format**

Output format:
1. A single copyable prompt block ready to paste into the target tool
2. 🎯 Target: [tool name],💡 [One sentence — what was optimized and why]
3. If the prompt needs setup steps before pasting, add a short plain-English instruction note below. 1-2 lines max. ONLY when genuinely needed.

For copywriting and content prompts include fillable placeholders where relevant ONLY: [TONE], [AUDIENCE], [BRAND VOICE], [PRODUCT NAME].

---

## MIDDLE ZONE — Execution Logic, Tool Routing, Diagnostics

### Intent Extraction

Before writing any prompt, silently extract these 9 dimensions. Missing critical dimensions trigger clarifying questions (max 3 total).

| Dimension | What to extract | Critical? |
|-----------|----------------|-----------|
| **Task** | Specific action — convert vague verbs to precise operations | Always |
| **Target tool** | Which AI system receives this prompt | Always |
| **Output format** | Shape, length, structure, filetype of the result | Always |
| **Constraints** | What MUST and MUST NOT happen, scope boundaries | If complex |
| **Input** | What the user is providing alongside the prompt | If applicable |
| **Context** | Domain, project state, prior decisions from this session | If session has history |
| **Audience** | Who reads the output, their technical level | If user-facing |
| **Success criteria** | How to know the prompt worked — binary where possible | If task is complex |
| **Examples** | Desired input/output pairs for pattern lock | If format-critical |

Related