Partial makes properties optional, Required makes them required, Readonly makes them immutable, Record maps keys to a type, Pick/Omit select or exclude fields.
Advanced answer
Deep dive
Expanding on the short answer — what usually matters in practice:
Context (tags): utility-types, types
Explain the "why", not just the "what" (intuition + consequences).
Trade-offs: what you gain/lose (time, memory, complexity, risk).
Edge cases: empty inputs, large inputs, invalid inputs, concurrency.
Examples
A tiny example (an explanation template):
// Example: discuss trade-offs for "name-common-utility-types-and-what-they-do."
function explain() {
// Start from the core idea:
// Partial makes properties optional, Required makes them required, Readonly makes them immut
}
Common pitfalls
Too generic: no concrete trade-offs or examples.
Mixing average-case and worst-case (e.g., complexity).