Naming Conventions

This document covers naming inside generated content: course module titles, topic titles, and section titles.

Repository artifact naming, prompt file naming, and other repository-facing conventions live in agents.md and are intentionally excluded from this document.

Course content naming

These rules are enforced at the outline design stage via the naming_instructions injection.

General rules

Use clear, simple language. No jargon, buzzwords, or overly long titles.
Consistent tone: professional, educational, encouraging.
Sentence case throughout: capitalize only the first word, proper nouns, and abbreviations.
Titles must connect to the course title and reflect its main idea.
When a title mentions a framework, model, method, standard, doctrine, or named concept, use only its official widely accepted name.
Do not invent pseudo-frameworks, relabeled known concepts, branded course-specific labels, or obscure references presented as established models.
If no official established name exists, describe the idea in plain language instead of turning it into a named framework or concept.
Never use the word "journey".
Do not use titles in the form "[name]'s aha moment" — rephrase to something equivalent.

By level

Level	Length	Form	Notes
Module	2–4 words	Noun phrase	Express the main theme or skill area (e.g., Recognizing strengths, Smart AI workflows)
Topic	max 6–8 words	Action-oriented where possible	Natural step in the learning path; avoid "Module X summary" — reflect the theme instead
Section	—	Statement or question, whichever is more natural	Must differ from the section type name; no numbers, no underscores; avoid "Module X challenge"; may use a question mark when that fits the section's real intent

Section-title guidance

A section title should always be derived from the meaning of the section as defined in its blueprint.
The blueprint is the source of truth for section intent. The source title wording is not.
If a compact title already expresses the section clearly and naturally, keep that framing. Do not rewrite it just to make it more explicit, conversational, or learner-directed.
If the title is already in the target language, sounds natural, reflects the essence of the section, does not violate the section-title anti-patterns, and follows target-language grammar, leave it unchanged.
If a literal phrasing sounds awkward, rewrite it into the clearest natural title that still matches the section scope.
Question-form section titles are allowed when that is the most natural way to express the section's idea.
Do not force question form when a neutral diagnostic or explanatory title already works well.
Do not change learner expectation, rhetorical stance, or assessment intent when rewriting.
Do not address the learner directly in the title unless that mode is clearly supported by both the section blueprint and the section type.
During localization, use the section blueprint to recover meaning when a direct translation would sound stiff or misleading.

Section-title anti-patterns

Titles that include module, topic, or section numbers.
Titles that repeat the section type name instead of describing the content.
Literal translations that sound translated rather than native.
Mechanical copies of source-language title shapes when the target language needs a different structure.
Titles that follow the old source wording even when the blueprint clearly supports a better learner-facing title.
Titles that add direct learner address or a more self-reflective framing without support from the section blueprint.