A real job
    Jesse Diehl
    Working with Claude

    Working with Claude, the Indochino way · October 2026

    You direct. Claude does the legwork.

    Claude works inside Figma, Photoshop, InDesign and the rest, following the house rules the team has already taught it. You set the direction, judge the result and decide what ships.

    Start hereThree minutes, nothing to install, nothing at risk.

    This is the system Jesse built for working with Claude at Indochino: the apps it can drive, the jobs it already does, and the places where it stops and waits for you. The first four sections take about ten minutes. The rest is reference for when a job needs it.

    At any point, if something is unclear, just ask Claude in plain words. It will explain.

    EmailPaid socialImagesRetailPrintInDesignWeb pagesFilesVideoHyperframesResearch
    Fig. 1 · Everything Claude can do, with you at the centre.Hover or tap a branch to see a real job.

    In a chat window

    Words only. It answers in text, and you move the text into your apps yourself.

    Working inside your apps

    You, the director

    Vision, taste and the final yes.

    Claude, your crew

    Designer, editor, builder, researcher. They read, build, check and report back.

    Your apps and folders

    It opens them and works inside them.

    Social board in Figma
    Social set in Figma
    Email frames in Figma
    Email in Figma
    Print-ready brochure PDF
    Print file
    Store window mockup
    Store window

    Real files. Every picture here came out of a job Claude and Jesse did together.

    Fig. 1.1 · The idea in one pictureYou direct, Claude does the legwork in your apps, and real files come out.

    Claude does not stop at words. Each job below shows what it opened, what it built, and which steps still wait for your yes before anything leaves the team or reaches a customer.

    How a job goes

    Every job in this guide follows the same five beats. You say what you want, Claude plans it, you approve the plan, Claude does the work inside your apps, and you check it before anything ships.

    1. You pick it up

      Open the Asana task. It is the brief. Say what done looks like.

    2. Claude plans

      Plan mode. It reads, writes the plan and changes nothing.

    3. You approve

      Read it, fix it in plain words, then say yes.

    4. Claude runs

      Auto. It works in Figma, InDesign and your folders.

    5. You check

      Look at the result like a proof. Nothing ships without you.

    Fig. 0 · One job, five beatsRound rings are people, the diamond is your yes

    The crew is fast and the house rules are built in. It does the legwork, and you hold the vision. The plan is where you catch a wrong turn while it still costs nothing.

    You direct. Claude does the legwork.

    You are the director. Claude is a crew at your disposal: a designer, an editor, a web builder, a researcher, a motion designer and more. The team has already taught the crew the Indochino design system and the house rules. What this piece should feel like, what is good enough and what ships stay with you.

    You

    • Set the vision and say what done looks like.
    • Judge what looks right.
    • Approve what ships.
    • Say when it is done.

    Claude

    • Finds the files and the facts.
    • Does the repetitive work.
    • Drafts options and checks its own work.
    • Explains what it did when you ask.

    Together

    • You say what is wrong in plain words, like marking up a proof.
    • Claude fixes it.
    • You look again.

    The crew follows the house rules without being reminded. It makes something good when a trained eye directs it.

    A good request to Claude is the same as a good request to a person: what you want, what it is for, which files to use and where the result goes.

    The first try is often wrong. That’s normal, and a second try in plain words is the cost of working fast.

    Start here

    Pick one. You don’t need to read all of this, so do one of the tries below and come back for the rest when you need it, because each one takes a few minutes and changes nothing.

    Try 1

    Say hello

    1. Open the Claude desktop app.
    2. Click Code.
    3. Choose any folder to work in.
    4. Paste the line below.
    5. Read the answer.

    Paste this

    Say hello and tell me, in five short lines, what you can do for a designer. Change nothing.

    You will see

    A short, friendly list. Nothing is created or changed. If the app is missing or you don’t see Code, tell Jesse. That counts as done.

    If it is wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Your original files stay untouched unless you say yes.

    Try 2

    Get a second pair of eyes on a Figma frame

    1. Copy the link to the frame.
    2. Open the Code tab in the Claude desktop app.
    3. Paste the line below.
    4. Replace the bracket with your link.
    5. Look at the answer like a proof.
    6. Ask about anything unclear.

    Paste this

    Look at this Figma frame [paste link]. Tell me what a senior designer would flag: hierarchy, type and spacing. Change nothing.

    You will see

    A screenshot Claude took of the frame, then notes with the reason for each. If Claude can’t open the link, tell Jesse.

    If it is wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Your original files stay untouched unless you say yes.

    Try 3

    Pick up an Asana task together

    1. Copy the task link.
    2. Open the Code tab in the Claude desktop app.
    3. Paste the line below.
    4. Replace the bracket with your link.
    5. Answer the questions Claude asks.

    Paste this

    Here is my Asana task [paste link]. The task is the brief. Tell me in a few lines what you understand it asks for, then ask me what is missing. Do not write to Asana.

    You will see

    Claude’s short summary of the task, then a few questions. Nothing is made or changed yet. If Claude can’t open the link, tell Jesse.

    If it is wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Your original files stay untouched unless you say yes.

    Try 4

    Plan a rename without running it

    1. Open the Code tab in the Claude desktop app.
    2. Choose the folder you want to tidy.
    3. Paste the line below.
    4. Read the dry run, the list of what would move.
    5. Ask for the real run only if the list looks right.

    Paste this

    Plan a rename for the files in this folder. Write the rename script and the undo script. Run only the dry run and show me the first twenty lines.

    You will see

    A plan table, two scripts and a list of what would move. Nothing moves.

    If it is wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Your original files stay untouched unless you say yes.

    Try 5

    Point Claude at a folder

    1. In Finder, select a folder of images.
    2. Press Option, Command and C.
    3. Open the Code tab in the Claude desktop app.
    4. Paste the line below.
    5. Press Command and V to paste the path over the bracket.
    6. Check the table.

    Paste this

    Look at the images in this folder: [paste path]. Make a table with each file name, its size in pixels and whether it is square. Change nothing.

    You will see

    A table of your files with their sizes. Nothing moves or changes.

    If it is wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Your original files stay untouched unless you say yes.

    Two more tries: a safe rename and a folder

    Try 4

    Plan a rename without running it

    1. Open the Code tab in the Claude desktop app.
    2. Choose the folder you want to tidy.
    3. Paste the line below.
    4. Read the dry run, the list of what would move.
    5. Ask for the real run only if the list looks right.

    Paste this

    Plan a rename for the files in this folder. Write the rename script and the undo script. Run only the dry run and show me the first twenty lines.

    You will see

    A plan table, two scripts and a list of what would move. Nothing moves.

    If it is wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Your original files stay untouched unless you say yes.

    Try 5

    Point Claude at a folder

    1. In Finder, select a folder of images.
    2. Press Option, Command and C.
    3. Open the Code tab in the Claude desktop app.
    4. Paste the line below.
    5. Press Command and V to paste the path over the bracket.
    6. Check the table.

    Paste this

    Look at the images in this folder: [paste path]. Make a table with each file name, its size in pixels and whether it is square. Change nothing.

    You will see

    A table of your files with their sizes. Nothing moves or changes.

    If it is wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Your original files stay untouched unless you say yes.

    How to work with Claude

    Three habits make Claude far more useful: pick the right mode, plan before you build, and point it at exactly the file or folder you mean. They take a minute each to learn and save hours later.

    Three modes

    A mode decides how much Claude asks before it acts. You choose it, and you can change it at any time.

    Auto

     

    Claude handles the permission questions itself, so you are not asked to approve each step.

    Use it when

    You have read and approved a plan and trust the job to run.

    Manual

     

    Claude always asks before making changes. It is the slowest mode and the safest.

    Use it when

    You are new, or the job touches files you care about.

    Accept edits

     

    Claude accepts every file edit without asking. Other actions still ask.

    Use it when

    You want to watch the other steps, but not click on every file change.

    Plan

     

    Claude reads, thinks and writes a plan before making changes. It changes nothing until you approve.

    Use it when

    The job has many steps, or you are not sure yet what you want.

    The mode menu in the Claude app, listing Auto, Manual, Accept edits, Plan and Bypass permissions, with a tick beside Auto
    The bottom left of the message box showing a plus, a microphone and the current mode, Auto

    Open the menu from the mode name at the bottom left of the message box. The tick shows where you are now.

    The menu also lists Bypass permissions, which accepts everything without asking. Leave it alone.

    Fig. 3.1 · The mode menu, from the Claude appA real screenshot, not a mock-up.

    Check your mode

    Which mode are we in? Tell me your plan before you change anything.

    Plan first, then let it run

    For anything with many steps, start in Plan mode. Claude writes a plan, you read it and fix it, and only then does the work begin.

    Working this way often lets Claude finish a whole project in one go. It also keeps Claude from drifting away from what you meant, because you checked the plan before anything was built.

    Auto and Accept edits can move and rename files, so switch to either only after you have read the plan. Sending, publishing, spending and deleting still wait for your yes.

    1. Switch to Plan.
    2. Open the task and say what done looks like.
    3. Read the plan Claude writes.
    4. Fix anything wrong by replying in plain words.
    5. Approve the plan.
    6. Switch to Auto.
    7. Tell Claude to start.
    8. Check the result.

    Say it like this, at step 2

    Plan how to [the job]. Done looks like [the result]. Do not change any file until I approve the plan.

    More habits: be interviewed, ask why, point at a file, four commands

    Get interviewed first with

    A plan is only as good as Claude’s grasp of your goal. Type and say what the project is. Claude then interviews you one question at a time, and it suggests an answer to each, so you can say yes or change it.

    When the questions run out, Claude understands the goal well enough to plan the work. Then switch to Plan mode.

    Try this

    I want to make a short video for the new fall suits. Interview me before you plan anything.

    When something doesn’t make sense, ask

    Ask Claude in the chat, in plain words. It will explain, and that is the fastest way to learn. Ask as often as you like.

    For a longer lesson on any topic, type . It builds a short course and saves your notes in the folder you are in, so make a new folder in Finder and choose it as the folder to work in. If you don’t see or when you type a slash, ask Jesse. Typing also opens short interactive lessons, if your version has it.

    Ask this

    Why did you choose that? Explain it in plain words.

    Start a lesson

    how Meta ad crop zones work

    Point Claude at the file

    In Finder, select a file or a folder and press these three keys. Finder copies its full path. Paste it into your message with Command and V.

    OptionCommandC

    Now Claude knows exactly which file or folder you mean. Paste the path exactly as it was copied. You can also drag a file into the message box, or type @ and pick a file. If a OneDrive file shows a cloud icon, let it finish syncing before you point Claude at it.

    Say it like this

    Use this as the reference image: [paste path]

    Say it like this

    Use every image in this folder as references: [paste path]

    Say it like this

    Save the results in this folder: [paste path]

    Say it like this

    Upscale this photo with : [paste path]

    Four commands worth knowing

    List what you can type.
    Start a fresh conversation.
    Pick up an earlier conversation.
    Switch to Plan mode.

    When it goes wrong

    Say what is wrong in plain words and ask again. If it is wrong twice, stop and message Jesse. Claude can be wrong, so look at anything that matters at full size before it leaves your desk.

    Where Claude stops

    Six things always wait for you. Claude drafts each of these, shows you the result and prepares everything around it, then stops and waits for your clear yes before anything leaves the building.

    1. Publish

      Fastr pages and anything public wait for your yes. Claude mocks the page at desktop, tablet and mobile first and shows screenshots.

    2. Send

      Email, Teams and messages as you. Claude writes a draft into Outlook Drafts. You press send.

    3. Spend credits

      Image and video generation costs real money. Claude shows the shot table and the credit count, then waits. A new comment from you cancels an earlier yes.

    4. Write to Asana

      Claude reads tasks and comments. The connection would allow writes, but the rule is no comments, no assigning, no renaming and no status changes.

    5. Write to Bloomreach

      Production is read only by rule. The system does not enforce it, and block edits reached production in September. No test sends and no edits to live assets without your say-so.

    6. Delete or overwrite

      New files, never overwrites. Originals and shared renders stay untouched, and nothing is deleted.

    Claude will not do these, even if asked

    • Enter your passwords, keys or tokens.
    • Beat a bot check or a CAPTCHA.
    • Regenerate a real person’s face.
    • Write into the external GROWTH folder.
    • Move a login from one machine to another.

    What Claude is

    Reference. Skip until you need it.

    Claude is the AI. Where you talk to it changes what it can do.

    Chat on the web or your phone

    You type, it answers and writes. It cannot reach your files.

    The Code tab in the Claude desktop app

    It works inside a folder on your Mac, opens apps like Figma and Photoshop, and saves what it makes. The work in this guide happens here.

    The same engine in a Terminal window

    The same power with no buttons. Jesse mostly uses the Code tab.

    KnowsWhat Claude remembers ChecksWhat verifies the work DoesWhat carries out a job TouchesThe apps it operates ShipsWhat leaves, after your yes
    Eleven words you will meet, one line each

    Each word below is a part of the setup, and each one has a real example from Jesse’s work that you can try for yourself.

    Claude

    The AI itself. It reads what you give it, thinks, then writes or acts. It starts every session knowing nothing about your work except what gets loaded for it.

    In practiceThe house rules and short notes load at the start of every session, so it already knows the brand uses EB Garamond and Inter and nothing else.

    Claude Code

    Claude working inside a folder on your Mac. It can read and write files, run scripts and use other apps. Most of the work in this guide happens here.

    In practiceSay "make the paid ad set" and it opens Figma, Photoshop and Higgsfield, then saves the results to a project folder.

    Skill

    A written procedure Claude follows for one kind of job. You type a slash and its name to start one. That typed name is called a command.

    written procedureClaude follows itfinished job

    In practice sends an email through five reviewers and reports what each one found.

    Connector

    A switch in claude.ai that lets Claude use a web service such as Asana or Figma as you. You turn it on once.

    Claudeswitch in claude.aiweb service

    In practiceWith the Asana connector, Claude reads a task, its comments and its attachments. It never writes back.

    MCP

    A small program that lets Claude operate another app. It can run on your Mac or on the web.

    Claudesmall programapp on your Mac

    In practiceThe Photoshop MCP lets Claude make a layer, run Remove on a belt loop, then look at a preview of the canvas.

    Plugin

    A bundle of skills and tools you install in one go.

    In practiceThe team plugin carries the shared email, paid and print skills, so a new teammate gets them with two commands.

    Hook

    A script that runs by itself at a set moment, so a rule is enforced without anyone remembering it.

    set momentautomatic checkallow or refuse

    In practiceA check reads every image prompt before it goes to Higgsfield and refuses one that is badly formed.

    Subagent

    A second Claude started to do one focused job, such as reviewing a file, then report back.

    Claudesecond Claudereport back

    In practiceThe strict gate reviewer reads an email last and says pass or fail, with the rule number for each flag.

    Lock

    A description pasted word for word into every prompt, so a face or a suit never drifts.

    In practiceThe model’s face description is copied from the shoot file, unchanged, into every prompt of that shoot.

    Memory

    Short notes Claude loads every session: corrections, rules and where things live. One fact per file.

    In practice"No surname on a review" sits in one note, and Claude applies it without being told again.

    Vault

    A folder of linked notes Claude reads before it answers, so the answer already has research behind it.

    In practiceAsk a question about past work and get an answer that names the pages it came from.

    Everything Claude can do

    Pick the job from your own day

    Eleven kinds of work, with real things Claude does in each. Pick one. Find the one from your own day, copy its try line and watch what happens, because each row carries a tag that tells you what is working today.

    Tags mark the exceptions
    No tagClaude does it, the usual case
    Claude + youClaude does it and you steer
    YouYou do it
    designedPlanned, not built
    blockedCannot be done today
    unverifiedNot checked yet
    7.1EmailA weekly send goes from a brief to a built frame to an audited email. Claude does the writing, the building and the checking. People still press Export and Send.
    Fig. 7.1Seven emails built from stock parts in one afternoon, using only their briefs.

    A real job

    Browse and cart abandon emails

    Browse abandon and cart abandon emails, built in Figma from the Email Love design system. Claude drafts the copy, builds each frame from stock parts and checks it. You export and send.

    7.1

    Email

    A weekly send goes from a brief to a built frame to an audited email. Claude does the writing, the building and the checking. People still press Export and Send.

    What Claude does here

    • Writes the brief on the house template, with copy counted against each module’s character budget. Claude
    • Builds the email frame in Figma from stock EmailLove components, then audits what actually landed. Claude
    • Runs five reviewers at once: design, performance, eye flow and voice, then a strict gate that only says pass or fail. Claude
    • Checks the Figma frame for the subject and preheader pair, one main button, dark mode contrast and tap size. Claude
    • Reads Bloomreach catalog fields to confirm a product’s name, fabric and price. Read only. Claude
    • 3 more
      • Drafts cart, browse and welcome emails in Figma to a locked spec, with a bracketed gap where a customer quote would go. Claude
      • Reads a failed HTML export against the Figma tree and fixes the Figma side. Claude + you
      • Presses Export in the EmailLove plugin panel. blocked

    Try this

    Write a Spotlight email brief for the October 9 through 12 offer. Use the brief template and stop before any Figma build so I can read it first.

    What you will see
    A brief with one block per module, counts written as used over budget, and a pass or fail from two gates.
    Needs your yes
    Anything that sends, and any upload to Bloomreach. Claude does neither.
    Does not work yet
    The plugin Export button is closed to Claude. Some component properties look set and do nothing, so every build gets an audit pass.
    FigmaEmailLoveBloomreach (read)email-briefemail-revise
    7.2Paid social and adsClaude reads the Asana brief, checks what is winning on Meta, then drafts concepts and type mock-ups on a throwaway page. You pick what lives.
    7.3Image creationClaude reads a reference, writes the prompt, fires the render once you say yes, then measures and looks at what came back.
    Fig. 7.3One finished frame, built from the parts in Fig. 6.

    7.3

    Image creation

    Claude reads a reference, writes the prompt, fires the render once you say yes, then measures and looks at what came back.

    What Claude does here

    • Reads one photo for pose, framing, light and grade, fabric or place, and writes each down as plain text. Claude
    • Writes the prompt scene first, with the face and wardrobe locks pasted byte for byte from the shoot file. Claude
    • Checks every prompt against the house method before a single credit moves. Claude
    • Fires renders on Higgsfield after your yes, waits for the jobs, downloads the frames and logs the job numbers. Claude
    • Upscales to 2K or 4K, then measures the width and height of every frame. Claude
    • 4 more
      • Opens frames at full size and compares colour against the real garment photo. Claude
      • Pulls full resolution product photos by product name from the product CDN. Claude
      • Removes belt loops and stray buttons in Photoshop with Remove, run by script. It worked 8 of 8 on 4 October. Claude
      • Matches the grade of a render to a reference photo. blocked

    Try this

    Read this reference with the pose and composition readers, then write the prompt for the model in the navy suit. Show me the shot table and the credit count. Do not fire anything.

    What you will see
    Two short reads of the reference, a table of shots, the credit math, and then a wait.
    Needs your yes
    Every render, every upload and every re-run. A new comment from you cancels an earlier yes.
    Does not work yet
    Higgsfield cannot match a reference grade, grain cannot be copied from a photo, and interlocked hands render as blobs. Claude never regenerates a real person’s face.
    HiggsfieldPhotoshopCapture Onescene-promptpose-dnacomposition-dnaphoto-dnasuit-dna
    7.4RetailWindow and barricade graphics are built from a store drawing, checked against the glass, and handed over as a dated package.
    Fig. 7.4Five window bays checked: zero lines of type cross a mullion.

    A real job

    Bellevue Square window

    The Bellevue Square window job from late September 2026: a flat drawing becomes a design, then a mockup you can judge. The same path works for any retail graphic.

    7.4

    Retail

    Window and barricade graphics are built from a store drawing, checked against the glass, and handed over as a dated package.

    What Claude does here

    • Reads a store drawing and lists each glass bay with its width. Claude
    • Builds window and barricade layouts in InDesign at a quarter of final size, to print at four times. Claude
    • Runs an InDesign script that checks no type crosses a mullion, the bar between two glass panes. One run found zero crossings across five bays. Claude
    • Scouts a venue: a plate, a camera list and a grade note, so one room can be shot again and again. Claude
    • Builds on-model showroom images from a library of real showroom photos. Claude
    • 3 more
      • Applies a sightline rule to hoardings: eye at 5 feet 3 inches, a short look up. Claude
      • Packs a dated delivery folder with a PDF for the review task. Claude + you
      • Downloads the official logo as a vector file. A traced stand-in sits in the layout instead. blocked

    Try this

    Here is the window drawing for the new store [attach]. List each glass bay with its width, then propose a layout that keeps type inside one pane. Build nothing yet.

    What you will see
    A table of bays and a short layout plan with the pane each line of type sits in.
    Needs your yes
    Any credit spend, and any file that goes to a printer. Claude never sends it.
    Does not work yet
    The official logo vector is out of reach, so a traced stand-in is used. One hoarding job still has its surface unconfirmed.
    InDesignPhotoshopHiggsfieldlocation-scoutlocation-dna
    7.5PrintPrint has one hard gate. Claude asks three questions before it touches colour: offset or digital, coated or uncoated, and the exact CMYK profile.
    Fig. 7.5Four print checks before any file goes out: resolution, RGB, overset text, links.

    A real job

    Wedding brochure

    Print jobs follow one path: layout in InDesign, checks for colour and size, then a print-ready PDF for the printer. The wedding brochure shows all three stages. Claude does not send files to the printer.

    7.5

    Print

    Print has one hard gate. Claude asks three questions before it touches colour: offset or digital, coated or uncoated, and the exact CMYK profile.

    What Claude does here

    • Asks the three print questions first and waits, because colour work done on the wrong profile has to be redone. Claude
    • Converts the placed photos in Photoshop to the printer’s profile, such as coated GRACoL with a 300 ink cap, and saves new files. Claude
    • Preflights the open InDesign file and lists each failing item: low resolution, RGB colour, overset text and broken links. Claude
    • Exports a PDF/X from InDesign with bleed, then reads the page boxes in the exported file. Claude
    • Packages the InDesign fonts, links and PDF/X for the printer and writes a handoff note that lists what is inside. Claude
    • 2 more
      • Builds large format files in InDesign at the finished size in inches, so the printer does not resample. Claude
      • Drafts prepress scripts for InDesign and Photoshop and hands them to you. It never runs them unreviewed. designed

    Try this

    Before we touch colour, ask me the three print questions for this postcard. Wait for my answers.

    What you will see
    Three plain questions, then a pause until you answer.
    Needs your yes
    Sending anything to a printer. Claude packages the files and you send them.
    Does not work yet
    Claude sees the page only through exports and a window capture. The printer’s real profile is often assumed. Illustrator beta refuses scripts.
    InDesignPhotoshopindesign-scripting
    7.6InDesignYou never touch the script. Describe the change in plain words with the document open. Claude writes the script, InDesign runs it, and the numbers return in a result file.
    Fig. 7.6258 layout checks from four books, run by script.

    A real job

    Entry doors page with a check

    Claude runs a script inside InDesign, reads the numbers back and reports pass or fail. For this job the mullion check found zero crossings.

    7.6

    InDesign

    You never touch the script. Describe the change in plain words with the document open. Claude writes the script, InDesign runs it, and the numbers return in a result file.

    What Claude does here

    • Checks margins, fonts, links and swatches with read-only scripts. Claude
    • Restyles a document to the brand: fonts, swatches and paragraph styles. Claude
    • Resizes the pages, reflows the text, places icons and merges swatches, then lists every change it made. Claude
    • Packages the dollar and Canadian versions together and compares their geometry. Claude
    • Cleans file metadata with an IDML round trip. Claude
    • 3 more
      • Judges a layout against 258 checks drawn from four layout books, and cites the rule number. Claude
      • Exports a page as a picture, then looks at it instead of trusting the script’s own report. Claude
      • Shows a live screenshot of the open InDesign page. Today you get an exported picture after each script. blocked

    Try this

    Check the margins in the document I have open and tell me which rule they break. Change nothing.

    What you will see
    Claude writes a read-only script, InDesign runs it, and you get a finding with a rule number and the measured values.
    Needs your yes
    Any script that changes the document. Claude saves a backup first.
    Does not work yet
    No live view of the page. The script’s reply comes back through a file. The scripting notes cover about 50 of roughly 800 object types.
    InDesignindesign-scriptingdesign-loopdesign-critique
    7.7Ecommerce web and landing pagesClaude mocks a page at three widths, builds it in Fastr with a real browser, then reads every variant back. Publishing is a hard stop.
    Fig. 7.743 of 43 products linked on the FW26 lookbook, one dot each.

    7.7

    Ecommerce web and landing pages

    Claude mocks a page at three widths, builds it in Fastr with a real browser, then reads every variant back. Publishing is a hard stop.

    What Claude does here

    • Mocks a landing page at desktop, tablet and mobile widths and shows you three screenshots. designed
    • Builds in Fastr through a real mouse and keyboard, and pastes code blocks into the editor. Claude
    • Reads back the text and images of each variant and builds a table of slots by device, so tablet is not forgotten. Claude
    • Pulls product images from the CDN and checks product fields in Bloomreach. Read only. Claude
    • Reframes images to the 5000 by 5000 product spec and checks the mask for leftovers. Claude
    • 2 more
      • Turns a design file into a hosted lookbook page, links 43 of 43 products, and asks before any push goes live. Claude
      • Publishes a Fastr page. blocked

    Try this

    Mock the hero for a mill landing page at desktop, tablet and mobile. Show me three screenshots. Do not open Fastr.

    What you will see
    Three screenshots side by side and a note on anything that clips.
    Needs your yes
    Publishing. Claude asks what asset and what spec, shows the mock, and waits.
    Does not work yet
    The Fastr preview button does not always follow the selected device. Product pages on the main site block scripts, so a person clears the check.
    FastrFigmaBloomreach (read)AmplienceNetlify
    7.8File management and renamingClaude names, sorts and checks files to one grammar. To point it at a file or a folder, select it in Finder, press Option, Command and C, then paste the path into your message. It plans a rename first, runs a dry run, and keeps an undo script beside it.
    Fig. 7.8171 folders and 720 images renamed in one run, with an undo script.

    A real job

    Product images to 5000 square

    How the margin was made, from the project notes: the script puts the head at 8 percent from the top and the soles at about 92.7 percent, then fills the sides with one flat colour taken from the edge of the photo. Stretching the edge pixels was tried and dropped because it left stripes. No generative fill was used for these files.

    7.8

    File management and renaming

    Claude names, sorts and checks files to one grammar. To point it at a file or a folder, select it in Finder, press Option, Command and C, then paste the path into your message. It plans a rename first, runs a dry run, and keeps an undo script beside it.

    What Claude does here

    • Finds a file anywhere on your Mac by name, type, size or date and tells you where it is. Claude
    • Sorts a messy folder into subfolders by type or by shoot, after you approve the plan. Claude
    • Names shoot frames to one grammar: shoot, look, shot, stage and version. Claude
    • Plans a bulk rename as a table, then writes a rename script and an undo script. On 2 October it renamed 171 folders and 720 images this way. Claude
    • Looks up what a material code means in a local list of 2,333 codes, instead of opening the admin site. Claude
    • 5 more
      • Writes a map and a read-me at each folder level so the next person can pick up cold. Claude
      • Finds shared references in the right folder, which starts with a dash. Claude
      • Opens every image in a folder and measures its real pixel size before anyone claims it is final. Claude
      • Moves work from scratch to a durable folder and states the full path. Claude
      • Renames files by a dedicated rename skill. blocked

    Try this

    Plan a rename of the files in this folder to the shoot grammar. Write a rename script and an undo script. Run only the dry run and show me the first twenty lines.

    What you will see
    A plan table, two scripts, and a log of what would move. Nothing moves.
    Needs your yes
    The real run. Claude also never writes into the external GROWTH folder and never deletes.
    Does not work yet
    There is no single rename skill, only per-project scripts. Cloud-only files can list but not open, so Claude does not bulk-open them.
    Finder pathsOneDriverename scriptswiki skills
    7.9Video editingClaude edits footage you already shot: it probes the clips, transcribes them, plans a cut, adds music and subtitles, and renders a draft. It also reframes, makes email GIFs and writes video prompts.
    Fig. 7.9A real edit: the Danesh ambassador video.

    A real job

    Danesh ambassador video

    A real job from the Organic Social calendar. A person on the team filmed an ambassador video. Claude turned the raw take into a beat sheet to slice by, then a finished vertical cut with music, punch-ins and subtitles. People decide what ships.

    Open the Asana task

    7.9

    Video editing

    Claude edits footage you already shot: it probes the clips, transcribes them, plans a cut, adds music and subtitles, and renders a draft. It also reframes, makes email GIFs and writes video prompts.

    What Claude does here

    • Probes footage, makes contact sheets and transcribes it on your Mac, then asks you to confirm who is speaking. Claude
    • Writes a beat sheet as a web page with a few slice options and running times. Claude
    • Cuts, adds captions, fits music and renders an MP4 plus a phone preview. Claude
    • Turns an approved vertical plate into 16:9 without regenerating, at zero credits. Claude
    • Makes GIFs for email with gifski, with hero files under 1 MB. Claude
    • 2 more
      • Writes video prompts for Seedance: one scene paragraph, then one movement paragraph. Claude
      • Drives After Effects through a script and reads the result from a file. Claude

    Try this

    Probe this clip and give me contact sheets and a transcript. Do not cut anything yet.

    What you will see
    Contact sheets, a transcript with the speakers marked unconfirmed, and a short list of what Claude noticed.
    Needs your yes
    Downloads, music, credits and any posting. Nothing ships without your approval of the cut.
    Does not work yet
    Proven on the Danesh ambassador edit. It has not run yet on a teammate’s Mac, so the first setup is done with Jesse. Video credits are costly, and the content filter flags some gestures.
    ffmpeggifskiAfter EffectsHiggsfield videovideo-edit
    7.10HyperframesVideo editing cuts footage that already exists. Hyperframes makes video that does not exist yet: titles, motion graphics and branded templates written as a web page, so one design can become fifty videos.
    Fig. 7.10A form resolving from coarse to fine, as each frame renders from code.

    7.10

    Hyperframes

    Video editing cuts footage that already exists. Hyperframes makes video that does not exist yet: titles, motion graphics and branded templates written as a web page, so one design can become fifty videos.

    What Claude does here

    • Builds a video as a web page whose timing is written in the page, then renders it frame by frame into an MP4. Claude
    • Renders a list of five products into five branded MP4s from one build script. This ran as a sandbox test, not on a production piece. Claude
    • Animates titles and supers with 24 named text effects and scene transitions, so a title card is a few lines, not an afternoon in a timeline. unverified
    • Drops in ready-made blocks such as grain, glitch and charts from a catalog of about 400, and turns data into moving charts. unverified
    • Checks the composition and takes a still before it renders, so a mistake costs seconds, not a render. unverified
    • 1 more
      • Turns a website or a Remotion project into a video. unverified

    Try this

    Build a six second title card in EB Garamond on a black ground for the Columbus Day offer. Lint it and show me one snapshot. Do not render the final file.

    What you will see
    A small project folder, a clean lint result and one still frame.
    Needs your yes
    Final renders that carry brand elements, and any post. Claude shows a still first.
    Does not work yet
    No finished production video made only in Hyperframes is on record. Use video editing for footage you already shot.
    HyperframesGSAPmedia-usevideo-edit
    7.11Research and the webClaude opens pages in a browser, reads them, pulls out the images and videos you ask for, and hands them to the next step. You decide what to keep.
    Fig. 7.11759 reel frames sorted down to 246 filed keepers, one dot each.

    A real job

    Showroom reference photos

    From the web and video to a usable set. Claude pulled the frames, sorted them, and filed them. Some frames show staff and customers, so check rights before using any of them outside the team.

    7.11

    Research and the web

    Claude opens pages in a browser, reads them, pulls out the images and videos you ask for, and hands them to the next step. You decide what to keep.

    What Claude does here

    • Opens a page in a real browser and reads its text, images and prices. Claude
    • Scans a page and lists every image on it with its size and where it lives. Claude
    • Pulls images off a page into a folder you point at, after you say yes to the download. Claude
    • Downloads a video embedded in a page, such as a social reel, with a tool like yt-dlp. Claude
    • Cuts a video into stills by scene and sorts them into a folder. One run turned 759 frames into 246 filed keepers. Claude
    • 3 more
      • Upscales a pulled image with , then uses it as a reference or uploads it to Higgsfield to make a video. Claude
      • Researches a topic across the web in rounds and files the sourced result as notes. Claude
      • Gets past a site’s press-and-hold check. blocked

    Try this

    Open this page [paste link]. List every image on it with its size and its address. Do not download anything yet.

    What you will see
    A table of images with sizes and addresses, and a note on anything the page blocked.
    Needs your yes
    Every download, and any upload to Higgsfield. Check you have the right to use each pulled image or video before it goes in a reference set, a render or anything we publish. Another person’s work is a reference to learn from. Do not copy or republish it. If you are unsure, ask Jesse.
    Does not work yet
    Some sites block scripts, and the press-and-hold check is yours to clear. Pulled images are references first.
    Browseryt-dlpffmpegupscale-4kHiggsfield

    7.12

    Also in the toolbox

    The same loop runs outside these eleven jobs. A few more things Claude does for Jesse every week.

    • Turns a meeting recording into notes, after you confirm who was speaking. Claude
    • Answers a question from the vault and names the pages it used. Claude
    • Researches a topic on the web in rounds and files the sourced result as notes. Claude
    • Draws a diagram of a system, such as the map this guide is styled on. Claude
    • Writes a performance report from Motion data. Claude
    • Critiques a design for usability, hierarchy and consistency. Claude
    • Rebuilds a one-page morning brief at 7:30 on weekdays. Claude
    • Reads the overnight sessions and proposes edits to its own rules. You adopt them. Claude + you

    Shoot references: build an image from parts

    Reference. Skip until you need it.

    An AI shoot is assembled from small, separate references. Each one carries one kind of information, so you can swap the suit, the room or the pose without redoing the rest of the shot. Change one part at a time.

    Attached as images

    Model sheet: four views of one man's head

    Modelone sheet, four views

    Black shawl-collar dinner jacket, product photoCream trouser, product photoWhite dress shirt, product photoBlack bow tie, product photoWhite pocket square, product photoBlack cap-toe oxford shoes, product photo

    Wardrobeone image per garment

    Room platea clean photo, no people

    Written as words

    Pose

    Crop and framing

    Light and grade

    The scene prompt

    1. 1Scene paragraph, first
    2. 2Face and wardrobe locks, copied exactly
    3. 3Plate line: lends only its surfaces and light
    4. 4Camera and crop, last
    A man in a black dinner jacket, cream trousers and a bow tie stands in a gilded room

    One finished frameBlack Tie set, Look 32

    Fig. 6 · One image, built from partsReal pieces from the Black Tie set. The model is AI-generated. The room tile is drawn as an icon.

    Make your first image, step by step

    This is the way Jesse makes an image. You choose four things: a model, a suit, a room and a pose. Claude writes the prompt, which is the written order that goes to Higgsfield. Claude also finds the model sheet, the suit photo and the room photo in the library and attaches them for you. The pose goes in as words, never as a photo. You say yes, and Higgsfield makes the picture. Then you change one thing at a time until it is right.

    Each grey box below is a message for Claude. Click Copy, paste it into the message box in the Code tab and press Return. Replace each [bracket], and the brackets too, with your own path or name. If Claude asks to read a folder, click Allow. Every image costs credits from one shared team pool, so tell Jesse before your first test. The small ? beside a command is a help icon, so type only the command.

    Step 1

    Collect your poses

    Find your own poses. Pinterest, magazines and your own past work all work. Claude reads each pose and writes it down in words. The photo never goes into the new image, so the person and the clothes in it do not carry over.

    1. In Finder, make a new folder called My first shoot.
    2. Inside it, make a folder called poses.
    3. Find two photos of people standing, sitting or leaning the way you want your model to. Drag web images into poses, or save a phone photo of a magazine page there.
    4. Open the Claude desktop app and click Code. When it asks which folder to work in, choose My first shoot.
    5. In Finder, select the poses folder and press Option, Command and C. This copies the folder’s full address, called a path.
    6. Paste the line below. Select [paste path] with your mouse, press Command and V to put your path over it, then press Return.

    Read the poses

    Look at the images in this folder: [paste path]. For each one, tell me the pose, the crop and where the person sits in the frame. Change nothing.

    You will see

    A short note on each photo. Nothing is made or changed.

    If it is wrong

    If Claude cannot open the folder, check that you pasted the full path and that OneDrive has finished syncing. If a box asks to allow reading, click Allow.

    Step 2

    Pick a model, a suit and a room

    1. Click Copy path on the first row of the shared references folder. Paste the line below and put that path over [paste path].
    2. Read the three lists.
    3. Names alone will not help you choose. In Finder, open the models folder, then Product-refs and its suits folder, then the locations folder, and look at the pictures.
    4. Pick one model, one suit and one room. Write down each folder name exactly. Use folders whose names start with IDC-M, IDC-SUIT or IDC-LOC.
    5. Right-click your three folders and choose Always Keep on This Device. Wait until the cloud icon on each one is gone. Pin only these three, never the whole shared folder.

    List what is there

    Open this folder: [paste path]. List the models, then ten suits, then ten rooms, one line each. Change nothing.

    You will see

    Three short lists. A model folder looks like IDC-M01-Greg, a suit folder like IDC-SUIT-bardwell-stripe-navy and a room folder like IDC-LOC-amber-corridor. Every model is an AI character with a four-view head sheet (the file ending _4angle-head), a full-body image and a written face description. A room folder holds a reference photo, the file called ref-interim, and a text note. Jesse calls a room photo a plate, and it lends the new image its surfaces and light.

    If it is wrong

    If a suit or room is missing, ask Claude to list more. Still missing? Tell Jesse. Do not use a website screenshot.

    Step 3

    Ask for the plan

    1. Paste the line below. Replace each bracket, and the brackets too, with a path or a full folder name, such as IDC-M01-Greg.
    2. Stay in the same chat you used in Step 2. If you start a new chat, paste the shared folder path again at the start of your message.
    3. Claude picks the model head sheet, the suit front photo (and the shoulder photo when fabric detail matters) and the room photo, and lists them in order. A shirt, tie or shoes you choose need their own photos, and Claude lists those too. Your pose photos are never attached. Pin each of those photos the same way. Check the list before you say go. If Claude cannot find a front photo for a suit, ask it to use the legacy file.
    4. Answer Claude’s questions. It may ask about a shirt, a tie and shoes, about shot sizes, or about styling rules. Pick from what it shows, or say you choose.
    5. If Claude offers to start a shoot sheet, say yes. It is a short file called _SHOOT.md, saved in My first shoot, that records your choices.
    6. Read the shot table. A good one names the pose, the crop, the room and the light for each frame.

    Plan one shot

    Read the images in [paste path to poses] with /indochino:pose-dna and /indochino:composition-dna. Plan one shot for each pose with the model [model name], the suit [suit name] and the room [room name]. Show me the shot table and the full prompt. Do not make anything yet.

    You will see

    A table with the pose, the crop and the room for each frame, then the full prompt and the list of attached photos. Nothing is made and no credits are spent. The two commands read each photo and write its pose and framing down in words.

    If it is wrong

    If Claude cannot find the model card or the shared folder, check the shared references folder. If it says it cannot find SS26, tell it the folder is called _shared-refs. If it cannot find a command, quit the Claude app and open it again, because commands load when it starts.

    Step 4

    Read it and fix it

    1. Read the table and the prompt like a proof.
    2. Check five things: the right model, the right suit, the right room, the right number of poses and the right crop.
    3. Say what to change in plain words. Ask why if a choice is unclear.
    4. Say yes only when all five match. This yes approves the plan and spends nothing. Making an image needs a separate go in Step 5.

    Say it like this

    Use the second pose only. Make the crop tighter, from the waist up. Show me the new table.

    You will see

    A new table. Claude changes only what you named.

    If it is wrong

    If the table is not what you meant, say so in plain words. Claude changes the plan, not your files.

    Step 5

    Make one test image

    1. Tell Jesse you are about to make your first test.
    2. Paste the line below and press Return. Claude makes one image at 2K. If Claude asks for permission to use Higgsfield, click Allow.
    3. Wait until Claude shows the image. Do not type another go while you wait.
    4. In Finder, open the saved file from My first shoot.

    Fire one test

    Go. Make one test image at 2K. Save it in this folder: [paste path to My first shoot]. Then show me the image and check my Higgsfield transactions to tell me how many credits that test used.

    You will see

    The image in the chat, a saved file in My first shoot and the credits it used. Claude waits for your yes before every image, including retries. 2K is the house size for tests and 4K is for finals. Say 1K if you want it cheaper. It is a smaller image, so judge the face and the fabric on a 2K test.

    If it is wrong

    If Claude says it cannot reach Higgsfield, go back to the Higgsfield connection. If nothing has appeared after a few minutes, tell Jesse. Do not say go again.

    Step 6

    Look hard, then change one thing

    1. Open the saved image at full size. In Finder, double-click the file.
    2. Put the model sheet (in the models folder) and the suit photo (in Product-refs) beside it.
    3. Check five things: the face matches the model sheet, the suit matches the real product photo, the hands, jacket hems and trouser hems look real, the pose feels natural, and the crop is what you asked for.
    4. Pick the one thing that is most wrong. Change only that part, using the list below.
    The face looks different
    Say: The face does not match the model. Check that the prompt carries the model’s full face description exactly as written, then show me the prompt.
    The suit colour is off
    Ask Claude to compare the image with the real product photo and say what drifted. The real photo is the colour truth.
    The room feels wrong
    Change only the room.
    The pose looks stiff
    Pick a different pose photo and read it again.
    The crop is wrong
    Say what must be out of the frame first, then what must be in it.

    Change one part

    Change only the room. Use [room name] and keep the model, the suit, the pose and the crop the same. Show me the prompt first.

    You will see

    A new prompt that differs in one place. Nothing is made until you say go.

    If it is wrong

    If you cannot tell what is wrong, put the image beside the model sheet and the product photo and tell Claude what looks different.

    Step 7

    Make the rest

    1. Work out the batch cost: the credits the test used, times the number of frames, at the same size. Tell Jesse before you run it.
    2. Ask for every pose as one batch.
    3. Ask for the width, the height and a close crop of hands and hems on every frame.
    4. Ask for 4K versions of only the frames you keep. 4K and any retries cost extra. Claude states the size and the count, then waits for your yes.
    5. Upload the keepers where your Asana task says and update the task yourself. Claude does not.

    Scale it up

    That works. Make the other poses the same way, as one batch. Save them here: [paste path to My first shoot]. Then give me the width and height of every frame and a 100 percent crop of the hands and hems.

    You will see

    A folder of frames, a table of sizes and the close crops. Claude measures every frame, because sizes can differ from what you asked.

    If it is wrong

    If a frame comes back at the wrong size, ask Claude to make it again and measure it.

    Step 8

    Shortcut: change one thing in a finished image

    1. In Finder, select a finished image you like and press Option, Command and C.
    2. Paste the line below and say the one thing to change. Claude reads the image as words and plans a new one.

    Start from a finished image

    Read this image with /indochino:pose-dna and /indochino:composition-dna: [paste path]. Plan a new shot that keeps the pose and the crop and changes only [the one thing]. Show me the shot table and the full prompt. Do not make anything yet.

    You will see

    A plan that keeps the pose and the crop and changes one thing. Nothing is made until you say go. Jesse can find the original prompt for some older images, so ask him if you want the exact first settings.

    If it is wrong

    If the plan changes more than you asked, say change only [the one thing] and ask again.

    Open the shoot references guide: the parts, where the files are, how to scale it

    Six words, in plain English

    Scene prompt
    One written paragraph that describes the whole picture, scene first. Claude writes it.
    Plate
    A clean photo of a room with no people in it.
    Reader
    A command such as that turns a photo into words.
    Grade
    The colour feel of the picture.
    Shot table
    The list of frames Claude plans, with the credit cost, before it fires anything.
    Model card
    A short page for each model, with the written face description to paste.

    The six parts, and where each one lives

    • Model

      Attached as an image

      CarriesThe face and body, as a four-view headshot sheet plus a short written description.

      Lives inmodels/IDC-M##-Name/, with model-card.md

      Read withmodel card

      Why it stays separateA face lifted from the wrong photo drags in the wrong clothes and pose.

    • Wardrobe

      Attached as an image

      CarriesEach garment as its own image: suit, shirt, tie, pocket square, buttons, shoes, watch and belt.

      Lives inProduct-refs/, with suits in suits/IDC-SUIT-name/ as a front and a shoulder shot

      Read with reads the fabric

      Why it stays separateColour comes from the real garment photo. Text alone lets a shirt, shoe or watch drift.

    • Location

      Attached as an image

      CarriesA clean photo of the room with no people in it, called a plate.

      Lives inlocations/IDC-LOC-name/, with ref-plate.png and location.md

      Read with and

      Why it stays separateA real room hands Claude real light. Describing a room in words gets a generic one.

    • Pose

      Written as text

      CarriesHow the body stands, moves and looks, written down from any reference photo.

      Lives inYour own reference photos, saved in a folder you make. Find them on Pinterest, in magazines or in past campaigns.

      Read with

      Why it stays separateA pose photo drags in its own person, clothes and framing, so only its words go in.

    • Composition and crop

      Written as text

      CarriesWhere the subject sits in the frame and how tight the crop is.

      Lives inRead from the reference, kept in your prompt

      Read with

      Why it stays separateCrop words buried mid-prompt are ignored, so the exclusions come first.

    • Light and grade

      Written as text

      CarriesWhere the light lands on the subject and the colour feel of the picture.

      Lives inRead from the reference. The plate adds real light too

      Read with

      Why it stays separateHiggsfield cannot copy a grade from a photo, so the look is written and then checked.

    Swap one part at a time

    New suit, same shoot: change only the wardrobe images.

    New room: change only the plate.

    New face: change only the model sheet.

    Scale it up

    Do one, look at it, then do the rest. The same prompts work for six looks or sixty, because you point Claude at a whole folder instead of attaching files one by one.

    1 · Start with the folder, change nothing

    Read the shoot folder first: [paste path]. Then show me a shot table for the looks we still need: crop, camera angle, pose and light. Do not fire anything.

    2 · Test one, then stop

    Run Look 32 only, at 2K, with the references in this folder: [paste path]. Show me the result and the credit count, then wait.

    3 · Scale it once the test is right

    That works. Run the other looks the same way, as one batch, with every image in this folder as references: [paste path]. Save the results here: [paste path].

    • Select the folder in Finder and press Option, Command and C. Paste that path into your message wherever it says [paste path].
    • Ask for the shot table first. It lists each shot in one row, so you can match any image you like back to its prompt.
    • Claude says the shots, the size and the credits before it spends anything, and waits for your yes. Test at 2K and make finals at 4K, once the direction is locked.
    • Ask for the whole batch at once. Sending shots one at a time costs you a paste every round.
    • Ask Claude to save the prompts next to the renders, so you can see later what produced what.
    • Ask for numbers and 100 percent crops of hands, hems and belts. A small contact sheet cannot show those.

    What to use, and why

    1. One reference, one job

      Each reference carries one kind of information. A single photo that carries everything drags everything in.

    2. Every garment gets its own image

      Attach the suit, shirt, tie, pocket square, buttons, shoes, watch and belt that show in the frame. Text alone lets them drift.

    3. The real garment photo is the colour truth

      A flat swatch can misread the made garment, and an AI render can drift. The real product photograph decides.

    4. The plate lends surfaces and light

      Tell Claude the plate lends only its surfaces and light. Do not list its objects, and do not ask it to keep its framing.

    5. Pose and crop go in as written text

      Read a reference with and and use the words. Never attach the pose photo.

    6. Say what is out of frame first

      A crop instruction buried mid-prompt is ignored. Open with what is out of frame.

    7. Every render waits for your yes

      Claude shows the shot table and the credit count first. Run one cheap test before the batch.

    8. Other people’s photos are for reading

      Use another person’s photo to read pose, light or framing. Keep it out of the prompt as an image, and do not copy it.

    Try this

    Read this reference [paste path] with and . Then write the prompt for the model in [paste path to the model card], wearing the suit in [paste path to the suit folder], in the room in [paste path to the plate]. Show me the shot table and the credit count. Do not fire anything.

    Claude shows the shot table and the credit count, then waits. The pose and composition readers cost nothing, so use them freely.

    From Asana task to delivered asset

    Reference. Skip until you need it.

    This is the path a paid ad request takes. Some parts run today. The full crew is still a design on paper, and Claude stops where people take over. Everyone works in their own Claude on their own Mac, and the always-on iMac is Jesse’s own, so you drive each stage yourself with your own copy of Claude.

    Nine stages

    1. 0Read the ticketAsana connection, read onlyClaude
    2. 1IntakeReads the task, the copy for and off the image, the sizes and anything banned. You check itClaude + you
    3. 2QuestionsClaude asks what the task leaves open, using the interview command, slate command or email brief command, with you answeringClaude + you
    4. 3PlanA written plan you approve before anything is builtdesigned
    5. 4GenerateClaude makes the first options: layouts on a scratch page, image renders, copy drafts or a cut, depending on the job. Renders wait for your yesClaude + you
    6. 5AuditA second Claude runs a check script and looks at the app window with Peekaboo, a window-capture tool that only looks. A reviewer then passes work along but never ships itClaude
    7. 6ReviseYour notes first, then the audit’s fix list, three rounds at mostClaude + you
    8. 7ExportNames like Campaign_Set_Subject_ratio, plus a before and after fencedesigned
    9. 8Hand offYou upload to SharePoint and update Asana. Claude stops here by designYou

    The crew’s last step is a Figma page, a QA report and a folder of exports. People upload to SharePoint and update Asana. Claude stops there.

    How the parts connect

    Reference. Skip until you need it.

    Every job in this guide follows one loop. You hand Claude the task. It draws on what it knows, picks a procedure, operates an app and checks the result against your rules. Then it hands the work back to you.

    1. You hand Claude the task, and hold the final yes. informs
    2. Memory tells Claude what it already knows about the work. informs
    3. Checks hold the work to your rules while it is made. constrains
    4. Skills are the written procedures Claude picks for the job. drives
    5. Apps are what Claude operates: Figma, Photoshop, InDesign, Higgsfield, Asana, Google and Bloomreach. drives
    6. Output is what comes back from the apps. produces
    7. Output goes to you for approval before anything ships. hands off
    8. What was learned goes back into memory. loops back
    informsconstrainsdrivesproduceshands offloops back

    The apps Claude can operate

    Each tile shows what Claude does there and how far it is allowed to go. A two-letter monogram stands in for each company logo, and the frame shows the kind of access.

    Solid: drives the appDashed: reads onlyDouble: spends creditsDotted: partly or not working

    • Drives the app

    • Figma

      Reads frames, builds pages, generates thumbnail sketches and type layouts, takes screenshots.

      drivesClaude

    • Photoshop

      Colour grades, places images, runs Remove and generative fill, shows a preview.

      drivesClaude

    • InDesign

      Builds documents, checks them, and prepares print files for prepress.

      drivesClaude

    • Browser

      Opens any web page in a real Chrome, reads it, pulls images and video, and researches a topic across sites.

      drivesClaude

    • After Effects

      Runs scripts on a project. It cannot paint pixels.

      drivesClaude

    • Fastr

      Builds landing pages through a real browser.

      drives, publish stopsClaude

    • EmailLove

      Stock email parts in Figma. Export is a person’s click.

      drives in FigmaClaude

    • Hyperframes

      Renders video from code. Sandbox runs only so far.

      drivesunverified

    • Netlify

      Hosts the lookbook page. A push deploys it, so Claude asks first.

      deploysClaude

    • Reads, and writes nothing

    • Asana

      Reads tasks, comments and attachments.

      read onlyClaude

    • Motion

      Reads Meta ad performance on Indochino ads: hook rates, spend, what is scaling. It never changes a campaign.

      read onlyClaude

    • Bloomreach

      Reads campaigns, the catalog and email blocks.

      read onlyClaude

    • Google

      Gmail, Calendar and Drive for the account you connect.

      reads and draftsClaude

    • Microsoft 365

      Outlook and Teams, through a browser profile.

      reads, drafts onlyClaude

    • Read means Claude can look at it and cannot change it.

    • Spends credits

    • Higgsfield

      Renders images and video after your yes.

      spends creditsClaude

    • Midjourney

      Explores style and references after your yes. Final renders happen elsewhere.

      spends creditsClaude

    • Every render waits for your yes.

    • Partly working or not working

    • Capture One

      Reads catalogs and grades. Export is run by hand.

      partialClaude + you

    • Lightroom

      The connection timed out on the current macOS.

      not workingblocked

    • Check these before you plan around them.

    Fig. 2.1 · The apps, shown as monogramsAccess shown on each tile

    Read it in one line: you hand Claude the task, Claude drives your apps, checks hold the work to your rules, and you approve what ships. Nothing leaves until you say so.