Map-Based UI

# Map-Based UI## UsageUse this DESIGN.md as a reusable design brief for an AI coding agent. Apply it when building a new page, restyling an existing interface, or keeping multiple screens visually consistent.## Design IntentYou are implementing an interface using the **Map-Based UI** design language. 以地图、位置点、筛选和详情抽屉为核心，适合出行、本地生活、物流和资产管理。Treat predictability, native conventions, accessibility, and component consistency as the main design material.## Aliases- 地图界面- location UI## Category- 平台与系统## Target Platforms- 移动端- PC 端## Summary以地图、位置点、筛选和详情抽屉为核心，适合出行、本地生活、物流和资产管理。## Visual DNA- 地图底图- 位置标记- 抽屉详情- 空间筛选## Best Use Cases- 出行 App- 本地生活- 物流追踪- 门店管理## Avoid When空间位置不是核心决策依据。## Anatomy地图做上下文，列表和抽屉做决策；移动端优先用底部抽屉，PC 端可用侧栏。## Color SystemUse a Seed → Map → Semantic → Alias token architecture. Components must consume named tokens instead of hard-coded colors.### Reference Palette- **reference-1** `#ecfeff`- **reference-2** `#ffffff`- **reference-3** `#0f766e`- **reference-4** `#2563eb`- **reference-5** `#111827`### Seed Tokens- **colorBgBase** `#ecfeff` - 页面基础背景.- **colorBgContainer** `#e4f6f7` - 卡片、面板与容器.- **colorFillSecondary** `#daecee` - 次级填充与弱状态.- **colorPrimary** `#2563eb` - 品牌主操作与选中态.- **colorTextBase** `#111827` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#e9effd`- **primary-2** `#cfddfb`- **primary-3** `#b1c7f8`- **primary-4** `#8eaef5`- **primary-5** `#628ff1`- **primary-6** `#2563eb`- **primary-7** `#235ad3`- **primary-8** `#2051bc`- **primary-9** `#1e48a4`- **primary-10** `#1b3e89`### Neutral Scale- **neutral-1** `#ffffff`- **neutral-2** `#f5f6f6`- **neutral-3** `#ecedee`- **neutral-4** `#d9dadc`- **neutral-5** `#bcbec3`- **neutral-6** `#9b9ea4`- **neutral-7** `#757982`- **neutral-8** `#545963`- **neutral-9** `#323845`- **neutral-10** `#111827`### Semantic Tokens- **colorSuccess** `#0f766e` - 成功、在线、已完成.- **colorSuccessBg** `#e2efee` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#faefe1` - 警告状态浅背景.- **colorError** `#dc2626` - 错误、危险、阻断.- **colorErrorBg** `#fce9e9` - 错误状态浅背景.- **colorInfo** `#2563eb` - 信息、链接、进行中.- **colorInfoBg** `#e5ecfd` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#e8fafb` - 应用整体画布.- **colorBgElevated** `#e8f7f8` - 弹层、浮层与菜单.- **colorBgSpotlight** `#323845` - Tooltip 与强提示.- **colorBorder** `#d9dadc` - 控件与容器边框.- **colorBorderSecondary** `#ecedee` - 轻分隔线.- **colorText** `#111827` - 一级文本.- **colorTextSecondary** `#57626c` - 二级文本.- **colorTextTertiary** `#7f8b93` - 辅助说明.- **colorTextDisabled** `#a2b0b6` - 禁用文本.- **colorPrimaryHover** `#628ff1` - 主操作 Hover.- **colorPrimaryActive** `#235ad3` - 主操作 Active.- **colorPrimaryBorder** `#8eaef5` - 主色边框.- **colorPrimaryBg** `#e9effd` - 主色浅背景.- **colorLink** `#2563eb` - 链接与可跳转文本.- **colorFocus** `#8eaef5` - 键盘焦点环.- **colorMask** `#0c111c` - Modal 遮罩基础色.Color rules:- Use the palette as design tokens, not random decorative swatches.- Keep primary text and primary actions at accessible contrast.- Use primary-1 through primary-10 for interaction states instead of inventing new brand colors.- Use semantic tokens consistently for success, warning, error, and info; pair color with iconography or text.- Map component styles to Alias Tokens so theme changes do not require component-level color edits.## Typography- Use a modern system sans-serif stack by default; only introduce a custom font when the brand direction requires it.- Headings should be confident but not ornamental; body text must remain readable across mobile and desktop.- Keep labels short, high-contrast, and aligned to the component structure.## Layout And Spacing- Use an 8px spacing base; reserve 4px for micro-gaps and 32px+ for major layout separation.- Keep cards, panels, controls, and lists dimensionally stable across responsive breakpoints.- On mobile, reduce column count before reducing legibility.- Recommended radius: 16-32px radius for major surfaces; use pill shapes only where they improve touch targets or softness.- Elevation and shadow: Use environment-tinted outer shadows and backdrop blur for elevation. Avoid closed white perimeter borders and full inset highlights that make glass look plastic; add a low-contrast same-color edge only when adjacent layers cannot separate. Contrast must come from text and component state, not blur alone.## Component Rules- Components should reinforce the primary information structure rather than introduce a separate decorative style.- Primary actions must be visually obvious and reachable; secondary actions should be quieter but still discoverable.- Cards need a clear title, supporting text or metric, state, and one obvious next action when action is expected.- Forms and filters should use familiar controls, stable dimensions, clear labels, and visible focus states.- Empty, loading, error, and success states must use the same visual language, not generic placeholders.## Interaction And Motion- Use slow, soft transitions for surface changes, highlights, and overlays.- Avoid constant background motion behind readable text.- Respect reduced-motion preferences and provide a static equivalent.## Implementation Recipe1. Start with the real user workflow and page structure; do not make a generic landing page unless explicitly requested.2. Establish layout zones first: navigation, content, controls, feedback, and primary action.3. Apply the color tokens to semantic roles: canvas, surface, text, border, accent, danger, and success.4. Build reusable components that express this style: buttons, cards, inputs, tabs, filters, modals, empty states, and status badges.5. Verify mobile and desktop breakpoints before adding decorative polish.6. Check that the final screen still communicates 地图底图, 位置标记, 抽屉详情 without relying on a single color or effect.## Quality Checklist- The screen is immediately recognizable as **Map-Based UI**, not a generic Tailwind layout.- The design uses surface, spacing, typography, and component shape together; it does not rely only on colors.- Primary actions and navigation are clear on both mobile and desktop.- Text is readable, controls are stable, and content does not overlap or shift unexpectedly.- Empty, loading, hover, focus, selected, disabled, success, and error states are styled in the same language.- The implementation avoids the known failure mode: 空间位置不是核心决策依据。## Anti-Patterns- Do not paste this palette onto an unrelated layout and call it finished.- Do not overuse decorative effects where the user needs to read, compare, or act quickly.- Do not mix this style with unrelated visual languages unless the product explicitly requires a hybrid.- Do not hide important state behind low contrast, blur, tiny text, or animation.## Keywords- map- location- mobile- pc- drawer## Agent Prompt SnippetImplement the UI in the **Map-Based UI** design language. Prioritize 地图底图, 位置标记, 抽屉详情. Use the color roles, typography guidance, spacing rules, component rules, and anti-patterns from this DESIGN.md as hard constraints. The result should feel purpose-built for 出行 App, 本地生活, 物流追踪, while avoiding: 空间位置不是核心决策依据。