CLAUDE LABJP
FORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as OctoberFORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as October
Articles/Claude.ai
Claude.ai/2026-05-13Beginner

What Changed After I Started Using Claude to Refine My English Artist Statements

An artist with 17 international art awards shares how using Claude to refine English artist statements changed the experience of applying to global open calls — and how to keep your own voice in the process.

claude-ai15artistenglish-writingpersonal-experienceopen-callsstatement

When writing English submission materials for international open calls, the gap between translation and genuine expression becomes most obvious at the core of your work.

My practice explores "the structure of collective psychology and cognitive worlds, rooted in a distinctly Japanese form of quiet reverence." Translating this into English with DeepL or Google Translate yields something like "the structure of collective psychology and cognitive worlds" — technically accurate, but stripped of the weight I intended. After receiving recognition across multiple international art awards including the IAA, I had a lingering sense that the quality of my English submissions was a variable I hadn't fully controlled.

Using Claude changed that, in a quiet but practical way.

Why Direct Translation Falls Short

An artist statement is not a description of a work — it's a declaration of why you make it. Jurors read hundreds to thousands of submissions a year, most written by professional translators or native English-speaking artists. In that context, translated English that carries Japanese sentence structure can be read — before its content — as a signal about the writer's relationship to the language.

Translation accuracy and prose quality are different things. Even when meaning is conveyed precisely, the sense of "what this person cares about" comes through in rhythm and structure. Now that machine translation is excellent at accuracy, the remaining gap lives in that register.

The First Prompt I Sent

I gave Claude the original Japanese statement alongside the English translation I'd been using. My instructions were specific:

Please bring this English text closer to the way an English-speaking artist
would write it — away from "translated English."

However, please preserve the nuance of the following terms as you adjust them:

- "prayer" (祈り): closer to quiet contemplation or reverence than prayer
- "tracing the structure of collective psychology": trace or map out,
  rather than explore

If any meaning shifts, please flag the change explicitly.

What came back was faithful to the original in meaning but noticeably different in rhythm. Claude avoided "prayer" entirely and suggested "ancestral reverence" — with an explanation of why it made that substitution. Having the "why" meant I could decide whether to accept it. That judgment stayed mine.

The key was not asking Claude to "rewrite everything." Being specific about which words I needed to protect raised the quality of what came back.

Handing Claude the Untranslatable

"A distinctly Japanese form of reverence" tends to be read by non-Japanese jurors as religious ritual — but what I mean is quieter and more secular. Something closer to the atmosphere of a Shinto shrine courtyard: a disposition, not a practice.

What I discovered in conversation with Claude is that handing over the difficulty of expressing something yields more useful results than asking for a solution.

I want to express "prayer" (祈り) in English without conveying religious overtones.
I'm after the feeling of quiet reverence in a Japanese shrine or temple —
a kind of contemplative attitude rather than devotion.
What options exist, and what are the nuance differences between them?

Claude returned a breakdown of candidates:

  • reverence: Respect bordering on awe. Usable without religious context. Close to the Japanese 畏敬 (ikei).
  • devotion: Dedication. Works in both religious and secular contexts. More active than 信心 (shinjin).
  • contemplative awareness: Introspective attention. Works well in spiritual-adjacent contexts.
  • ancestral connection: Implies relationship to predecessors. Useful when Japanese concepts of death and lineage are present.

I chose "quiet reverence." It isn't a direct translation of anything, but it holds what I meant. Getting a map of options and then deciding for myself — that's the mode that works for this kind of work.

Adjusting Tone for Each Open Call

International open calls vary considerably by type. The culture of evaluation differs between gallery submissions, competitions, and residency applications.

Gallery calls tend to weight conceptual depth. Competitions look for alignment between visual impact and statement. Residency panels want to know why this place with specificity.

For the same work, passing Claude the context of each destination produces more tailored variations of a base statement:

Please adjust this statement for a submission to a contemporary gallery in New York.
This gallery emphasizes conceptual work and social themes.
My understanding is that the panel values context around "why I am exploring this
question now" over descriptions of the work itself.

With that framing, what came back felt written for that reader rather than adapted from a template. Having a solid base statement once means subsequent variations are relatively fast to generate.

What Didn't Work

A few early mistakes are worth noting.

The most common is handing Claude an open-ended request: "Write me a good artist statement." This produces well-formed generic text that looks like an artist statement but doesn't sound like me. It reads as if no one in particular wrote it.

The other failure mode was submitting only the English text without the Japanese original and asking Claude to "improve it." Without access to the underlying intent, Claude modifies what it sees — and tracking what changed and why becomes difficult. Sending both the Japanese source and the English translation in parallel consistently produces better feedback.

Keeping Your Own Voice

One thing I've been careful about: Claude returns readable English, but readability and individual voice sometimes conflict. My writing style is intentionally fragmented and repetitive in places — and Claude would occasionally smooth that away as if it were error.

The fragmented style in this statement is intentional.
Please do not improve the flow.
Limit your edits to vocabulary accuracy and cultural nuance.

After adding that constraint upfront, revisions came back with my voice intact. Claude is a finishing tool. The writing is mine. Keeping that boundary clear is what makes it sustainable to use over time.

My grandfathers on both sides of my family were temple carpenters — the kind of craftsmen who built structures meant to last generations. The habit of working with your hands and taking final responsibility for the result runs through how I approach making anything, including language. Delegating the judgment entirely would remove the thing that makes the statement worth reading.

Where to Start

Write first in Japanese. Then tell Claude: "Please bring this closer to the way an English-speaking artist would write it, not translated English." And be specific about which words you need to protect.

That sequence is the foundation of how I use it. The same approach works in any situation where you need to communicate your concepts and intentions in English. The experience of finding — slowly, through conversation — that something previously only sayable in Japanese becomes sayable in English too has been more practically useful than I expected.

For a broader look at how I use Claude in creative and development work, see Claude as a Creative Partner — What I Noticed After Putting It in My Studio. And if you're interested in the collaborative writing process more broadly, Writing with Claude: Drafting, Revising, and Finding Your Voice Together covers that ground.

I hope this is useful to anyone preparing materials for international open calls.

Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • Copy-paste ready implementation code
  • New advanced guides published daily
  • $5/mo or $10 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

Claude.ai2026-05-16
How I Handle 30+ App Store Reviews Monthly Using Claude — A Solo Developer's Workflow
Managing Beautiful HD Wallpapers and other apps with 50 million total downloads means dealing with reviews in 8 languages. Here's the Claude-powered workflow I built to handle 30–40 replies per session without triggering App Store throttling.
Claude.ai2026-05-05
Claude Keeps Making the Same Mistake — Why Corrections Don't Stick and How to Fix It
Why Claude repeats mistakes even after correction, and how to make your instructions stick permanently using Projects, custom prompts, and smarter conversation design.
Claude.ai2026-05-01
When Claude won't send your message: a diagnostic order that always finds the cause
When the send button does nothing, the spinner runs forever, or your message vanishes — here's the order I work through to find the real cause within five minutes.
📚RECOMMENDED BOOKS
Build a Large Language Model (From Scratch)
Sebastian Raschka
LLM Dev
Prompt Engineering for LLMs
Berryman & Ziegler
Prompting
AI Engineering
Chip Huyen
AI Eng
* Contains affiliate links
See all →