评审设计系统组件需求
拆解组件申请背后的需求,评估复用、无障碍与维护成本,给出处理建议及回复文案。
完整提示词
<context>
Component requests usually describe a solution ("we need a StatusPill") rather than the need behind it ("users must see an order's state at a glance in a dense table"). Many can be met by an existing component, a new variant or prop, or a documented pattern that composes existing parts. Every core component is a permanent cost: design, code on every supported platform, accessibility, documentation, support and future migrations. Good triage separates the need from the proposed solution, checks reuse across teams, and always leaves the requester with a path forward, including "build it locally now, we will consider promoting it once a second team needs it". Saying yes to every loud request bloats the system; saying a bare no sends teams off to build their own.
</context>
<task>
Triage this request.
<request>
{{request}}
</request>
{{#system_inventory}}
<system_inventory>
{{system_inventory}}
</system_inventory>
{{/system_inventory}}
{{#criteria}}
<criteria>
{{criteria}}
</criteria>
{{/criteria}}
1. **Underlying need.** Restate the user problem the request is trying to solve, separately from the proposed component. If the need is unclear, write the questions that would clarify it.
2. **Existing options.** Check the inventory for components or patterns that meet the need as is, with a new variant or prop, or by composition. If no inventory was given, say the check could not be done and what to look for.
3. **Assessment.** Score the request on: reuse (how many products or teams plausibly need it), fit with the system's principles and existing components, accessibility complexity, platform coverage needed, and maintenance cost. Apply the user's criteria if given.
4. **Recommendation.** Choose one: use an existing component, extend an existing component, document a pattern, accept as a new core component (via the contribution process), or keep it local with a promotion path. Give the reason and what would change the decision.
5. **Accessibility check.** If the requested design has an accessibility problem (information only on hover, colour as the only signal, a custom control replacing a native one without need), say so and how the recommendation avoids it.
6. **Reply to requester.** A short, friendly message: what we recommend, why, what they can do today, and what happens next. No jargon.
</task>
<constraints>
- Do not claim the system has components or props that are not in the inventory.
- Never answer with a bare no; every verdict comes with something the team can do now.
- Do not approve a new core component on the strength of one team's deadline alone.
{{> output/uncertainty}}
</constraints>
<output_format>
Markdown with the sections from the contract, in order. Verdict is one line. Assessment as a table (Criterion, Finding, Score low/medium/high). Reply to requester as a quoted block under 150 words.
</output_format>可替换内容
- {{request}}
- {{#system_inventory}}
- {{system_inventory}}
- {{/system_inventory}}
- {{#criteria}}
- {{criteria}}
- {{/criteria}}
- {{> output/uncertainty}}
分类与标签
设计创意、设计系统、组件评审、组件复用、无障碍设计