规划设计系统视觉刷新发布
梳理视觉改版的系统层级、产品准备度和发布顺序,输出质量检查、沟通与回滚方案。
完整提示词
<context>
A visual refresh is where a design system pays for itself or exposes its gaps. Changes that live entirely in semantic tokens ship in one release; anything hard-coded, overridden or built outside the system has to be found and fixed by hand, and that is where refreshes stall. Different kinds of change carry different risk: a new colour mostly risks contrast failures, while a new typeface changes line heights, text widths and truncation, and a new radius or spacing value moves layouts. Experienced teams ship the new look as a switchable theme so old and new can coexist, measure how much of each product is token-driven before promising a date, re-baseline visual regression tests on purpose rather than accepting every diff, and plan for the surfaces that lag: native apps tied to store releases, transactional emails, generated PDFs and third-party embeds.
</context>
<task>
Plan the rollout of this visual refresh.
<refresh>
{{refresh}}
</refresh>
<products>
{{products}}
</products>
{{#constraints}}
<constraints_from_user>
{{constraints}}
</constraints_from_user>
{{/constraints}}
1. **Change inventory.** For each change, say which layer it touches (primitive tokens, semantic tokens, component internals, assets such as icons and illustrations, fonts) and its risk type (contrast, layout shift, text metrics, recognisability). Flag any change that cannot be expressed through tokens.
2. **Readiness per product.** From the products list, estimate how token-driven each product is and what must happen before it can take the refresh (upgrade to a recent system version, remove hard-coded styles, migrate off overrides). Where readiness is unknown, name the audit that would measure it.
3. **Rollout strategy.** Recommend how old and new coexist: a new theme selected by a flag or attribute, a new major version, or a direct switch, and explain the choice. Cover fonts (loading, fallbacks, licence for every platform) and assets.
4. **Sequencing.** Order: system foundations, core components, then products by readiness and visibility. Separate the internal readiness date from any public launch date, and say what can ship dark (built but switched off) before launch.
5. **Quality checks.** Contrast for every text and UI pair in every theme, text truncation and wrapping with the new font in long and translated strings, layout checks at key breakpoints, a deliberate review of visual regression diffs, and screens outside the system (emails, PDFs, error pages, app store assets).
6. **Communication.** What product teams need to know and do, by when, and where to raise problems.
7. **Rollback.** How to switch back per product if something fails after launch, and what cannot be rolled back (store releases, sent emails).
8. If the refresh description lacks values the plan depends on (for example no new colour values), list them as open questions instead of guessing.
</task>
<constraints>
- Do not invent colour values, font names, contrast ratios or product readiness figures; compute contrast only from values given and mark estimates.
- Do not promise that the whole estate switches on one day unless the readiness evidence supports it.
- Font licensing is a legal question; flag it for checking rather than asserting what a licence allows.
{{> output/uncertainty}}
</constraints>
<output_format>
Markdown with the sections from the contract, in order. Change inventory and sequencing as tables. Quality checks as a checklist. End with Open questions.
</output_format>可替换内容
- {{refresh}}
- {{products}}
- {{#constraints}}
- {{constraints}}
- {{/constraints}}
- {{> output/uncertainty}}
分类与标签
设计创意、设计系统、视觉改版、产品发布、视觉回归