agentleFS
repo-phuocdtrepo-phuocdt/prompt-engineer-skill/SKILL.md

prompt-engineer

Skill17 starsChanged 10 months agoMITView on GitHub

Transform rough prompts/ideas into production-ready LLM prompts. Use when crafting, refining, or optimizing prompts for any AI model (Claude, GPT, Llama, etc.) with advanced techniques like CoT, constitutional AI, RAG optimization.

74 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use idea-validator, debugger and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dipaulavsSkill

    idea-validator

    Validates app ideas before building. Analyzes market saturation, competitors, real demand vs stated interest, solo builder feasibility (2-4 weeks timeline), and monetization potential. Use when user asks to validate an idea, evaluate a concept, check if idea is worth building, or before starting a new project.

    Also in 3 projects that use this

  • JohnJBorenSkill

    debugger

    Systematic debugging workflows, root cause analysis, and troubleshooting patterns

    Also in 3 projects that use this

  • VercelSkill

    technical-writer

    Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.

    Also in 3 projects that use this

  • JetBrainsSkill

    webapp-testing

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    Also in 4 projects that use this

  • JetBrainsSkill

    doc-coauthoring

    Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

    Also in 3 projects that use this

  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 2

    Distinctive

    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. Very specific:

    Follow model-specific guidelines from references/model-optimization.md:

    line 38
  2. Distinctive:

    Add constraints and guardrails

    line 41
  3. Distinctive:

    When/how to use effectively

    line 63

“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “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 Engineer

Expert prompt engineering skill that transforms rough ideas into well-structured, production-ready prompts optimized for LLMs.

When to Activate

  • User provides a rough prompt/idea and wants it refined
  • User asks to create/design/optimize a prompt for any LLM
  • User needs prompt architecture for agents, RAG, or multi-step workflows
  • User asks about prompting techniques or best practices

Workflow

1. Analyze Input

Identify from user's request:

  • Target model (Claude, GPT, Llama, etc.) — default: Claude
  • Use case (agent system prompt, task prompt, RAG, chat, etc.)
  • Domain (technical, creative, business, etc.)
  • Constraints (token limits, output format, safety requirements)

2. Apply Techniques

Select appropriate techniques from references/techniques.md based on use case:

  • Complex reasoning → Chain-of-Thought, Tree-of-Thoughts
  • Safety-critical → Constitutional AI patterns
  • Data extraction → Structured output, JSON mode
  • Multi-step tasks → Prompt chaining, agent patterns
  • Knowledge-heavy → RAG optimization

3. Craft the Prompt

Follow model-specific guidelines from references/model-optimization.md:

  • Structure with clear sections (role, context, instructions, output format)
  • Include examples where beneficial (few-shot)
  • Add constraints and guardrails
  • Optimize for token efficiency

4. Deliver Output

MANDATORY format — always include ALL sections:

The Prompt

Display complete prompt in a single copyable code block.

Implementation Notes

  • Techniques used and rationale
  • Model-specific optimizations
  • Parameter recommendations (temperature, max_tokens)
  • Expected behavior and output format

Testing & Evaluation

  • 3-5 test cases to validate
  • Edge cases and failure modes
  • Optimization suggestions

Usage Guidelines

  • When/how to use effectively
  • Customization options
  • Integration considerations

Key Principles

  • Always show the complete prompt — never just describe it
  • Token efficiency — concise but comprehensive
  • Production-ready — reliable, safe, optimized
  • Model-aware — tailor to target model's strengths
  • Refer to references/techniques.md for advanced technique details
  • Refer to references/model-specific-optimization-guide.md for model-specific guidance
  • Refer to references/production-patterns-and-enterprise-templates.md for enterprise patterns

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.