Design tokens in the prompt, or a file the agent reads each time?
EP
El picked up Gan@draftbedraggled · Design ops
Our change-summary agent needs to know the token names. Pasting the whole list into the instructions works until someone renames a token and forgets the prompt.
Has anyone moved to having the agent read the current token file on every run? Worried about cost and about it getting lost in a 900-line file.
6 REPLIESHS
Hana Sato@sprintloam · Growth product manager
Read the file, but pre-filter it to the tokens the change touches. You get correctness without the 900 lines.
OR
Oscar Ruiz@larkspurgrid · Web designer
File, read each time. We tried pasting the tokens into the prompt and the agent started quoting old ones from memory a week after we changed them.
MD
Marcus Dell@tallowcanvas · Art director
File, and the agent has to name the token it used in the output. If it says 'brand blue' instead of a token name, it gets sent back.
IH
Ingrid Haas@veloursketch · Illustrator
Illustrator's view: the same rule works for a palette. Give it the swatch file and make it name the swatches it used.
TL
Tomas Lind@harvestclip · Video producer
Motion side here, same problem with easing curves. We generate a small summary file nightly and the agent reads that.
EP
El picked up Gan@draftbedraggled · Design ops
Went with the nightly summary. Renames show up the next morning instead of three weeks later.