learning-mode
/learning-mode
Prowadzi mentoring praktyczny: agent przygotowuje szkielet pracy, a potem zatrzymuje się, by inżynier sam napisał krótki, istotny fragment kodu liczący mniej więcej 5 do 15 linii.
- Autor
- opendatahub-io ↗
- Repozytorium
- ai-helpers ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 22.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 1
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Prowadzi mentoring praktyczny: agent przygotowuje szkielet pracy, a potem zatrzymuje się, by inżynier sam napisał krótki, istotny fragment kodu liczący mniej więcej 5 do 15 linii.
Oryginalny opis (EN)
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.
Jak działa
- Philosophy
- Default workflow
- When to ask the engineer to code
- Practice prompt template
- Balance with “just ship it”
- Educational insight (optional, in chat only)
Podgląd SKILL.md
--- 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.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · opendatahub-io/ai-helpers | 100 | Apache-2.0 |
| osipchuk/agent-skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 90673bee779f (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90mentoring-engineers
Prowadzi mentoring inżynierów oparty na celach, dobranych zadaniach rozwojowych i pytaniach zadawanych przed udzieleniem odpowiedzi. - 100capacity-building
Projektuje komponent szkoleniowy wniosku: efekty uczenia, sposób realizacji, ocenę i transfer wiedzy po szkoleniu, w tym coaching, mentoring i Training of Trainers. - 100practice
Daje uczącemu się ćwiczenie programistyczne jako zadanie z celem i kryteriami, bez rozwiązania, a potem przegląda jego kod.