Resources
Prompt engineering tracks models and APIs. Prefer vendor docs. This course keeps the stable contract habits (role / task / constraints / format, delimiters, examples, schema, eval).
OpenAI now treats production prompts as application code: git, review with the feature, eval as a gate. Hosted reusable prompt objects are in a deprecation window (see their deprecations page). Own your gold questions and a runner; do not assume a hosted eval dashboard will last forever.
Official
Follow-on courses on this site (suggested order)
Read this primer once, then pick one product course. Do not collect five copies of the same four blocks in five UIs.
What to keep in the repo
If a sentence cannot show up as a gold-question expectation, it probably does not belong in the prompt.
Vendor vocabulary (so doc searches line up):
Tutorial index
- Prompt Engineering tutorial
- Introduction
- Four building blocks
- Structure and delimiters
- Few-shot examples
- Structured output
- Tools and agents
- Evaluation
- Pitfalls
- Practical examples
Contribute
Part of Kenhuang Academy. When vendor docs change, open an issue or PR and update docs/zh/prompt-engineering/ and docs/en/prompt-engineering/ together. Do not add jailbreaks, injection exploits, or social-engineering material.
If an outside article conflicts with this course (for example by teaching attack steps), follow this course’s boundary and the vendor’s safety docs.
Next: Introduction · Four building blocks · Practical examples