-
Notifications
You must be signed in to change notification settings - Fork 0
feat: keep teaching progress out of workspace files #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
thedamod
wants to merge
3
commits into
main
Choose a base branch
from
feat/private-teaching-workspace
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
16 changes: 16 additions & 0 deletions
16
packages/ai/skills/sections/agent-guidelines/create-learning-path.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| --- | ||
| name: create-learning-path | ||
| description: Build a personalized learning roadmap with milestones and practice checkpoints. | ||
| --- | ||
|
|
||
| # Create a learning path | ||
|
|
||
| Read the private teaching workspace with `get_teaching_workspace` first. Save the resulting roadmap as a `reference` or `lesson` artifact, not as a visible workspace file. | ||
|
|
||
| 1. Assess the learner's baseline and target outcome. | ||
| 2. Sequence the smallest set of topics from fundamentals to applied practice. | ||
| 3. Define achievable milestones, practice tasks, feedback criteria, and time-boxed checkpoints. | ||
| 4. Include reflection in every phase and limit the resource list. | ||
| 5. End with a measurable next milestone. | ||
|
|
||
| Completion means the roadmap names the target, order, practice, feedback, timing, and next checkpoint. |
16 changes: 16 additions & 0 deletions
16
packages/ai/skills/sections/agent-guidelines/run-learning-retrospective.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| --- | ||
| name: run-learning-retrospective | ||
| description: Review learning progress, find blockers, and adjust the next milestone. | ||
| --- | ||
|
|
||
| # Run a learning retrospective | ||
|
|
||
| Read the private teaching workspace with `get_teaching_workspace` first. Save the retrospective as a `learning-record` artifact, not as a visible workspace file. | ||
|
|
||
| 1. Compare completed work with the target outcomes. | ||
| 2. Identify recurring blockers and weak concepts from evidence, not impressions. | ||
| 3. Decide what to reinforce, what to defer, and why. | ||
| 4. Adjust pacing and practice tasks. | ||
| 5. Set one next milestone with a measurable checkpoint. | ||
|
|
||
| Completion means the retrospective records progress, blockers, changes, and the next checkpoint. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| --- | ||
| name: teach | ||
| description: Teach a user a skill or concept across sessions with short lessons and practice. Use when the user asks to learn. | ||
| --- | ||
|
|
||
| # Teach | ||
|
|
||
| Use the private teaching workspace. Do not store teaching state in visible workspace files. | ||
|
|
||
| ## Before teaching | ||
|
|
||
| 1. Call `get_teaching_workspace` before teaching. Read the mission, learning records, notes, references, and resources it returns. | ||
| 2. If the mission is missing or unclear, ask why the learner wants this and what outcome they need. Do not invent a mission. | ||
| 3. Use trusted sources for factual content. Save sources as `resource` artifacts. | ||
|
|
||
| ## Lesson loop | ||
|
|
||
| 1. Teach only the knowledge needed for one narrowly scoped skill. | ||
| 2. Make the learner retrieve, apply, and receive feedback. Prefer a short interactive exercise. | ||
| 3. Save the lesson as a `lesson` artifact with a stable slug and complete HTML content. | ||
| 4. Save durable facts as `reference` artifacts and non-obvious progress as `learning-record` artifacts. | ||
| 5. Save mission changes only after the learner confirms them. Use the `mission` artifact for the current mission. | ||
| 6. End with a concrete next step and a way to ask follow-up questions. | ||
|
|
||
| Keep lessons short enough to finish quickly. Favor storage strength over a smooth explanation: recall, spacing, and interleaving matter more than immediate fluency. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| --- | ||
| name: unslop | ||
| description: Rewrite plans and documentation in direct, specific language. Use when removing generic AI prose. | ||
| --- | ||
|
|
||
| # Unslop | ||
|
|
||
| Rewrite text so it sounds specific, direct, and human. Preserve meaning and the intended tone. | ||
|
|
||
| ## Process | ||
|
|
||
| 1. Scan for puffery, vague claims, filler, repetition, over-structured prose, and generic conclusions. | ||
| 2. Replace each with a concrete fact, instruction, decision, example, or number. | ||
| 3. Prefer active voice, plain words, varied sentence length, and sentence-case headings. | ||
| 4. Keep the author's point of view when it helps. Do not add enthusiasm or marketing language. | ||
| 5. Read the result once as a skeptical editor. Remove anything that could appear unchanged in another project's docs. | ||
|
|
||
| ## Remove | ||
|
|
||
| - Puffery and promotion: "pivotal", "groundbreaking", "vibrant", "stunning", "must-visit", "testament". | ||
| - Vague attribution: name the source or remove the claim. | ||
| - Abstract metaphor jargon: "landscape", "flywheel", "north star", "bedrock", "scaffolding", "harness". | ||
| - Fancy verbs: use "is", "has", "use", and "help" instead of "serves as", "boasts", "leverage", and "facilitate". | ||
| - "Not just X, but Y", forced groups of three, synonym cycling, and false "from X to Y" ranges. | ||
| - Filler such as "in order to", "it is important to note", and excessive hedging. | ||
| - Chatbot phrases, sycophancy, decorative emojis, curly quotes, and em dashes. | ||
|
|
||
| ## Keep | ||
|
|
||
| - One idea per sentence when a sentence becomes hard to parse. | ||
| - A single source of truth for each rule. | ||
| - Steps in execution order. End each step with a checkable completion condition. | ||
| - Reference material behind a clear pointer when only one branch needs it. |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.