Which token naming scheme survives the next redesign?
For design-system teams selecting a token architecture with migration consequences exposed.
Works with
- Cursor
The prompt244 words · 5 blanks
What you fill in
- First naming scheme
[naming_option_a]Examplesemantic role then state - Second naming scheme
[naming_option_b]Examplecomponent then property then state - Current token sample
[existing_tokens]Examplecolor.blue.500, text.primary, button.primary.hover, surface.raised - Supported surfaces
[product_surfaces]ExampleWeb, iOS, Android, and two white-label themes - Migration tolerance
[migration_constraint]ExampleAliases allowed for one release
How to use it
- 1Open it in PromptVault. Find it in Design, or search for “Which token naming scheme survives the next redesign?”.
- 2Fill in the 5 blanks. first naming scheme, second naming scheme, current token sample, supported surfaces and migration tolerance — the only things the prompt cannot know.
- 3Copy and paste it into Cursor. That is the tool it is written for.
About this prompt
“Which token naming scheme survives the next redesign?” is a advanced design prompt. For design-system teams selecting a token architecture with migration consequences exposed. It is 244 words long and written to get a usable answer on the first message, in Cursor or any other chat assistant. Good for: design system, decision making, deep dive, comparison and handoff. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
