Motion & Video · Web & Digital
A Tokyo creative director had Claude Code draw a cut sheet in Figma, then directed his studio's reel and a playable site through nine versions of it
Takuma Hashimoto of FunTech used a Figma cut sheet as the contract with Claude Code, writing feedback per cut until the film and site stopped looking like AI.
Done withCCClaude CodeFFigmaBBlenderGIGPT image generationTthree.jsASAdobe Stock
The studio's own reel and promotional site (self-promotion); no client. Won an FWA award.
WHAT THEY DID
Takuma Hashimoto, a designer and creative director at Tokyo studio FunTech, made the studio's 2026 reel, a roughly 50-second film rendered from three.js code, and a ten-scene interactive site built from the same scenes, directing Claude Code (Opus 5.5) through a cut sheet it drew in Figma.
STEP BY STEP
- Tested the viral one-line showreel prompt, then decided to direct the agent scene by scene.
- Claude Code drew cut-sheet and music-brief templates in Figma via MCP.
- Rough scene memos; the agent proposed cuts; feedback column per round, v1 to v9.
- Depth estimation from member photos turned into material statues; Adobe Stock textures and GPT-generated neon signs added.
- UI rebuilt after the first options were judged too AI-like; fine-tuning via side-by-side options in Figma and one pull request per fix.
HOW IT WENT
He says it took about a week from the first test to the finished film and site (about three days for the FunTech film and site alone), with nine versions of the film. The site is live, and the project won an FWA award on 19 Oct 2026.
Reported results: About a week from first test to finished film and site (about three days for the FunTech film and site alone); nine film versions; FWA award 19 Oct 2026.
WORTH KNOWING
A dated, first-person production log in which the designer keeps every judgement call: the cut sheet is the brief, each round of feedback is a column on it, and the agent's first UI ideas were thrown out for looking too much like AI.
TRY IT
- Ask the agent to build a cut-sheet template in Figma (one row per cut, start and end frames) and give feedback there.
- If you can't fill a blank sheet, write one rough line per scene and let the agent propose the cuts, then react.
- When the UI matches the visuals too closely, tell the agent where to go quiet: loud scenes, minimal but detailed UI.
Rates the entry, not the tool.
Source: Takuma Hashimoto (@tkm_hmng8) · X (Article)Open as a page
- Work done: not stated in the source (Not stated as a calendar date. He says the work took about a week from the first test; the finished film was first posted on X on 30 Sep 2026.)
- Source published: Oct 6, 2026
- On 4TC: added Nov 20, 2026 · checked Nov 20, 2026
About this source
Type: Agency example · Firsthand report · Demonstrated workflow
- 制作工程ぜんぶ見せます(前編) (The whole production process, part 1)
Takuma Hashimoto (@tkm_hmng8) · X (Article) · Published Oct 6, 2026 (X Article posted 6 Oct 2026; in Japanese.) · Checked Nov 20, 2026
Primary: the designer's own first-person production log of his studio's self-promotional reel and site. paid_partnership false; no sponsorship or affiliate disclosure.
Access: Japanese; quotes and paraphrases are 4TC translations. - 制作工程ぜんぶ見せます(後編) (The whole production process, part 2)
Takuma Hashimoto (@tkm_hmng8) · X (Article) · Published Oct 6, 2026 (X Article posted 6 Oct 2026; in Japanese.) · Checked Nov 20, 2026
Primary: part 2 of the same log (UI, fine-tuning, lessons, released character model). paid_partnership false.
Access: Japanese; quotes and paraphrases are 4TC translations. - How we turned a viral one-prompt motion test into Experience FunTech Creativity — with a Figma cut sheet, nine versions of a film, and a UI that had to stop looking like AI.
Takuma Hashimoto, FunTech Inc. · The FWA (Insight) · Published Oct 24, 2026 (Byline 24 Oct 2026; award dated 19 Oct 2026.) · Checked Nov 20, 2026
Primary, English: a first-person write-up submitted by FunTech on the FWA site after the award (award-platform editorial, self-promotion).
Access: open - EXPERIENCE FUNTECH CREATIVITY
FunTech Inc. · FunTech · Publication date not stated (Live site; no publication date on the page.) · Checked Nov 20, 2026
The finished artefact (the studio's own promotional site).
Access: Best on desktop with sound, per the creator. - Opus5.5の動画制作、工夫次第でここまでいけます (film post)
Takuma Hashimoto (@tkm_hmng8) · X · Published Sep 30, 2026 (Film first posted 30 Sep 2026; in Japanese.) · Checked Nov 20, 2026
Primary: the finished film as first posted by the creator.
Access: Japanese.
Source check: Researched from the public page; not yet re-checked by an editor. Nobody at 4TC has tested this.
Claims and where they come from
- He tried the viral one-line prompt asking Claude Opus 5.5 for a 15-second motion designer showreel, liked the result, then noticed that everyone's reel looked the same: black background, bold type, particles and glitches. (reported) [1][3]
- Claude Code drew a cut-sheet template and a music-brief template straight into Figma through Figma's MCP: one row per cut, a start frame and an end frame, the motion in words, and a column for what the visitor does on the site. (reported) [1][3]
- Faced with a blank cut sheet, he wrote rough one-line memos per scene and asked the agent to propose the cuts and the music brief, then reacted; each round of feedback went into a column on the sheet, through nine versions. (reported) [1][3]
- A depth-estimation test on one photo per team member came back clean enough that he swapped the planned particle scene for a museum of statues, each member in a different material; he says MoGe-2, Depth Anything 3 and BiRefNet were chosen because their licences allow commercial use. (reported) [1][3]
- To make code-drawn images look less CG, the agent listed suitable Adobe Stock textures (with ID, resolution and use) and he downloaded them: 32 in all, such as glass cracks, riso grain and lens dust. (reported) [1][3]
- The 36 neon signs were made with GPT image generation from prompts the agent wrote, including the shop names. (reported) [1][3]
- The agent's first three UI options were judged 'too AI' when he asked colleagues; he concluded the UI matched the loud scenes too closely, and told the agent that the scenes are loud, so the UI should be minimal but obsessively detailed. (reported) [2][3]
- When a strange pattern appeared around the character's outline, the agent confidently 'fixed' the floor reflection; the real cause was a lens-dust texture lit by bloom. (reported) [1][3]
- Near the end, every fix became its own pull request that he checked and merged. (reported) [2][3]
- The film went from 60 seconds at 144 BPM in version 1 to 49.66 seconds at 174 BPM in the final. (reported) [1][3]
- Building every scene once during the opening terminal screen, so shaders compile before the visit, cut desktop loading from about 19 seconds to about 6, he says. (reported) [3]
4TC interpretation
Our reading, not something the source says.
He started from a viral one-line prompt and noticed every result looked the same. Instead of prompting again, he made the agent's work reviewable in Figma: start and end frames per cut, a feedback column, and side-by-side options whenever a fix needed his call.
Designer impact
One-prompt output converges on the same look; he calls matching the UI too closely to the visuals a tell of AI design.
- Decide where the design should go quiet and write that rule down for the agent.
- Ask colleagues for a gut check on whether it looks AI-made.
Alleged [3]
The agent can report a fix that doesn't address the real cause.
- Check fixes against before-and-after frames rather than the agent's explanation.
Alleged [2]
Asking another model to strip information made the UI too minimal to tell visitors what to do next.
- Compare several options side by side and choose yourself.
Established = documented by primary sources or the company’s own statements. Disputed = contested with evidence on both sides. Alleged = reported, not established.
Votes rate whether this entry was useful. They are not an endorsement of the tool, and don’t mean voters agree with the company’s practices.
Report an issue or correction
Share your own experience
4TC does not endorse a tool unless an explicit 4TC endorsement is shown.