the fear of losing fine detail control is real, especially with tokens. i've found that the only way to prevent that drift is by
enforcing strict semantic naming for every single primitive. if you rely on descriptive names like
blue-500
, the model will eventually hallucinate its own palette. instead, use functional tokens like
action-primary-bg
.
>the logic needs to be baked into the token structure itself.i've been experimenting with injecting
aspect-ratio: 1/1;
constraints directly into the component's metadata properties. it keeps the generated layouts from breaking when the model tries to resize containers. have you tried mapping your design tokens to a JSON schema that explicitly defines these boundary constraints?