Life Radar
Generate an action-first digest, not a raw data dump.
If the user asks from a specific role perspective (CEO / manager / employee), read references/modes.md and adapt prioritization/output accordingly.
Output format
Always output in this structure:
- 1. Must-do (today) — max 3 items
- Should-do (soon) — max 5 items
- Nice-to-have — max 3 items
- Suggested next actions — 1-line commands the user can say next
Each item must include:
- - What happened
- Why it matters
- Deadline/time window (or “unspecified”)
Priority rules
Classify with this order:
- Payment due / account risk / security alert
- Meeting in <2h
- Time-sensitive message requiring response today
- Meeting or task in 24-72h
- Follow-up pending from important contact
- Logistics prep (travel, weather-impact, documents)
- Low urgency updates
- Optional optimization tasks
If uncertain, downgrade priority and mark uncertainty explicitly.
Source collection flow
Collect only what is available in current environment; skip unavailable sources without failing.
- 1. Calendar events (today + tomorrow)
- Recent urgent messages (SMS/iMessage/email/DM)
- Billing or financial notifications
- Weather impact for planned outings
- Existing tasks/notes (if connected)
Time-window defaults
- - If user asks "today": prioritize 0-24h window
- If user asks "this week": prioritize 7-day window, still keep Must-do today-centric
- If user asks without a window: default to today + next 72h
Safety and quality
- - Redact secrets, tokens, and full account numbers.
- Avoid hallucinating dates or amounts; mark as unknown when missing.
- Prefer fewer high-confidence items over many noisy items.
- If no meaningful items, return: “Today looks clear. No urgent actions detected.”
Trigger phrases
Treat these as strong triggers:
- - “今天有什么要处理”
- “给我每日行动清单”
- “帮我做个优先级摘要”
- “扫一下我今天的事情”
- “daily action digest”
生活雷达
生成一份以行动为先的摘要，而非原始数据堆砌。
如果用户从特定角色视角（CEO/经理/员工）提问，请阅读 references/modes.md 并根据优先级/输出进行调整。
输出格式
始终按以下结构输出：
- 1. 必须做（今日） — 最多3项
- 应该做（近期） — 最多5项
- 锦上添花 — 最多3项
- 建议下一步行动 — 用户可说的单行指令
每项必须包含：
- - 发生了什么
- 为什么重要
- 截止时间/时间窗口（或“未指定”）
优先级规则
按此顺序分类：
- 付款到期/账户风险/安全警报
- 2小时内会议
- 需今日回复的时效性消息
- 24-72小时内的会议或任务
- 重要联系人待跟进事项
- 后勤准备（出行、天气影响、文件）
- 低优先级更新
- 可选优化任务
如不确定，降低优先级并明确标注不确定性。
信息来源收集流程
仅收集当前环境中可用的信息；跳过不可用来源，不报错。
- 1. 日历事件（今日+明日）
- 近期紧急消息（短信/iMessage/邮件/私信）
- 账单或财务通知
- 计划外出的天气影响
- 现有任务/笔记（如已连接）
时间窗口默认值
- - 如果用户问“今天”：优先处理0-24小时窗口
- 如果用户问“这周”：优先处理7天窗口，仍以今日必须做为中心
- 如果用户未指定窗口：默认今日+未来72小时
安全与质量
- - 隐去机密信息、令牌和完整账号。
- 避免虚构日期或金额；缺失时标注为未知。
- 宁少而精，勿多而杂。
- 如无有意义事项，返回：“今天很清闲。未检测到紧急行动。”
触发短语
以下视为强触发：
- - “今天有什么要处理”
- “给我每日行动清单”
- “帮我做个优先级摘要”
- “扫一下我今天的事情”
- “daily action digest”
