Actions: Inventory inconsistencies (spacing/type/color/components), identify the operational blocker the system will remove (e.g., slow production, inconsistent UI, customization needs). Choose the first high-leverage slice.
3) Lock logic with blockframes (separate thinking from styling)
3) 用blockframes锁定逻辑（将思考与样式分离）
Inputs: Key flows; current IA; constraints.
Actions: Create or specify “blockframes” (lo-fi, system-aware wireframes). Map each block to intended components and token usage so hi-fi execution becomes faster and more consistent.
Outputs: Blockframe-to-component map (v1).
Checks: A reviewer can validate flow/IA without debating visual details.
4) Define the token model (make the future style changeable)
4) 定义令牌模型（让未来风格可修改）
Inputs: Brand constraints, accessibility targets, desired direction (e.g., depth/texture/motion).
Actions: Define token taxonomy + naming; include elevation/depth and state tokens. If doing a visual refresh, design the token model so style can evolve without rewriting components.
Outputs: Token model + token backlog (v1).
Checks: Tokens support theming and states; accessibility constraints are addressed (contrast, focus, motion).
Actions: Tier components (primitives → composites → patterns). Prioritize by reuse and user impact. Define milestones, owners, and acceptance criteria.
6) Make it easy to use (guardrails for non-experts)
6) 提升易用性（为非专业人士提供防护规则）
Inputs: Target user types; common mistakes; documentation needs.
Actions: Design documentation and component guidelines so they “teach by structure”: sensible defaults, constrained options, examples, do/don’t. Provide starter templates for common layouts.
Outputs: Documentation + enablement plan (v1).
Checks: A non-expert can assemble a consistent screen using templates with minimal training.
Actions: Define decision rights, contribution workflow, review gates, and release cadence. Create a champion/office-hours plan to drive adoption. Run references/CHECKLISTS.md and score with references/RUBRIC.md. Finalize Risks / Open questions / Next steps.
Outputs: Final Design System Operating Pack.
Checks: Ownership is unambiguous; adoption plan exists; quality bar is explicit and repeatable.