laabidi-ahmed-ai Concept Explainer
Activation rule (read first)
Only run this skill when the user explicitly invokes it by name. Valid triggers:
concept explainer: <topic>use concept explainer for <topic>/concept-explainer <topic>- any equivalent phrasing where the user clearly names "concept explainer".
If the user just asks a related question in normal conversation ("what is gradient clipping?", "explain batch norm") without naming this skill, do not activate. Answer normally instead. Never fire automatically on topic match alone.
The <topic> is whatever the user put after the invocation. If no topic was given, ask for one in a single short line, then proceed once provided.
Audience calibration
The reader is an MLOps engineering student: comfortable with software basics, ML/DL, FastAPI/Django, and Python. They know the fundamentals of ML/DL but are still learning Docker, Kubernetes, and CI/CD — cover those at a conceptual / interview level when they come up, without assuming hands-on experience. Write mid-course: not for a total beginner, not for an expert. Practical and student-level, never academic-paper dense.
Output structure (produce ALL sections, in this exact order)
1. Simple explanation
Plain language, built around an analogy or everyday comparison. Explain it as if to someone partway through the course — enough grounding to build intuition, no hand-waving.
2. Technical explanation
The formal, rigorous version: correct terminology, the underlying math or algorithm where relevant, and how it actually works internally. This is the depth expected in a technical interview. Use compact math notation where it clarifies; keep it readable.
3. Tiny code example
A minimal, runnable snippet (Python / PyTorch / TensorFlow / scikit-learn, whichever fits the concept best) that demonstrates the concept concretely. Keep it under ~20 lines. Add brief inline comments on the lines that matter.
4. Interview angle
2–3 interview questions on this exact concept, each with a concise model answer (a few sentences, not an essay). Pick questions an interviewer would realistically ask.
5. Common pitfalls / gotchas
The mistakes people actually make with this concept in practice — subtle bugs, wrong defaults, misuse, misconceptions.
Optional closing section
Related concepts to know
If the concept has variants or neighbours worth knowing (e.g. gradient clipping → exploding gradients, gradient norm, clip_grad_norm_ vs clip_grad_value_), list them briefly at the very end. Skip this section if there's nothing genuinely relevant to add.
Style
Practical, direct, student-level. Headers for the five sections. Prose over bullet-dumps inside each section, except where a short list is genuinely clearer. Don't pad.