タスクに合わせたツール選び

You know the three families; the real skill is matching a tool to a task. Like a toolbox, you wouldn't use a hammer to tighten a screw. Let's match the common ones.

When you want to understand an idea — what an API is, how a loop works — a chat assistant is perfect. Ask for a beginner-level answer and keep asking follow-ups.

Want a working app from scratch, like a calculator or notes page? Reach for an agent. Describe what it does and any limits, then review and test what it built.

Got an error you don't understand? A chat assistant shines: paste the error and code and ask what went wrong. Always include the exact error text — details help a lot.

Inside a project making lots of small changes — renaming, tweaking layout? An IDE assistant keeps you fast, suggesting code right where your cursor is.

Adding something big to an existing app, like a search bar or dark mode? An agent handles multi-file changes well. Be specific so it doesn't change more than you meant.

Not sure how to start? Use a chat assistant to plan first — ask for the steps before any code. A clear plan makes the build smoother, however you do it.

A quick rule by task size: tiny question or snippet, use chat; small ongoing edits, use an IDE assistant; whole feature or app, use an agent. When in doubt, start small.

Also match by confidence: unsure what you want? Chat first to think it through. Clear goal and want it done? Hand it to an agent. Clarity lets you safely automate.

Picking the wrong tool isn't a disaster — you just adjust. Too small? Ask an agent. Too much? Switch to chat to learn what happened. The goal is progress, not perfection.

Before any task, ask three quick things: how big is it, do I want to learn or build, and how clear is my goal? The answers point you to the right tool.

Let's test your tool-matching instinct.

Well done! Learning or fixing an error, reach for chat; small edits, an IDE assistant; a whole feature, an agent. Match by size and clarity, and adjust freely. Next: set up your first tool.