feat: proactive map visualization + travel planning skill - #51
Merged
Conversation
Problems fixed: 1. AI never calls static_map unless explicitly asked → added PROACTIVELY hint to static_map description 2. Trip plans cluster in one area → added district-based exploration hints to explore_area and plan_route descriptions 3. No travel planning methodology → new references/travel-planning.md with anti-patterns, time budgets, correct flow Changes: - static_map: "PROACTIVELY call after explore_area, plan_route, etc." - explore_area: "call multiple times with district names, not city name" - plan_route: "geographic arc per day, call static_map after" - New: references/travel-planning.md (complete methodology) - Recipe 1 rewritten: district-first, always-visualize approach - SKILL.md: added travel-planning.md to reference table Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…very
Replaces AI-knowledge-dependent district approach with tool-driven flow:
1. search_places("top attractions in {city}") → naturally diverse anchors
2. Cluster anchors by proximity → assign to days as geographic arcs
3. explore_area around each anchor → find supporting restaurants/cafes
4. plan_route per day → static_map per day
Verified: search_places("top attractions in Kyoto") returns points spanning
8km×10.7km across Fushimi/Higashiyama/Kinkaku-ji/Arashiyama — natural
geographic diversity without needing pre-knowledge of city districts.
Also: static_map description now says PROACTIVELY call after other tools.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Search Along Route (new tool): - Uses Google Places searchText API with searchAlongRouteParameters - Internally: directions(A→B) → get polyline → searchText along polyline - Results ranked by minimal detour time, not proximity - Tested: Fushimi Inari→Kiyomizu-dera finds 5 along-route restaurants Tool description improvements: - static_map: PROACTIVELY call after search/route tools - explore_area: use district names not city name - plan_route: geographic arc per day Travel planning methodology (references/travel-planning.md): - Tool-driven geographic spread via search_places anchors - 6-layer decision model from research - Anti-pattern table + time budget guidelines - Search Along Route as core filling mechanism All 9 files synced (16 → 17 tools). 132 smoke test assertions, 0 failures. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6 reference files forming a comprehensive knowledge package: New files: - architecture.md — system architecture, transport modes, tool registration, code map - google-maps-api-guide.md — API endpoints, pricing, coverage, common gotchas - geo-domain-knowledge.md — GIS fundamentals, coordinates, spatial search, Japan context - decisions.md — 10 ADRs with context and rationale Updated files: - travel-planning.md — complete 6-layer model with Search Along Route - tools-api.md — Recipe 1 rewritten with search_along_route, added tool docs - SKILL.md — expanded reference table (6 files, 3 categories) Reading this skill package gives full capability to maintain, develop, and make informed decisions about this project. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Agent Skill (skills/google-maps/) — how to USE the tools:
- SKILL.md, tools-api.md, travel-planning.md
Project Docs Skill (skills/project-docs/) — how to DEVELOP/MAINTAIN:
- SKILL.md, architecture.md, google-maps-api-guide.md,
geo-domain-knowledge.md, decisions.md (10 ADRs)
Separation ensures the agent skill stays focused on tool usage
(published to skill registries) while project knowledge lives
in its own skill for developer onboarding.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two problems fixed:
1. AI doesn't proactively generate maps
static_mapdescription now says "PROACTIVELY call after explore_area, plan_route, search_nearby, or directions"explore_areaandplan_routedescriptions end with "After results, call static_map to visualize"2. Trip plans cluster in one area
references/travel-planning.md— complete methodology:explore_areadescription: "call multiple times with district names, not city name"plan_routedescription: "geographic arc per day"Test plan
npm run buildpasses🤖 Generated with Claude Code