Skip to content
Agentic Levels

Everything starts here.

GuestLocal progress only
PreferencesSign in
01Start with one taskBest first move for beginners.02Check your LevelMeasure where you are.03Score an AI resultFind the habit to practice first.04Return to Your WorkScores, links, and checkpoints.
Start here

Begin

HomeThe main entry point.New to AIStart with one useful task.
Know where you are

Measure

Check your LevelUse this after you have tried AI.Fluency ScoreScore an AI result you can review.
Build the habit

Learn

LevelsLessonsTracks
Find the reference

Library

PromptsReferenceResourcesCompare Tools
Turn it into work

Apply

Your Next MoveChoose what AI should change next.Tool SetupGet the tools ready.
Come back later

Return

Your WorkScores, links, and checkpoints.My PathContinue from your level.Updates
Site

Site

PricingAboutFAQ & FeedbackPreferences

© 2026 Fuentes Studio

Privacy·Terms
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

Tracks›Claude Design
L2Lesson 2Free

Chat on a selection for surgical changes

After this, you'll be able to select a single element and chat with Claude about only that part, so your change lands where you mean it and the rest of the design stays put.

Before you start

Complete The four edit modes: Tweak, Comment, Edit, Draw first; this lesson sharpens the Tweak idea into a way to talk to Claude about one element at a time.

The idea

You can select one element on the page and open a chat focused only on it, so Claude changes that part and leaves everything else alone. The keyboard shortcut for this is Cmd + G on a Mac, or Ctrl + G on Windows. A shortcut is a key combination that triggers an action without clicking through menus.

A small button, a whole section, and the full page all get treated as one edit scope.
A small button, a whole section, and the full page all get treated as one edit scope.

Here is the problem this solves. When you type a change into the main chat, Claude looks at the whole design to decide what you meant.

Most of the time that is fine. But sometimes you want a change to touch one element and nothing else, and a whole-page instruction can accidentally nudge more than you intended.

Selecting the element first removes the guesswork. You point at exactly the thing, then talk about only that thing. Claude knows the change is scoped to your selection, so it does not go wandering into the rest of the page.

Here is the before and after: Someone types "make this bigger" into the main chat while three things on the page could count as "this." Claude guesses, and resizes the wrong one. The fluent user selects the headline, presses Cmd + G, and says "make this bigger." Now there is no guessing, because the target is already chosen.

When to reach for it is any change you would describe as surgical: precise, local, and aimed at one element. A single button, one heading, one image, one card. You select it, open the focused chat, and describe the change in plain words, exactly as you would in the main chat.

Why this matters for your allowance and your nerves: a scoped change is less likely to ripple. Fewer surprise side effects means fewer "undo that and try again" rebuilds, which means fewer builds spent from your allowance. Precision up front saves cleanup later.

Select the element, press Cmd + G (or Ctrl + G), and chat about only that part. It is how you make a change land exactly where you mean it.

Try it (8 min)

Watch out for

  • Typing 'make this bigger' into the main chat when several elements could be 'this.' Select the element first so Claude has no room to guess wrong.
  • Using a focused, single-element chat for a page-wide change. If you want the whole palette warmer, the main chat is the right place; scoping it to one element won't help.
  • Forgetting you selected something and then asking for an unrelated change in the same focused chat. The focused chat is about the thing you picked; switch back to the main chat for the rest.
  • Reaching for the mouse to drag the selected element. Selecting is for aiming your words, not for dragging; you still describe the change.

Paste this into Claude

I want to practice writing surgical, single-element instructions for Claude Design, the kind I'd give after selecting one element and opening a focused chat (Cmd + G on Mac, Ctrl + G on Windows).

Imagine a landing page for my [YOUR_BUSINESS_TYPE] with: a hero headline, a "Get started" button, three feature cards, and a footer.

