퓨샷 예시
원하는 스타일과 형태를 인공지능에 보여주십시오.
퓨샷 예시은(는) CoddyKit의 무료 Vibe Coding 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Vibe Coding 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Show, Don't Just Tell
Describing the code you want with words works — but showing an example works even better. This technique is called few-shot prompting: you give the AI one or more examples of input and the matching output, then ask it to follow the same pattern.
It's the difference between explaining a recipe and handing someone a finished dish to copy. Examples remove guesswork and lock in your exact style.
Zero-Shot vs Few-Shot
Zero-shot = you ask with no examples. Few-shot = you include a couple of examples first.
- Zero-shot: "Write a function that turns a title into a URL slug."
- Few-shot: same request, plus 2 examples of titles and the exact slugs you expect.
Few-shot wins whenever the format matters and is hard to describe in words. You teach by demonstration.
Your First Few-Shot Prompt
The pattern is simple: list a few input → output pairs, then leave the last one open for the AI to complete.
Here we teach the AI exactly how our slugs should look. It now knows: lowercase, spaces become dashes, punctuation dropped — without us writing a single rule.
Turn each title into a URL slug, following these examples:
Title: "Hello World!" -> hello-world
Title: "My First App" -> my-first-app
Title: "10 Tips & Tricks" -> 10-tips-tricks
Title: "Vibe Coding 101" ->Examples Teach Style
Few-shot isn't only for data formats — it's how you transfer coding style. Show the AI one function written your way, and it will match your naming, comments and structure on the next one.
This is gold in a real project: paste an existing function as the example, then ask for a new one "in the same style." The AI matches your codebase instead of inventing its own conventions.
Here is how I write functions in this project:
// Returns the average of a list of numbers
function averageOf(numbers) {
const total = numbers.reduce((sum, n) => sum + n, 0);
return total / numbers.length;
}
Write a function maxOf(numbers) in exactly this style.See the Matching Output
When you give a clean example like the one before, the AI returns code that fits right in. Here's the kind of result that prompt produces — same comment style, same naming, same shape.
Run it to confirm the pattern holds.
// Returns the largest number in a list
function maxOf(numbers) {
return numbers.reduce((biggest, n) => (n > biggest ? n : biggest), numbers[0]);
}
console.log(maxOf([3, 9, 2, 7]));
console.log(maxOf([-5, -1, -10]));How Many Examples?
You rarely need many. A few rules of thumb:
- 1 example — when the pattern is mostly clear and you just want to pin the style.
- 2–3 examples — when the format has edge cases (punctuation, numbers, special words).
- Add an edge case on purpose so the AI learns how to handle the tricky input, not just the easy one.
More than 3 rarely helps and just makes the prompt long.
Format phone numbers like these examples (note the edge case with extra digits):
"1234567890" -> (123) 456-7890
"5551234567" -> (555) 123-4567
"12345" -> invalid number
"9998887777" ->Cover the Edge Cases
The trick that separates good few-shot prompts from great ones: include the weird input. If you only show happy-path examples, the AI assumes inputs are always clean — and your app crashes on the first odd one.
By showing an invalid or empty example and the response you want, you teach error handling by demonstration. No long explanation needed.
Convert each price string to a number. Handle bad input as shown:
"$19.99" -> 19.99
"$0" -> 0
"free" -> null
"" -> null
"$120.50" ->Few-Shot for Tone and Text
Examples aren't only for code logic — they shape any text the AI writes. Building an app with messages, button labels, or error text? Show two examples in your voice and the AI matches it.
This keeps your whole product consistent: friendly, terse, professional — whatever you demonstrate.
Write friendly, short error messages in this style:
Problem: empty email field -> "Oops! We need your email to continue."
Problem: password too short -> "Almost there — make your password a bit longer."
Problem: file too large ->Examples Inside Real Tools
Few-shot works everywhere you prompt:
- Cursor / Claude Code: paste an existing function as the example, ask for a sibling function "in the same style."
- v0 / Lovable: describe a component, then say "like this card" and paste a sample to copy.
- Copilot: write one example function above, and its autocomplete mimics your pattern for the next one.
The AI is a pattern-matcher — give it the pattern.
// @cursor: here is our standard API helper, follow this exact shape
async function getUser(id) {
const res = await fetch(`/api/users/${id}`);
if (!res.ok) return null;
return res.json();
}
// Now write getOrder(id) in the same style.When Examples Backfire
Few-shot is strong, so be careful:
- A buggy example teaches the bug — the AI copies your mistake.
- Inconsistent examples confuse it: if your two slugs follow different rules, output is random.
- Examples that are too narrow make it overfit and fail on anything new.
Rule: your examples must be correct, consistent, and cover the range of inputs you expect.
Combine With Roles and Constraints
The most reliable prompts stack everything you've learned: a role, a few constraints, and one or two examples. Role sets the skill, constraints set the rules, examples set the exact shape.
That combination is how builders get code they can paste and ship — instead of rolling the dice on each request.
ROLE: Senior JS engineer.
CONSTRAINTS: vanilla JS, return only the function.
EXAMPLE:
isEven(4) -> true
isEven(7) -> false
TASK: Write isPositive(n) following the same simple style as isEven.Quick Check
You're using few-shot prompting to format dates, but the AI keeps breaking on empty input. What's the best fix?
Recap: Teach by Example
Few-shot prompting is one of your sharpest tools:
- Show input → output pairs and let the AI complete the pattern.
- Examples transfer format, style, and tone better than words.
- Include edge cases so the AI learns error handling.
- Keep examples correct and consistent — bugs and contradictions get copied.
- Stack with roles + constraints for the most reliable output.
Next: breaking big features into small, promptable steps.
자주 묻는 질문
“퓨샷 예시” 강의는 무료인가요?
네 — “퓨샷 예시” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Vibe Coding 강의 전체를 잠금 해제할 수 있습니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.
“퓨샷 예시”에서 뭘 배우나요?
원하는 스타일과 형태를 인공지능에 보여주십시오. 브라우저에서 직접 실행하는 실습 코드로 Vibe Coding을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Vibe Coding을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Vibe Coding은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.
“퓨샷 예시” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Vibe Coding 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Vibe Coding 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.