agentleFS
aroyburman-codesaroyburman-codes/compound-product-management/skills/prompt-coach/SKILL.md

prompt-coach

Skill1 starsChanged 9 months agoMITView on GitHub

Use when the user's prompt is vague, overloaded, or missing context that would improve the output. Also use retroactively at session breakpoints to surface prompting patterns the user can improve. Coaches without being annoying.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. selmakcby/promptlint★ 4same name
    2. shadownrx/skills★ 4same name
    3. goingli0324/prompt-coach★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a prompt triggers coaching:

    line 32
  2. Distinctive:

    Research first, ask second: Check the codebase, conversation history, and memory files before formulating questions.

    line 34
  3. Distinctive:

    Ask 1-3 targeted questions: Never more than 3. Use the AskUserQuestion tool when available.

    line 36
  4. Distinctive:

    Show the rewrite: After getting answers, show the improved prompt alongside the original.

    line 38
  5. Very specific:

    Bypass must exist: If the user prefixes with !

    line 88
  6. Distinctive:

    Use these to evaluate (internally, not shown to user unless asked):

    line 94

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Prompt Coach

Coach the user toward better prompts. Intervene only when it matters. Show, don't lecture.

When to Nudge

Fire coaching only when one of these conditions is true:

  1. Missing goal — the prompt says what but not why or what success looks like
  2. No constraints — no mention of language, framework, style, or boundaries
  3. Overloaded request — multiple unrelated tasks bundled into one prompt
  4. Dump-and-hope — code or content pasted with no explicit question
  5. Repeated failure — the same type of request has failed or needed correction 2+ times this session
  6. Undefined success — "make this better" or "fix this" with no measurable target

When to Stay Silent

  • Conversation history already fills in the ambiguity
  • The user gave a clear, specific instruction
  • Slash commands and memorization prompts (clear intent)
  • The user has bypassed coaching before on similar prompts

How to Coach

In-Session (Real-Time)

When a prompt triggers coaching:

  1. Research first, ask second. Check the codebase, conversation history, and memory files before formulating questions. Questions grounded in context ("Are you targeting the UserProfile component or the API layer?") beat generic ones ("Can you be more specific?").
  2. Ask 1-3 targeted questions. Never more than 3. Use the AskUserQuestion tool when available. Frame as quick clarifications, not interrogations.
  3. Show the rewrite. After getting answers, show the improved prompt alongside the original. Concrete demonstration transfers faster than abstract guidance.

Example:

Your prompt: "Fix the login bug"

Improved: "Fix the login bug where users get a 401 after OAuth redirect.
The issue is in auth/callback.ts — the session token isn't persisted
before the redirect completes. Expected: user lands on /dashboard
after Google OAuth. Actual: user sees 'Unauthorized' and loops back
to /login."

Retrospective (Session Review)

At session breakpoints, scan the conversation for prompting patterns:

Patterns to detect:

PatternSignalCoaching
Serial refinementUser needed 3+ follow-ups to get the right output"Try frontloading constraints: language, framework, file scope, success criteria"
Context dripUser provided critical context only after the first attempt failed"Include the 'why' upfront — it changes the approach"
Scope creepStarted with one task, gradually expanded to five"Split compound requests into individual prompts"
Missing examplesUser described output format in words when an example would be faster"Paste an example of what good output looks like"
Repeated correctionsSame type of correction across multiple promptsSurface the pattern, suggest adding it to CLAUDE.md

Retrospective output format:

## Prompt Patterns — [date]

This session had 12 prompts. 3 patterns worth noting:

1. **Serial refinement on API design** (prompts 3-6)
   You refined 4 times before landing on the right interface.
   Next time, try: "Design a REST endpoint for X. Must support
   pagination, return JSON, follow existing patterns in routes/."

2. **Missing test criteria** (prompts 8, 11)
   Both test-related prompts needed follow-up on what to assert.
   Next time, include: expected inputs, expected outputs, edge cases.

Prompts 1-2, 7, 9-10, 12 were clear and specific. No notes.

Coaching Principles

  1. Most prompts pass through unchanged. Coaching on every prompt trains the user to ignore you.
  2. Research before asking. Generic questions ("What do you mean?") are lazy. Grounded questions ("Do you want this in the existing UserService or a new module?") are useful.
  3. Show the improved version. A before/after comparison teaches more than explaining what's wrong.
  4. Cap questions at 3. More than 3 questions means you don't understand the user's context well enough.
  5. Bypass must exist. If the user prefixes with ! or says "just do it," skip coaching entirely. Respect the override.
  6. Surface patterns, not individual mistakes. One vague prompt is fine. Three vague prompts in the same category is a pattern worth naming.
  7. Praise specificity when you see it. Reinforce good prompts briefly: "Clear prompt — working on it." One line, not a speech.

Prompt Quality Dimensions

Use these to evaluate (internally, not shown to user unless asked):

DimensionWhat It Measures
ClarityCan the prompt mean only one thing?
SpecificityAre files, functions, or components named?
ContextIs the environment, framework, or codebase referenced?
Success criteriaIs the expected outcome defined?
ScopeIs this one task, not five?

Score each 1-5 internally. Below 2.5 average = nudge. Above 3.5 = pass through silently.

What Good Prompts Look Like

Provide these as examples when coaching:

Weak: "Add authentication" Strong: "Add JWT authentication to the Express API. Use the existing User model in models/user.ts. Protect all /api/v2/ routes. Store refresh tokens in Redis (already configured in lib/redis.ts). Return 401 with { error: 'unauthorized' } for invalid tokens."

Weak: "Make the tests pass" Strong: "Fix the failing test in tests/checkout.test.ts:47. The CartTotal calculation returns 99.99 but expects 100.00. Likely a floating-point rounding issue in calculateTotal() at lib/cart.ts:23."

Weak: "Refactor this" Strong: "Extract the email-sending logic from OrderController.create() into a separate EmailService class. Keep the same interface. Add error handling so a failed email doesn't roll back the order. Write a unit test for the new service."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.