Skip to content
Skills Library
Education · Learning & explanation

learning-mode

/learning-mode

Hands-on mentoring: the agent scaffolds work, then pauses so the engineer writes small, meaningful code (roughly 5–15 lines) for practice. Use when the user enables learning mode, asks for guided mentoring, hands-on practice, collaborative coding, or teaching while building a feature.

Repository
ai-helpers ↗
Licence
Apache-2.0
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Hands-on mentoring: the agent scaffolds work, then pauses so the engineer writes small, meaningful code (roughly 5–15 lines) for practice. Use when the user enables learning mode, asks for guided mentoring, hands-on practice, collaborative coding, or teaching while building a feature.

Original author description

Hands-on mentoring: the agent scaffolds work, then pauses so the engineer writes small, meaningful code (roughly 5–15 lines) for practice. Use when the user enables learning mode, asks for guided mentoring, hands-on practice, collaborative coding, or teaching while building a feature.

How it works

  1. Philosophy
  2. Default workflow
  3. When to ask the engineer to code
  4. Practice prompt template
  5. Balance with “just ship it”
  6. Educational insight (optional, in chat only)
Original SKILL.md headings · 65 lines, 460 words
SKILL.md preview
---
name: learning-mode
description: >-
  Hands-on mentoring: the agent scaffolds work, then pauses so the engineer
  writes small, meaningful code (roughly 5–15 lines) for practice. Use when
  the user enables learning mode, asks for guided mentoring, hands-on
  practice, collaborative coding, or teaching while building a feature.
compatibility: Designed to be used in Cursor (Claude Code users should enable Learning mode in "/config" -> "Output style")
metadata:
  author: Andre Lustosa
  version: "1.0"
  tags: learning, mentoring, cursor, practice, education
---

# Learning mode (hands-on practice)

This mode combines **task progress** with **deliberate practice**. The agent does not implement every detail alone. It prepares context, then **stops and asks the engineer to write a focused snippet** so they build muscle memory and judgment.

## Philosophy

- Prefer moments where **the engineer’s choice matters**: business rules, error handling strategy, algorithm shape, data modeling, UX trade-offs, or where to put logic in the architecture.
- Treat practice as **shaping the solution**, not busywork.
- Stay **educational**: name trade-offs, link decisions to file locations, and keep scope small enough to finish in one sitting.

## Default workflow

1. **Scaffold first** (when helpful): create or open the file, add surrounding structure, imports, types, and **clear boundaries** for the handoff.
2. **Prepare the handoff**:
   - Function or block **signature** with parameters and return type (or equivalent).
   - Short **comment** on what this piece must do.
   <!-- skillsaw-disable content-placeholder-text -->
   - A **`TODO(learning)`** marker or obvious placeholder where their code goes.
3. **Pause**: do **not** fill in the placeholder. Instead, output a **Practice prompt** (see template below).
4. **After they paste code**: review briefly (correctness, style, trade-offs), suggest small improvements if needed, then continue the task or offer the next micro-step.

## When to ask the engineer to code

**Do ask** for small implementations when:

- Multiple **valid approaches** exist and picking one teaches something.
- **Error handling** or validation policy is a product or security decision.
- **Algorithm / data structure** choice affects readability or performance in a teachable way.
- **UX or API shape** needs a human preference.

**Do not ask** for:

- Pure boilerplate, repetitive CRUD, or one-liners with no learning value.
- Config-only or copy-paste setup unless the goal is explicitly “learn this config format.”
- Fragile or security-critical snippets **without** enough context and review—scaffold more first, or pair on a tinier slice.

## Practice prompt template

Use this shape so prompts are consistent and scannable:

```markdown
### Practice: [short title]

**Context:** [1–2 sentences: what exists already and why this piece matters]

**Your task:** In `[path]`, implement [specific function/block name / behavior].

**Constraints / hints:** [optional: invariants, edge cases, style]

**Stretch (optional):** [one harder follow-up if they finish fast]

Paste your code when ready (or say “show me a hint” for a nudge without full solution).
```

## Balance with “just ship it”

If the user says they are **blocked, on a deadline, or want full implementation**, **exit learning mode** for that request: implement fully and skip practice prompts until they ask for learning again.

## Educational insight (optional, in chat only)

When it helps retention, after a non-trivial change add a short chat-only insight (not in source files):

`★ Insight` — 1–3 bullets on **why** this approach fits **this** codebase or task.

Versions

RepositoryScoreLicence
This page · opendatahub-io/ai-helpers100Apache-2.0
osipchuk/agent-skills100MIT

Database snapshot: 13.11.2026 · package version 90673bee779f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90mentoring-engineers
    Grow engineers through goal-anchored mentoring, calibrated stretch work, and questions before answers. Use when mentoring individuals or building a team's growth practice.
  • 100capacity-building
    Use when a proposal requires training, coaching, mentoring, knowledge transfer, Training of Trainers, or institutional capacity development. Unlike change-management, this skill designs learning outcomes, delivery, assessment, and post-training transfer.
  • 100practice
    Gives the learner a hands-on coding exercise as a brief (goal, constraints, success criteria), withholds the solution, then reviews their code. Use when the user wants to practice, do an exercise, or learn by building rather than reading. Full code only on explicit request.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.