Vibe Coding · 강의

큰 작업을 단계로 나누기

기능을 프롬프트로 요청할 수 있는 단위로 분해합니다.

큰 작업을 단계로 나누기은(는) CoddyKit의 무료 Vibe Coding 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Vibe Coding 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Big Tasks Break AI

Ask AI to "build me a todo app with login, a database, and dark mode" in one prompt and you'll often get a tangled mess — half-finished, buggy, impossible to review. AI, like people, does its best work on one clear thing at a time.

The skill in this lesson is decomposition: breaking a big feature into small, promptable chunks you build and verify one by one.

Why Small Steps Win

Building in small steps with AI gives you huge advantages:

Reviewable — you can actually read 20 lines, not 500.
Testable — run each piece and confirm it works before moving on.
Recoverable — if step 3 breaks, steps 1–2 are still safe.
Steerable — you correct course early, not after a giant mess.

Small steps are how pros ship reliable apps with AI.

Plan First, Then Prompt

Before writing code, have the AI help you plan. Ask it to break your feature into a numbered list of steps. You're not building yet — you're getting a roadmap you can follow and reorder.

This planning prompt costs one message and saves you from building the wrong thing.

You are a senior engineer. Don't write code yet. I want to build a 'save favorite articles' feature for my web app. Break this into a numbered list of small, buildable steps, from simplest to most complete. Keep each step to one clear task.

A Good Decomposition

A solid plan turns one scary feature into a checklist. For our "favorites" feature, the AI might return:

1. Add a star button to each article card.
2. Toggle the star's filled/empty state on click.
3. Store the favorited IDs in the browser.
4. Load saved favorites when the page opens.
5. Add a "My Favorites" view that filters the list.

Now each line is its own small prompt.

Prompt One Step at a Time

With the plan in hand, build step 1 only. Tell the AI explicitly to stop there. This keeps the output small and focused.

Notice the constraint: only this step. That prevents the AI from racing ahead and writing the whole feature in one unreviewable blob.

We're following our plan. Build ONLY step 1: add a star button to each article card. Use vanilla JS and HTML. Don't implement saving or toggling yet — just render the button. Return only the code for this step.

Verify Before You Continue

After each step, run it and check. Does the button appear? Good — move on. Broken? Fix this step before adding more. Stacking new code on a broken foundation is how vibe-coded apps fall apart.

Here's a tiny, self-contained piece of step 2 logic — toggling a saved state — that you could verify on its own.

// Step 2 logic, tested in isolation
function toggleFavorite(savedIds, id) {
  if (savedIds.includes(id)) {
    return savedIds.filter((x) => x !== id);
  }
  return [...savedIds, id];
}

let ids = [];
ids = toggleFavorite(ids, 7);
console.log(ids);
ids = toggleFavorite(ids, 7);
console.log(ids);

Carry Context Between Steps

Each new step depends on the last. When you prompt for step 2, remind the AI what step 1 produced — paste the relevant code or describe it. In agentic tools like Claude Code or Cursor, the AI can see your files, so just point at them.

Without this context, the AI may invent different names and break the connection between steps.

Now build step 2: toggle the star when clicked. Here is the button from step 1 so you match its class and structure:

<button class="star-btn" data-id="42">☆</button>

Write the click handler that switches between ☆ and ★. Return only the JS for this step.

The Vertical Slice Approach

Another way to decompose: build one tiny end-to-end slice first, then widen it. Instead of building the whole UI, then the whole backend, make ONE feature work all the way through — then add the rest.

Slice 1: favorite a single hard-coded article, save it, reload it.
Then: apply that working flow to all articles.

A thin working slice beats many half-built layers.

Let's build the thinnest working version first. Make ONLY this work end-to-end: clicking a star on one article saves its id to localStorage and re-reading localStorage shows it's saved. Skip the UI polish and the favorites page for now.

Decomposing in App Builders

Even in prompt-to-app tools like Bolt, v0 and Lovable, small steps win. Generate the first screen, preview it, then ask for the next change. Don't request the entire app in your opening prompt.

Prompt 1: "A landing page with a hero and a sign-up button."
Prompt 2: "Now add a pricing section below the hero."
Prompt 3: "Make the sign-up button open a modal."

You build a real app through a conversation, not one giant ask.

Keep a Running Checklist

Track your steps so you and the AI stay aligned. Keep a simple checklist in your prompt or a notes file and mark progress. This becomes the shared memory of your build.

In Claude Code, a TODO.md or CLAUDE.md works great — the agent reads it and knows what's done and what's next.

Here is our progress. Continue from the first unchecked item.

[x] 1. Star button on each card
[x] 2. Toggle star on click
[ ] 3. Save favorited IDs to localStorage
[ ] 4. Load favorites on page open
[ ] 5. 'My Favorites' filter view

Build step 3 only.

Knowing When to Split Further

If the AI's output for one "step" is still large or buggy, that step was too big — split it again. Signs a step needs breaking down:

The answer is hundreds of lines.
It touches many files at once.
You can't tell if it works by reading it.

There's no shame in tiny steps. The smaller the step, the more control you keep.

Quick Check

You ask AI to build a whole feature at once and get 400 lines you can't follow. What's the best next move?

Recap: Build in Steps

Decomposition is how you tame big builds with AI:

Have the AI plan the feature as a numbered list first.
Prompt one step at a time and tell it to stop there.
Run and verify each step before moving on.
Carry context forward and keep a checklist.
Prefer a thin end-to-end slice, and split further when a step gets too big.

Next: pinning the exact tech stack and style so AI builds it your way.

자주 묻는 질문

“큰 작업을 단계로 나누기” 강의는 무료인가요?

네 — “큰 작업을 단계로 나누기” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Vibe Coding 강의 전체를 잠금 해제할 수 있습니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.

“큰 작업을 단계로 나누기”에서 뭘 배우나요?

기능을 프롬프트로 요청할 수 있는 단위로 분해합니다. 브라우저에서 직접 실행하는 실습 코드로 Vibe Coding을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Vibe Coding을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Vibe Coding은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.

“큰 작업을 단계로 나누기” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Vibe Coding 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Vibe Coding 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Vibe Coding(으)로 돌아가기