diff --git a/presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html b/presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html index 7e05fed..f67b2c3 100644 --- a/presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html +++ b/presentation/2026-04-25-gdg-kolachi-cli-claude-code-gemini/index.html @@ -516,37 +516,66 @@ - +
A dedicated Claude worker — own context, tools, focus.
+What the specialist (or Claude) can actually do.
+What Claude holds in its head now — 200K–1M tokens.
+Repeatable step-by-step recipes — like an AC install guide.
+Persistent instructions you write.
+Read, Edit, Bash, WebSearch.
Claude in Chrome actually sees browser pages.
Instructions you write.
-Instructions Anthropic bakes in.
Allow / ask / deny for tool use.
Deterministic scripts that fire on events.
@@ -557,7 +586,7 @@ -Same question, different prompt — sometimes the harness asks first instead of acting.
Same question across runs can route through different tools and sources.
External tools can time out, return errors, or fetch stale data.
A harness gives the brain hands — but not a fixed routine.
@@ -600,7 +629,7 @@ -Even before you set up any structure, how you prompt matters. Specific beats vague. Context beats assumption.
We're going to learn five concepts using one running example: a weather reporter agent that fetches Dubai's temperature and renders a weather card. Same person — five different angles.
An agent is Claude playing a specific role. Meet the weather reporter — a specialist hired to fetch and report weather data for Dubai. Same Claude, different hat.
The difference in one picture: prompting is asking a stranger on the street; using an agent is asking your dedicated specialist.