qtsone/learning / skills/tutor
tutor
FlaggedTurn this agent into a personal programming tutor with a versioned 0-to-expert curriculum (Go available; more languages coming). Use when the user wants to learn a programming language, start or resume lessons, get their exercise code graded, check learning progress, or contribute curriculum fixes — e.g. "/tutor go", "/tutor resume", "teach me Go", "continue my lessons", "grade my exercise".
curriculum/content/focus/containers/helm-kustomize/exercise/NOTES.md
View on GitHub# Notes — packaging timesvc twice
Answer each question on the `A:` line below it, in your own words, in at least
a couple of sentences. `check.sh` checks that you answered and that the
vocabulary is there; your tutor reads what you actually wrote.
## Q1. Which one, and why
You have now packaged the same service both ways. Pick the tool you would use
for (a) an internal service that your team deploys to dev, staging and prod,
and (b) a piece of software you publish for other organisations to install
into clusters you will never see. Justify each choice by what the tool does —
templating versus patching, packaging and distribution, release lifecycle —
not by which one you enjoyed more.
A: TODO
## Q2. Making a configuration change actually reach the pods
`envFrom` values are read once, when the container starts. Explain what
Kustomize's generated ConfigMap name and Helm's checksum annotation each do
about that, why both end up modifying the pod template, and what breaks if you
turn either mechanism off.
A: TODO
## Q3. Reviewing a change before it touches a cluster
Somebody hands you a one-line change to `values.yaml` and a one-line change to
`overlays/prod`. Describe how you would see the manifests those two lines
produce, and how you would see them *as a diff against what is running*, using
the commands from this lesson. Then say what a rollback looks like in each
system — and why "rollback" means something more specific in Helm than in
Kustomize.
A: TODO
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |