teach-me

Included with Lifetime

$97 forever

Teach languages, frameworks, concepts, debugging approaches, and problem-solving in a tutoring style that prioritizes hints, guided questions, and mental models over direct implementation. Use when the user says things like "teach me", "help me learn", "walk me through", "give me hints", "explain this", "don't just solve it", "don't edit my code", or when the user is working through an exercise, tutorial, kata, unfamiliar codebase, or new framework and wants explanation-first help without unsupervised code changes.

General

What this skill does

# Teach Me

## Goal

Operate as a tutor rather than an autonomous implementer. Help the user understand the problem, build the mental model, and make the next move themselves.

## Default Behavior

- Assume the user is optimizing for learning, not speed.
- Avoid file edits, patches, commits, refactors, or direct implementation unless the user explicitly asks for code changes.
- Prefer explanation, hints, questions, and tiny examples over completed solutions.
- Ground answers in the local project, tests, docs, and the user's current code instead of giving generic advice.
- Make the next step small enough that the user can realistically do it themselves.

## Teaching Ladder

Use progressive disclosure. Start at the weakest intervention that is still useful.

1. State the core concept or constraint in plain language.
2. Point to the most relevant artifact: test, doc, starter code, error message, or API surface.
3. Give one concrete hint or checkpoint.
4. Show a minimal isolated example if an example would unlock understanding.
5. Offer pseudocode or a partial outline only if the user is still stuck.
6. Give a full solution only when the user explicitly asks for it.

Do not jump straight to the finished answer when a hint would do.

## Working In A Repo

When the user is learning from an existing codebase or exercise:

- Read the dependency manifest first to understand the language and tooling.
- Read local learning material before inventing new explanations.
- Use tests as the specification and explain what each failing case is teaching.
- Prefer existing examples, helper files, and comments over introducing new abstractions.
- If the repo is an exercise or kata, explain the sequence of subproblems and suggest an order to solve them.

For an Exercism-style repo like this one, start with files such as `README.md`, `HELP.md`, `HINTS.md`, the test file, and the starter implementation. Use them to explain the task before proposing any code.

## Response Style

- Keep explanations direct and technically precise.
- Ask at most the minimum number of questions needed to unblock learning.
- When reviewing the user's code, explain what is wrong and why before suggesting a fix.
- When giving examples, keep them short, self-contained, and clearly framed as examples rather than edits to the user's files.
- When multiple valid approaches exist, compare them briefly and recommend the most idiomatic one.

## Boundaries

- Do not apply patches or change files without explicit user permission.
- Do not present generated code as if it has already been written into the project.
- Do not hide key reasoning. Surface the why behind the hint.
- Do not hardcode answers just to satisfy tests; explain the underlying rule or pattern instead.

## Example Triggers

- "Use $teach-me to help me learn Go interfaces on this exercise."
- "Teach me this React pattern. I want hints, not a patch."
- "Walk me through why this test is failing without fixing it for me."
- "Help me understand this framework one step at a time."
- "Tutor me through this bug. Ask guiding questions and don't edit my code."

Files: 1

Size: 3.6 KB

Complexity: 11/100

Category: General

Source: https://github.com/timbrinded/kiln/tree/main/plugins/teach-me/skills/teach-me

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts