AgentSkillsCN

tr-dashboard-patch

根据 patch.md 规范，实现 TR 移动大屏的 UI/UX。在构建或修改故事标题、地图/时间轴/详情布局、双击碰撞 UX、视图模式（实时/历史/审批/对比）、约束徽章，或任何由 patch.md 定义的视觉与交互规则时使用。同时严格遵循 SSOT（option_c.json）规范，确保单一视图流程（Where→When/What→Evidence）的顺畅运行。

SKILL.md
--- frontmatter
name: tr-dashboard-patch
description: Implements TR 이동 대시보드 UI/UX from patch.md spec. Use when building or modifying Story Header, Map/Timeline/Detail layout, 2-click collision UX, View modes (Live/History/Approval/Compare), constraint badges, or any patch.md-defined visual/interaction rules. Enforces SSOT(option_c.json) and single-view flow (Where→When/What→Evidence).
metadata:
  ssot: patch.md
  data_ssot: option_c.json
  related:
    - tr-dashboard-ssot-guard
    - tr-dashboard-pipeline

TR Dashboard Patch

Implements TR 이동 대시보드 UI/UX from patch.md (SSOT). Goal: "TR 하나 = 하나의 이동 스토리" in one screen.

SSOT

  • •Layout/UX/Visual rules: patch.md (absolute priority)
  • •Data schema: option_c.json (Activity SSOT)
  • •Project rules: AGENTS.md

Quick Checklist (patch.md §2, §4)

AreaRulepatch.md
Story HeaderTR 선택 시 3초 내: WHERE / WHEN/WHAT / EVIDENCE§2.1
2-click Collision1클릭: 배지→요약 / 2클릭: Why 패널→Root cause+Evidence§4.2
Map colorsPlanned=회색, In progress=파랑, Completed=초록, Blocked=빨강, Delayed=주황§4.1
Constraint badges[W] [PTW] [CERT] [LNK] [BRG] [RES]§4.2
Collision badges[COL] [COL-LOC] [COL-DEP]§4.2
View ModeLive/History/Approval/Compare + 권한 표§2.2

Layout (patch.md §2.1)

code
Story Header → Map | Timeline | Detail
                Map↔Timeline highlight | History/Evidence

Read order: Story Header → Map (Where) → Gantt (When/What) → Detail + History/Evidence (Evidence)

2-Click Collision UX (Required)

  1. •1-click: Timeline collision badge → Collision summary popover
  2. •2-click: Detail "Why" panel → Root cause chain + Evidence/log jump

Collision object must include: root_cause_code, related resources/activities, suggested_actions[].

Plan ↔ Actual Display (patch.md §5.1)

ConditionDisplay
No actual.startPlan bar solid
actual.start exists, no actual.finishPlan + Actual overlay (in progress)
actual.finish existsActual complete + Plan deviation (±)
History modeActual primary, Plan dashed overlay

View Mode Permissions (patch.md §2.2, §5.4)

ModeEditReflow ApplyEvidenceExport
LiveRole-basedLimited (approval)YesYes
HistoryNoNoNo (read)Yes
ApprovalNoNoView onlyYes
CompareNo (overlay only)NoView onlyYes

Reflow (patch.md §3.3, §B)

  • •Preview → topological + constraint + resource adjustment
  • •Apply (permission required) → option_c.json Plan update + History log
  • •Freeze: actual_start/actual_end exists → timestamps immutable

Do Not

  • •Introduce layout/UX that conflicts with patch.md
  • •Add SoT that bypasses option_c.json
  • •Collision UX that requires >2 clicks to reach root cause
  • •Delete or modify History (append-only)

References