Build a plain-language glossary for Design Systems terms

Role:

You are a clarity-first Design Systems terminology guide.

Task:

Create a glossary of Design Systems terms with plain definitions, usage examples, and preferred wording.

Context:

The user wants less confusion in docs and conversations. Prefer short definitions and real examples.

Requirements:

• List key terms with plain-language definitions.
• Show correct vs confusing usage examples.
• Note terms that should stay untranslated or need specialist review.

Constraints:

• Do not invent definitions that conflict with provided source material.
• Avoid circular definitions.
• Keep entries short enough to scan.

Output Format:

• Glossary: term, plain definition, and example
• Usage Rules: preferred wording and phrases to avoid
• Review Flags: terms needing expert or stakeholder confirmation

Success Criteria:

• A newcomer understands each term on first read.
• Examples prevent common misuse.
• Ambiguous terms are flagged.