菜单
Compact a lesson by folding answered ?> Q&A pairs into <details> blocks, so a re-read flows past them. Run after the user has worked through a lesson.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Answer an inline question marker (?> or ?>>) in a lesson file. Locates the Nth marker of the given kind and writes the answer in-place. Use when /api/ask routes a user question.
Review the user's solution for one studyground exercise. Reads exercises/<name>/main.py, gives feedback, writes it to exercises/<name>/feedback.md and to a feedback block in the calling lesson.
Have a real first conversation with a new learner — open-ended, learner-led, not a survey. Let them tell you what they're after; follow up where it actually matters; when you have enough to draft something useful, offer to write the curriculum. Then on action=finalize, write tracks/<track>/curriculum.md.
Generate the next lesson in the current track. Reads progress.json, writes a new lesson file, updates progress. Use when the user is ready to advance.
A persistent tutor / coordinator that the learner talks to ABOUT a course (not inside a single lesson). Knows the curriculum, what's done, what's pending, the materials, and recent btw threads. Discusses plan, pace, gaps, suggestions — does not write to lesson files itself; recommends actions the user can take with other skills.
Start a new learning track on a topic. Generates the first lesson under $STUDYGROUND_DIR/lessons/ and updates progress.json. Use when the user says "let's learn X" or invokes /studyground:learn.
| name | recap |
| description | Compact a lesson by folding answered ?> Q&A pairs into <details> blocks, so a re-read flows past them. Run after the user has worked through a lesson. |
Fold the consumed Q&A in a lesson into collapsed <details> blocks. Leave the
main narrative intact.
Read lessons/<slug>.md.
For each pair of ?> question followed by <!-- answer:start --> ... <!-- answer:end -->, replace both the question line AND the answer block with:
<details>
<summary>?> {question text}</summary>
{original answer body, verbatim}
</details>
Leave ?>> btw markers (they're already folded), :::exercise blocks,
and <!-- feedback:start --> ... <!-- feedback:end --> blocks untouched.
Do not touch <!-- answer:pending --> markers (those haven't been asked
yet — keep them visible so the user knows there's a question pending).
Save the file.
After 4–5 ?> markers in one lesson have been asked and answered inline, the
file gets long and the main narrative is harder to skim on a second read. Folding
collapses the Q&A behind a single line, but keeps it one click away.
Note: in the reader, an answered ?> is open by default (so the learner
sees the answer they earned). Recap is the explicit "I've already absorbed
this, now hide it on re-read" action — it overrides the default by rewriting
the source into a raw <details> block.