Filmsquare HelpDocs

3.0 The departments3.5 Wardrobe

Wardrobe

How costumes work in Filmsquare (a look per cast member per scene) and what signing off Wardrobe means.

Updated 3 min read.md

On this page
  1. What this step produces
  2. Who works on it
  3. How AI prepares it
  4. Signing it off
  5. What makes it go stale
  6. What it costs
  7. With your own Claude

Wardrobe dresses the cast, under Cast & sets → Costumes. In Filmsquare a costume is a look: a name and a picture on a cast member, tied to the scenes they wear it in. Anna in her work coat is one look, Anna in the evening dress is another.

The Wardrobe department of an episode: the cast on the left, a cast member's looks and the scenes each one covers (open the full screenshot)
Fig. 1 The Wardrobe department of an episode: the cast on the left, a cast member's looks and the scenes each one covers

What this step produces #

Signed-off looks per episode: for each cast member, which look they wear in which scene. A cast member wears one look per scene. With no cast yet, the page reads "No cast yet".

Who works on it #

On a film crew, a costume designer does the work and the director signs it off. Those are crew jobs, not Filmsquare roles: what a person may do comes from their workspace role. A producer can assign the step, or one cast member to one person, next to that cast member's name.

How AI prepares it #

  1. Open Cast & sets → Costumes and choose a cast member on the left.
  2. Choose New look. A look needs a Name and a Picture, an image you upload. Choose Add look.
  3. Under the pictures, each look has a row across the scenes of the episode. Click a cell to tie the look to that scene, click again to take it off. Tying a scene takes another look of that cast member off it.
  4. Shots in those scenes use the picture as the cast member's reference. A look has its own @handle, such as @anna-raincoat, which stands for the cast member wearing it.

Edit renames a look or gives it a new picture; Archive takes it out. Both need the maker role or higher.

A change to the cast member itself is still a new version. To keep a shot on an earlier version, pin it on that shot through the API or your own Claude (updateShotElement).

See Elements, versions and @handles.

Signing it off #

Signing off Wardrobe says: the cast wears these costumes. Wardrobe locks the finals by default. The Trailer template skips Wardrobe.

What makes it go stale #

A new or changed look, or a change in the scenes it covers, makes Wardrobe Changed after sign-off. So does a new version (v2 and up) of a cast member, in every episode that uses it, and Casting with it. The change flows on to the Animatic, the Draft and the Final. Takes made with a look go stale when it changes or is taken off that scene.

Costumes are where continuity slips most often. A continuity check compares clothes, colours, accessories, wear and dirt between the shots of a scene. See Continuity.

What it costs #

A look costs nothing in credits: its picture is one you upload. A reference sheet of a cast member is a still: 1.66 credits · €0.08 on Seedream 5.0 Pro, or 2.94 credits · €0.15 on Nano Banana 2 where the server offers it. Routing picks the model with the lowest cost per accepted take unless you choose one. See Credits and what things cost.

With your own Claude #

The tools are under With Claude on this page. Looks (createElementLook, setLookScene), forking a version and rendering a sheet go through find_actions and run_action.

With Claude

MCP

Your own Claude does this over MCP, in your name and with your role:

  • work_on_stepPrompt

    A working method: prepares one department step of an episode for sign-off, with the cost first.

    Ask: Use the Filmsquare work_on_step prompt for Wardrobe on episode 2.

  • view_media

    Looks at a still, keyframe or take; video comes back as its poster plus a download link.

    Ask: Show me the picked still of shot 3 and tell me if it matches its references.

  • upload_file

    Adds a file you have as a new take on a shot or scene, or as a production asset (10 MB at most).

    Ask: Upload this reference photo to the assets of the production.

  • get_continuity

    Lays an episode's picked shots side by side, with the element versions each one uses.

    Ask: Lay out the picks of scene S2 for a continuity check.

  • report_continuity

    Records the continuity check you did; each mismatch becomes a note on the shot's pick.

    Ask: Check continuity in scene S2 and report the mismatches you find.

  • request_signoff

    Asks the signers of a department step to sign off; they get a notification.

    Ask: Ask the signers of Wardrobe on episode 2 to sign off, with a note on what changed.

  • sign_off

    Records your decision on a step: signed off or changes requested. Only when you ask it to decide.

    Ask: Sign off Wardrobe on episode 2 for me.

  • find_actions

    Searches everything the API can do and returns the matching actions with their inputs.

    Ask: Find the action that changes a step's sign-off rule.

  • run_action

    Runs one action found with find_actions, as you, with your role and rights.

    Ask: Pick the second take of shot 5 on episode 2.

Connect Claude 5.1

This page as Markdown: /docs/departments/wardrobe.md