Files
AOS/skills/design/design-templates/social-card-map/SKILL.md
T
Z User e45b68bb8b feat: IMAP mail sync with thread-to-contact matching (PRD §6.1)
Real IMAP connection via imapflow library:
- Connects to IMAP server (IMAPFlow, TLS on port 993)
- Fetches recent messages (configurable limit, default 20)
- Extracts: from, fromEmail, subject, date, snippet (200 chars)
- Thread-to-contact matching (PRD §6.1):
  1. Match sender email against persons table
  2. If no person match, extract domain and match against company.website
  3. Returns matchedCompany + matchedPerson for each email
- Audit-logged (action: crm.mailsync:imap)
- Zod validated (host, port, user, password, folder, limit)
- 502 on IMAP connection failure with detail
- 400 on validation failure

Tested: invalid creds → 502 'IMAP connection failed', missing host → 400
2026-10-27 22:50:50 +00:00

2.0 KiB
Executable File

name, description, visibility, mode, carrier, scenario, pattern_source, source_priority, triggers, related_patterns
name description visibility mode carrier scenario pattern_source source_priority triggers related_patterns
social-card-map 地图 / 行程 / 路线主导的社交卡 — 路线 + 3 个停靠点 / 邻里地图 + 推荐标签 / 一日行程 + 简化路径 / 地点卡 + 迷你地图 + 旅行笔记 / 两区两路线对比。地理必须激进简化,只标必要地点,给清晰路径层级,配 city/date/duration/walking-driving 上下文。触发:"做个旅行路线卡 / 行程图卡 / 邻里地图卡 / 周末散步路线 / 城市指南"。NOT 真实地图数据虚构,NOT 地图当背景装饰。 public template fixed-image social-content pattern.html skill-first
做个旅行路线卡
行程图卡
邻里地图卡
周末散步路线
城市指南卡
地图打卡卡
social-card-editorial

Social Card Map / Travel Template

Use when location, route, itinerary, distance, neighborhood, or place relationship is central to the card.

Core Rule

A map card must clarify spatial relationships. Do not add a map shape only as decoration.

Structure Options

  • route map + 3 stops
  • neighborhood map + recommendation labels
  • day itinerary + simple path
  • place card + mini map + travel note
  • comparison: two areas / two routes

Must Do

  • Simplify geography aggressively.
  • Label only necessary places.
  • Use a clear route/path hierarchy.
  • Include context: city, date, duration, walking/driving/transit if relevant.

Avoid

  • Map details too dense for phone viewing.
  • Fake exact map data when none is provided.
  • Decorative map backgrounds unrelated to content.

Pattern Source Rule

Read this SKILL.md first. Do not read pattern.html by default.

Read pattern.html only when you need concrete layout rhythm, spatial relationships, or interaction/annotation behavior that this markdown cannot fully specify. When read, extract patterns only; do not copy DOM, CSS classes, exact spacing, placeholder copy, or styling wholesale.