Track props and costume-relevant objects

Maintain project-wide props, connect them to story use, and generate visual references without duplicating facts.

Props are project-level entities

Props are shared across episodes and appear in a canvas and list. Use one canonical record for a recurring object, then describe variations or states clearly. Avoid creating a new prop each time the same object changes hands.

Laper's current module is a prop system rather than a complete wardrobe department. Costume-relevant objects and visual notes can be tracked where useful, but do not assume a hidden costume breakdown workflow beyond the visible fields and project views.

Make props dramatic and producible

Record why the object matters, who controls it, visible states, continuity requirements, and any production constraint. “Old key” is weak; “brass archive key, tooth three filed flat, carried by Mara until scene 18” is actionable.

Use AI and generated images deliberately

The assistant can read and edit prop entities when you have write access. Ask it to reuse existing props and name the episode or scene where the change belongs. AI prop images are reference assets; verify scale, material, continuity, and rights before production.

Audit continuity

Compare props with screenplay scenes and beats. Check entrances, transfers, damage, and payoffs. Because props are shared across the project, a deletion or rename can affect later episodes. Preserve a history checkpoint before broad cleanup and fix story usage in the screenplay rather than relying on the prop card alone.