Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
hiyeshu avatar

Trip Map Builder

hiyeshu/trip-map-builder

  • 206 installs
  • 175 repo stars
  • Updated July 8, 2026
  • hiyeshu/trip-map-builder

Plan a trip, research restaurants via Dianping and Xiaohongshu, then generate an interactive mobile-first Leaflet map page with a timeline and optional Vercel deploy.

About

Runs a Plan-Research-Build pipeline that turns constraints and wishlists into an area-based itinerary, enriches dining with Dianping/Xiaohongshu signals, and generates a Leaflet map page. A user runs it to create a deployable interactive trip map with navigation and reservation links.

  • Single-file Leaflet template with location types, payment chips, and Xiaohongshu links
  • Optional swap to alternative brand design systems from awesome-design-md

Trip Map Builder by the numbers

  • 206 all-time installs (skills.sh)
  • +19 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #1,042 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hiyeshu/trip-map-builder --skill trip-map-builder

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs206
repo stars★ 175
Last updatedJuly 8, 2026
Repositoryhiyeshu/trip-map-builder ↗

What it does

Plan a trip, research restaurants via Dianping and Xiaohongshu, then generate an interactive mobile-first Leaflet map page with a timeline and optional Vercel deploy.

Files

SKILL.mdMarkdownGitHub ↗

Trip Map Builder

Three-phase pipeline: Plan → Research → Build.

The output is a reference itinerary, not a script the traveler must obey. During the trip, weather, current location, fatigue, and hunger can override the original plan.

Shared memory

Before planning or building, read ~/.trip-map-builder/MEMORY.md if it exists. Use it only for durable traveler context:

  • pace preference
  • food and drink preferences
  • budget habits
  • payment and navigation preferences
  • previously generated trip outputs
  • recurring constraints and unresolved follow-ups

If the file does not exist, continue normally. Do not block on memory setup.

Do not store raw screenshots, passport data, booking codes, full chat logs, or other sensitive/private material.

After each completed trip plan, research pass, or map build, update ~/.trip-map-builder/MEMORY.md with only durable facts:

# Trip Map Builder Memory

## Traveler Defaults
- Departure city:
- Pace:
- Food preferences:
- Budget habits:
- Payment preference:
- Navigation preference:
- Language preference:

## Past Trips
| Trip | Dates | Destination | Output | Notes |
|------|-------|-------------|--------|-------|

## Reusable Preferences
-

## Open Threads
-

Phase 1: Plan the itinerary

Read references/trip-planning.md for the full methodology.

Core sequence:

1. Extract hard constraints — dates, flight times, terminals, hotel location 2. Group user's wishlist — city-easy / needs-reservation / far-suburbs / pass-through 3. Cut high-risk items first — too far, holiday-crowded, weather-dependent. Say what was cut and why. 4. Arrange by area — one main area per day, first day light, last day close to airport 5. Fill in meals — daily-area candidates first, 大众点评 + 小红书 signals second, fame last. 6. Add tickets & transport — only critical ones (museum tickets, airport transfer) 7. Write reference doc — conclusion first, then daily plan, weather-sensitive spots, meal areas, and what was cut

Key principles:

  • Not everything the user listed fits. Delete for them.
  • One area per day. One reservation-required spot per day max.
  • Itineraries should be smooth, not packed.
  • The plan gives coordinates for later adjustment; it does not pretend reality will follow the timeline.
  • All user-facing questions follow the 4-beat format: Re-ground → Simplify → Recommend → Options. See references/trip-planning.md § 用户交互 for examples and anti-patterns.

Phase 2: Research via 大众点评 + 小红书

Read references/dianping-research.md for the 大众点评 OpenCLI workflow. Read references/xhs-research.md for the 小红书 OpenCLI + CDP workflow.

For restaurants, use 大众点评 as the main Chinese dining signal for taste, queue risk, value, and obvious traps. Use 小红书 to supplement atmosphere, recent experience, photo-worthiness, and soft warnings. Do not bend a whole day around a famous restaurant unless it is already on the route.

小红书 core sequence:

1. Launch Chrome with --remote-debugging-port=9223 2. Connect via OpenCLI's CDPBridge 3. Navigate to xiaohongshu.com/search_result?keyword=<encoded> (never simulate input box) 4. Intercept POST /api/sns/web/v1/search/notes response 5. Pick top 2-3 notes by relevance, open detail pages 6. Extract via DOM: #detail-title, #detail-desc, .author-container .username 7. Compress to one decision-useful sentence per store, write back to local .md

Filtering rules:

  • Keep: specific store name, address, dish, personal experience, repeated keywords
  • Drop: generic area roundups, reposts, pure emotion, "氛围很好" x3
  • Output: store name + one representative link + 2-3 sentence verdict

Phase 3: Build the map page

1. Copy assets/template.html → index.html 2. Fill HOTEL object and DAYS array with structured data from Phase 1+2 3. Each location needs: name, lat/lng, type, time, desc; optional: budget, detail, pay, xhs, reserve, gmap 4. Fill overviewContent() with trip summary, payment warnings 5. Apply design system — default template uses Apple style, but can switch to any style from awesome-design-md

Location types: food | spot | drink | hotel | transport

Payment chip values: 1 = confirmed yes (green), 0.5 = maybe (orange), omit = not shown

Design system (optional)

Default template uses Apple design system (SF Pro, light theme, frosted glass).

To use a different style, grab a DESIGN.md from awesome-design-md:

# Browse available design systems
# Apple, Vercel, Linear, Stripe, Notion, Airbnb, Nike, Spotify, etc.
curl -O https://raw.githubusercontent.com/VoltAgent/awesome-design-md/main/design-md/<brand>/DESIGN.md

Then adjust template.html's :root CSS variables (colors, fonts, spacing, border-radius) to match the chosen DESIGN.md tokens.

Deploy (optional)

git init && git add . && git commit -m "trip map"
gh repo create REPO --public --source=. --push
# Import from vercel.com/new — auto-deploys on push

Dependencies

ToolPurposeInstall
OpenCLI大众点评 adapter + 小红书调研npm install -g @jackwener/opencli
Chrome/Chromium浏览器 + 远程调试已有
Leaflet.js地图渲染（CDN 引入，无需安装）template.html 内置
gh CLIGitHub 仓库创建（可选）brew install gh

Resources

  • references/trip-planning.md — itinerary planning methodology, input/output templates, selection principles, common pitfalls
  • references/dianping-research.md — 大众点评 OpenCLI search/shop workflow, dining decision signals, writeback format
  • references/xhs-research.md — OpenCLI installation, Chrome CDP setup, 小红书 search workflow, API details, filtering criteria
  • assets/template.html — single-file HTML map template (Leaflet + Apple design system)
  • awesome-design-md — 60+ brand design systems (Apple, Vercel, Stripe, Linear, etc.) for alternative styling

Related skills

mattpocockGrill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kmattpocockGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196kopen.feishu.cnLark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kopen.feishu.cnLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kopen.feishu.cnLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kopen.feishu.cnLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k
Productivity & Planningworkflow
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.