Prompt Engineering Guide: A Structured Reference for LLM Prompting, RAG, and Agents
GitHub describes it as 🐙 Guides, papers, lessons, notebooks and resources for prompt engineering, context engineering, RAG, and AI Agents.. The repository metadata lists MDX as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- The Prompt Engineering Guide from DAIR.AI is a MIT-licensed collection of tutorials, papers, and notebooks covering prompt engineering, context engineering, RAG, and AI agents. It is a reference and learning resource, not a software tool, and its value depends on how current its content remains.
- Who is it for?
- Adopt the Prompt Engineering Guide if you are a developer, researcher, or student looking for a structured, free introduction to prompt engineering, RAG, and AI agents, and you prefer a web-based reference over a single vendor's documentation. Do not use it as your only source if you need hands-on training, because the repository itself is mostly links and articles, not runnable code.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 8 months ago.
- What is it written in?
- Mainly MDX, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- dair-ai/Prompt-Engineering-Guide80,037 ★ · +2,580
| Repository | 2026-08-13 | 2026-11-13 |
|---|---|---|
| dair-ai/Prompt-Engineering-Guide | 77.5k | 80k |
2,580 Stars in the last 92 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What the Guide Actually Is
The guide targets two audiences. Researchers use prompt engineering to improve LLM performance on tasks like question answering and arithmetic reasoning. Developers use it to design prompts that interface with LLMs and other tools. The guide is also positioned as a learning path, with links to lectures and a Discord community. If you are looking for a library to install, this is not it. If you want a structured overview of prompting techniques, it fits that role.
The Content Structure: From Basics to Advanced Techniques
The repository organizes content into several sections. Introduction covers LLM settings, basics of prompting, prompt elements, and general tips. Techniques lists 16 distinct methods: zero-shot, few-shot, chain-of-thought, self-consistency, generate knowledge, prompt chaining, tree of thoughts, RAG, ART, APE, active-prompt, directional stimulus, PAL, ReAct, multimodal CoT, and graph prompting. Applications covers function calling, data generation, synthetic RAG datasets, code generation, and a case study on graduate job classification. Prompt Hub provides categorized prompt examples, from classification to adversarial prompting. Models section includes model-specific guides, starting with ChatGPT. This is a broad taxonomy, and it is useful because it names techniques you might otherwise encounter as scattered blog posts.
How to Use the Guide: Commands and Configuration
Reading the guide needs no commands, config keys or installs. The repository is a Next.js/Nextra site (package.json defines dev, build and start scripts and lists dependencies) built from MDX files. To use it, you visit promptingguide.ai or clone the repository and read the MDX files. The README points to the web version as the most up-to-date source. If you want to contribute translations, the README notes that the guide supports 13 languages; the README says it welcomes more translations. The README links to the Discord, Twitter, YouTube channel and newsletter, and gives the promo code PROMPTING20 for 20% off the paid courses. This is a reading resource, not a tool, so the 'getting started' step is simply opening a browser.
The Strengths: Coverage and Accessibility
The guide's main strength is its breadth. It covers techniques that span from simple zero-shot prompting to advanced methods like tree of thoughts and graph prompting. It also includes RAG and AI agents, which are current topics. The web version is free, and the repository is MIT-licensed, so you can reuse the content in your own materials with attribution. The guide is also multilingual, which lowers the barrier for non-English speakers. The inclusion of notebooks and papers as resources gives you a path to deeper study. For someone new to the field, the guide provides a map of the terrain. It tells you what techniques exist, and the links lead to the matching pages on promptingguide.ai. That is genuinely useful, because finding the right paper on your own is time-consuming.
Limitations: Staleness and Lack of Hands-On Depth
The biggest limitation is that the guide is a static snapshot. The README mentions the guide crossed 3 million learners in January 2024, but that is a marketing number, not a technical fact. The content may not reflect the latest model capabilities, especially for proprietary models that change frequently. The README does not list a 'last updated' date, so you cannot tell how current each page is. Another limitation is that the guide is not hands-on. It provides examples and explanations, but it does not give you a runnable environment or a framework to test prompts. The paid courses are meant to fill that gap, but the repository also includes a notebooks/ directory. If you need to learn by doing, you will have to set up your own LLM API calls or use other tutorials. The guide also has a commercial bias: the courses and consulting services are promoted within the README, so you should be aware that the free content is a funnel for paid offerings.
Comparison with Alternatives: Course Platforms and Model Docs
The main alternative is to learn prompt engineering from the documentation of a specific model provider, like OpenAI's prompt engineering guide or Anthropic's. Those docs are vendor-specific and often more detailed about that model's quirks, but they do not cover the breadth of techniques that this guide does. Another alternative is a structured course on platforms like Coursera or DeepLearning.AI, which offer hands-on labs and quizzes. Those courses are more interactive but usually cost money. The Prompt Engineering Guide sits in between: it is free and broad, but it lacks the interactivity of a course and the model-specific depth of vendor docs. For a researcher who wants to survey techniques across models, the guide is better than vendor docs. For a developer who needs to optimize prompts for a single model, vendor docs are more practical. The guide also includes RAG and agents, which many vendor docs treat separately, so it is a more unified reference for those topics.
Maintenance and Licensing: What You Need to Know
The repository is MIT-licensed, which means you can use, copy, modify, and distribute the content with attribution. That is a permissive license, and it is a real advantage for educators who want to build on the material. However, the repository has no GitHub releases, and the last push was on 2026-03-11. The README announces courses and services, which suggests the maintainers are active, but the guide's content may not be updated on a regular schedule. The web version is described as 'most up-to-date,' but there is no versioning or changelog. If you use the guide as a reference, you should check the specific page for its own update date, if any. The maintenance cost is low for you as a reader, but the risk is that techniques become outdated. For example, a technique that was state-of-the-art in 2023 may be less relevant in 2025. The guide's value depends on the maintainers' willingness to keep it current.
Editorial conclusion
Adopt the Prompt Engineering Guide if you are a developer, researcher, or student looking for a structured, free introduction to prompt engineering, RAG, and AI agents, and you prefer a web-based reference over a single vendor's documentation. Do not use it as your only source if you need hands-on training, because the repository itself is mostly links and articles, not runnable code. Before relying on it, verify the publication date of each section you plan to cite, since the field moves quickly and the guide may lag behind the latest model capabilities. The guide is best used as a starting point, not a definitive reference.
Frequently asked questions
What are the 5 principles of prompt engineering?
The README index does not present a five-item principle list. Its introductory advice is split across separate pages named Basics of Prompting, Prompt Elements and General Tips for Designing Prompts, so there is no single page here that presents five principles under that heading.
How should I learn prompt engineering?
Start with the web version at promptingguide.ai, which is where the README sends readers for the current material. The introduction track runs LLM Settings, Basics of Prompting, Prompt Elements, General Tips for Designing Prompts and Examples of Prompts before the techniques pages begin. Paid self-paced courses sit separately at academy.dair.ai.
What are the 5 P's of effective prompting?
None of the sections in the README index is organised under that name. The closest structure is the Prompt Hub, which groups ready-made prompts by task, with sections for Classification, Coding, Creativity, Evaluation, Information Extraction, Mathematics, Question Answering, Reasoning, Text Summarization, Truthfulness and Adversarial Prompting, rather than by a set of P-named principles.
Is there a PDF version of the ChatGPT prompt guide available?
The guide is distributed as a website at promptingguide.ai, and its Models section includes a ChatGPT page at promptingguide.ai/models/chatgpt. The repository has no PDF export step: the only scripts in package.json are dev, build and start, and each one runs a Next command rather than generating a document.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/dair-ai-prompt-engineering-guide)Star history chart for your README
[](https://hysenlabs.com/projects/dair-ai-prompt-engineering-guide)Was this useful?