Please:
1. For each of these four targets (the headline, the button, one feature card, the footer), write me a clear single-element instruction I'd give in the focused chat.
2. For each, show the "whole-page" version of the same request next to it, so I can see how the focused version removes Claude's guesswork.
3. Give me a simple test for deciding when a change deserves a selection-first, focused chat instead of the main chat.

Created by potrace 1.16, written by Peter Selinger 2001-2019 What a good response looks like

Here's your surgical-edit practice, for a bakery page:

**1. Headline** → select it, then: "make this two sizes larger and bold."
Whole-page version: "make the headline bigger" (Claude has to find which text is the headline).

**2. "Get started" button** → select it, then: "give this a warm orange background and more padding."
Whole-page version: "fix the button color" (which button? there might be several).

**3. One feature card** → select it, then: "add a small icon at the top of this card."
Whole-page version: "add icons to the cards" (changes all three, maybe not what you wanted).

**4. Footer** → select it, then: "make this smaller and lighter gray."
Whole-page version: "tone down the footer" (vaguer, more room to misread).

**The test:** if your instruction needs the word "this" to be obvious, select the element first. If it's a page-wide change ("warm up the whole palette"), the main chat is fine.

Created by potrace 1.16, written by Peter Selinger 2001-2019 What good looks like

  • You can explain what selecting an element first does: it scopes the change so Claude doesn't touch the rest
  • You know the shortcut to open a focused chat on a selection (Cmd + G on Mac, Ctrl + G on Windows)
  • You can write a single-element instruction that names the change without naming the location
  • You can tell when a change is 'surgical' enough to deserve selecting first
Design Selection ScopeMove through Chat on a selection for surgical changes, check proof, then fix only the weak part.
yesnorun it again
StartBegin with the real task
Chat on a selection for surgicalAfter this, you'll be able to select a single element and chat with Claude about only
1Proof visible?You can explain what selecting an element first does: it scopes the change so Claude
Ready to useTake a change like 'make this stand out more,' then say which one element you'd
Fix the weak partBreaks when you give local, precise instructions through the whole-page chat. Claude

When this breaks

  • Breaks when you give local, precise instructions through the whole-page chat. Claude has to infer the target, so it sometimes changes the wrong element and you spend a build undoing it.
  • Breaks when you expect a selection to let you drag and resize by hand. Selecting scopes your description; it does not turn the canvas into a drag-first design app.

AI can help with this

Not sure if your change is scoped right? After you select an element and describe the change, you can ask Claude in the focused chat: 'will this only affect the thing I selected?' Claude confirms or tells you it needs to touch more, so you are never surprised.

The edit scope shrinks to the exact target, with surrounding areas left locked.

Created by potrace 1.16, written by Peter Selinger 2001-2019 You can now

✓

You can complete the lesson outcome in Claude Design or in the supporting tool the lesson names.

  • ✓You can explain what selecting an element first does: it scopes the change so Claude doesn't touch the rest.
  • ✓You know the shortcut to open a focused chat on a selection (Cmd + G on Mac, Ctrl + G on Windows).
  • ✓You can write a single-element instruction that names the change without naming the location.
  • ✓You can tell when a change is 'surgical' enough to deserve selecting first.

Key takeaways

Selecting one element and chatting about only that part (Cmd + G or Ctrl + G) scopes your change so Claude touches that element and nothing else. It is how surgical, local changes land exactly where you mean.

  1. 1Select one element, then open a chat focused only on it, to scope a change precisely.
  2. 2The shortcut is Cmd + G on a Mac, or Ctrl + G on Windows.
  3. 3Selecting first removes Claude's guesswork about which element 'this' refers to.
  4. 4Use it for surgical, local changes: one button, one heading, one image, one card.
  5. 5Scoped changes ripple less, which means fewer surprise side effects and fewer cleanup builds.

Created by potrace 1.16, written by Peter Selinger 2001-2019 Go deeper

  • How to use Claude Design (step-by-step on this site)
  • Claude Design full tutorial (selection and focused editing)

Was this helpful?

Up nextStructural vs granular feedback→
← Back to Claude Design