PromptVaultRetire a component without splitting the product
For design-system teams sequencing a component deprecation across design and code.
Works with
- DeepSeek
- Cursor
The prompt149 words · 1 blank
What you fill in
- Deprecation inventory
[component_inventory]ExampleLegacy modal used in 14 flows; replacement dialog lacks stacked-action and mobile variants
How to use it
- 1Open it in PromptVault. Find it in Design, or search for “Retire a component without splitting the product”.
- 2Fill in the blank. deprecation inventory — the only things the prompt cannot know.
- 3Copy and paste it into Cursor. It also works with DeepSeek.
About this prompt
“Retire a component without splitting the product” is a advanced design prompt. For design-system teams sequencing a component deprecation across design and code. It is 149 words long and written to get a usable answer on the first message, in DeepSeek and Cursor or any other chat assistant. Good for: planning, design system, handoff, step by step and automation. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
More design prompts
All 64 in Design
A controlled rollout for a shared Figma libraryFor design-ops leads sequencing migration work across files, teams, and release gates.- Component APIs that designers and engineers can both predictFor design-system practitioners learning to name variants, states, slots, and behaviors.
- Engineering handoff reaches implementation without guessworkFor first-time designers sequencing a handoff from design lock through acceptance.
- Legacy design assets reach one dependable homeFor teams sequencing an asset migration without breaking active project references.
- Localized interfaces checked before release pressure peaksFor product teams scheduling visual language checks across markets and release cadences.
- Dark-mode tokens from a light-theme sourceA production-shaped dark theme preserving semantic aliases and interaction states.