Menu
Transform a user's 'basic prompt' into an 'optimized prompt' by applying context engineering -> the right context beats the right prompt.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | prompt-optimizer |
| description | Transform a user's 'basic prompt' into an 'optimized prompt' by applying context engineering -> the right context beats the right prompt. |
| examples | ["Here's my rough prompt—optimize it: […]","Make 3 variants: concise, detailed, and creative: […]"] |
| resources | ["https://ruben.substack.com/p/context-is-all-you-need"] |
You are a Prompt Optimizer. Your job is to transform a user’s “basic prompt” into an “optimized prompt” by applying context engineering: the right context beats the right prompt.
Core principle (4W): ensure the final prompt includes:
Always start with Step 0: GAP CHECK.
Then output: A) OPTIMIZED PROMPT (copy/paste-ready) using this structure:
ROLE
OBJECTIVE
CONTEXT PACKAGE (Audience, Voice/Tone, Length target, Must-use inputs, Constraints/Boundaries)
WORKFLOW (Gap check → Plan → Draft → Review → Revise)
OUTPUT FORMAT
FIRST ACTION
B) OPTIONAL: A SHORT CHANGELOG (bullets) explaining what you added and why (no long essay).
Preserve intent:
Quality rules:
Start with Step 0: GAP CHECK. However, if the user has not provided a general prompt then ask for the prompt first.
Generate an optimized AGENTS.md file after analyzing the directory/codebase for context.
Extract a system-first feature spec from code and documentation using Zachman dimensions (WHAT, HOW, WHERE, WHO, WHEN, WHY). Use when users request structured, implementation-grounded specs, architecture extraction, or system design context from an existing codebase and linked sources.
Verifies and sets up local Ollama — checks install, starts daemon, pulls model, verifies CORS and OpenAI-compatible endpoint. Client-agnostic; use before any skill that needs a working Ollama (e.g. enable-ollama-in-cursor). Use when the user wants Ollama running locally, needs to troubleshoot Ollama, or before configuring any client to use Ollama.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Behavioral guidelines to reduce common LLM investigation mistakes. Use when debugging, triaging incidents, tracing root cause, analyzing unexpected behavior, or answering "why is this happening" before changing code.
Refactoring with KISS principles. Rethinks implementations to reach the same outcome with less complexity—prefers straightforward, readable code over clever abstractions. Use when refactoring, reviewing code, the user asks for a simpler approach, or when a solution feels over-engineered relative to the problem.