You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/instructions/lesson-writing.instructions.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,8 @@ Each lesson is an object in the lesson plan array with these fields:
51
51
### Instructions
52
52
- State exactly what the user must do, in one or two sentences.
53
53
- Use imperative language: "Parse the path…", "Write a query that…", "Return null if…".
54
-
- Name the required library action in the task (method/class/option/exception behavior) so the objective is implementation-focused rather than concept-only.
54
+
- Name the required library action at the capability level (method family/class/option/exception behavior) so the objective is implementation-focused rather than concept-only.
55
+
- Do not reveal the full implementation path in the task text. Avoid naming the exact operator or single method call when that would make the solution trivial.
55
56
- Do not explain how — that belongs in the background.
56
57
- Do not refer to the testing framework or expected test mechanics in user-facing task text.
0 commit comments