Yardımcıdan Etmene
Yapay zekanın yalnızca yanıt vermekle kalmayıp eyleme geçtiği durumlar.
Yardımcıdan Etmene, CoddyKit'te ücretsiz bir Vibe Coding dersidir. Bu, 4 dersinin 1. dersidir. Aşağıdan dersin tamamını ücretsiz okuyabilir, sonra tarayıcıda yerleşik kod editörü ve 7/24 yapay zeka koçu ile uygulamalı olarak pratik yapabilirsin. Bu, Vibe Coding öğrenme yolunun bir parçasıdır ve ilerlemeniz web ve CoddyKit uygulaması arasında senkronize olur. Vibe Coding kursu toplamda 4 dersten oluşur.
Bu dersin bazı bölümleri henüz çevrilmemiş olup İngilizce olarak gösterilmektedir.
When AI Stops Talking and Starts Doing
So far you've used AI like a chat partner: you ask, it answers, you copy the code. That's an assistant.
An agent is different. You give it a goal, and it acts on its own: it reads files, runs commands, checks results, and keeps going until the job is done. You're no longer the one pasting everything.
This lesson is about that leap: from AI that answers to AI that does the work.
Assistant vs Agent
The simplest way to feel the difference:
- Assistant: "Here's the code for a login form" — you take it from there.
- Agent: "I created
login.html, wired up the form, ran the app, and it works." — it did the steps.
Tools like Claude Code and Cursor's agent mode are agentic: they touch your real project files, not just a chat box.
The Agent Loop
Under the hood, an agent runs a simple loop: think → act → observe → repeat.
It plans a step, takes an action (edit a file, run a command), looks at what happened, then decides the next step. It keeps looping until your goal is met or it gets stuck.
Here's that loop sketched as JavaScript pseudo-code so you can picture it:
function agentLoop(goal) {
let done = false;
while (!done) {
const plan = think(goal); // decide next step
const result = act(plan); // edit file / run command
done = check(result, goal); // is the goal met?
}
return "Goal reached!";
}
console.log("An agent repeats: think, act, observe.");What a Goal Looks Like
You don't micromanage an agent. You hand it an outcome and let it figure out the steps.
Compare a single instruction to an agent goal: the goal describes the finished result, not each keystroke.
Goal for an agent (paste into Claude Code or Cursor agent mode):
"Add a dark mode toggle to my website. Create a button in the top
right, switch the page between light and dark colors when clicked,
and remember the choice when the user comes back. Test it works
before you finish."Agents Use Your Real Project
The big shift: an agent works inside your actual files. It can open index.html, find your CSS, add new code, and save — all without you copy-pasting.
That's powerful and a little scary. It means the agent can change a lot at once, so you'll learn to review what it did (and you'll cover safety in the last lesson of this course).
Agents Can Run Things
Beyond editing files, agents can run commands: start your app, install a package, or run tests. Then they read the output and react.
If a command fails, a good agent notices the error and fixes it — no need for you to copy the red text into chat. This is why agents feel like a teammate, not a tool.
Example agent goal that involves running things:
"Install the dependencies for this project, start the dev server,
open the homepage, and tell me if there are any errors in the
console. If there are, fix them and run it again."Watching an Agent Work
When you run an agent in Claude Code or Cursor, you'll see it narrate its steps: "Reading file... editing... running... done."
This is your window into its thinking. Read it! If it heads in the wrong direction, you can stop it and steer. You stay the pilot; the agent just flies the plane for the boring parts.
Approve Before It Acts
Most agent tools ask for permission before doing something risky — like deleting files or running an unknown command. They show you the action and wait for a yes.
Treat every approval as a real decision. "Allow once" for normal edits is fine; pause and read carefully before approving anything that removes or overwrites a lot.
Good Tasks for an Agent
Agents shine on tasks with many small, mechanical steps:
- Renaming something across many files
- Adding a feature that touches several places
- Fixing a bug, running the app, confirming it's gone
- Setting up a new project from scratch
For a one-line question ("what does this function do?"), a plain assistant chat is faster. Match the mode to the job.
You Set the Goal, AI Walks the Path
Here's the mindset to carry forward: you own the goal and the judgment; the agent owns the legwork.
You decide what success looks like and check the result. The agent handles the how — the dozens of little steps in between. That partnership is the heart of vibe coding at the next level.
Try this framing for any agent request:
GOAL: what the finished result should be
CONTEXT: which project / files it should work in
DONE WHEN: how the agent knows it succeeded
Fill those three in and you've written a great agent task.Your First Agent Mindset
Before the quiz, picture it: instead of asking "how do I add a contact form?" and copying code, you say "Add a working contact form to my site and confirm it submits."
Same idea, totally different workflow. The agent reads your project, builds it, tests it, and reports back. You review and approve. That's agentic building.
Quick Check
Let's make sure the assistant-vs-agent difference clicked.
Recap: From Answering to Acting
You've made the leap in mindset:
- An assistant answers; an agent acts on a goal.
- Agents run a think → act → observe loop on your real files.
- You hand over a goal (and a "done when"), not every step.
- Watch and approve — you stay the pilot.
- Tools like Claude Code and Cursor agent mode make this real.
Next up: giving your agent tools so it can reach the web, files, and code.
Yapay zeka eğitmeniyle JavaScript öğren — ücretsiz
Tarayıcında gerçek kod yaz ve çalıştır, 7/24 yapay zeka eğitmeninden anında yardım al; web'de ya da uygulamada kaldığın yerden devam et.
- Kurslar
- 25
- Dersler
- 100
Sıkça Sorulan Sorular
“Yardımcıdan Etmene” dersi ücretsiz mi?
Evet — “Yardımcıdan Etmene” dersin tüm metni burada web'de ücretsiz olarak okunabilir. Etkileşimli olarak pratik yapmak (yerleşik kod editörü ve 7/24 yapay zeka koçu) ve Vibe Coding kursunun geri kalanını açmak için CoddyKit PRO'ya yükselt. Vibe Coding kursu toplamda 4 dersten oluşur.
“Yardımcıdan Etmene” dersinde ne öğreneceğim?
Yapay zekanın yalnızca yanıt vermekle kalmayıp eyleme geçtiği durumlar. Vibe Coding ile uygulamalı kodu tarayıcıda doğrudan çalıştırarak pratik yaparsın ve 7/24 yapay zeka koçu dersi çalışırken sorularını yanıtlar.
Vibe Coding öğrenmeye başlamak için deneyim gerekli mi?
Önceden deneyim gerekmez. CoddyKit'te Vibe Coding, başlangıçtan ileri seviyeye kadar yapılandırıldığı için buradan başlayabilir veya başından başlayıp kendi hızında ilerleme yapabilirsin. Bu, 4 dersinin 1. dersidir.
“Yardımcıdan Etmene” dersi ne kadar sürer?
Çoğu CoddyKit dersi yaklaşık 5–10 dakika sürer. Her biri kısa ve etkileşimli olduğu için sabit ilerleme yaparsın ve web ile uygulama arasında tam olarak bıraktığın yerden devam edebilirsin.
Bu Vibe Coding dersinde kod yazıp çalıştırabilir miyim?
Evet. Her Vibe Coding dersi yerleşik bir kod editörü içerir, bu sayede tarayıcıda gerçek kod yazıp çalıştırabilir ve anlık yapay zeka geri bildirimi alırsın — yerel kurulum gerekli değildir.