--- name: ev-road-trip-a4-map description: > Create a compact, colorful, print-ready A4 EV road-trip route map from a user-provided start and destination. The map must be route-dominant, show the start at the bottom and destination at the top, use a wide diagonal road, mark visible checkpoints with flags, identify left/right side of the road relative to travel direction, prioritize same-side charging/food/hotel stops, and include only concise practical travel information. version: 1.0 --- # EV Road Trip A4 Map Skill ## Purpose Use this skill whenever the user wants a **single-page A4 EV road-trip pamphlet/map** that is useful while driving. The result is not a normal itinerary and not a text-heavy travel report. It should look like a **visual highway route card** that a traveler can print, save on a phone, or quickly glance at during a trip. The main priorities are: 1. **Route visibility** 2. **Driving direction** 3. **Checkpoint visibility** 4. **EV charging reliability** 5. **Same-side stopping convenience** 6. **Compact hotel/food/scenic options** 7. **A4 print readability** --- # 1. Core User Preferences These are the default visual and route preferences unless the user explicitly overrides them. ## 1.1 Page format - Use **A4 portrait**. - Preferred aspect ratio: approximately **1 : 1.414**. - The **map must dominate the page**. - Avoid wasting vertical space on a large title or footer. - Keep the top information strip and bottom quick-tip strip **small and compact**. - Use nearly the full page for the road, checkpoints, and scenery. ### HARD RULE — no side text column Do **not** build a tall vertical panel of text, trip details, or a checkpoint table down one side of the page (as a sidebar). This is the single most common failure. The map — road + scenery + checkpoint cards — must occupy **the full width of the page**. All stop information lives in small cards attached to the road (§5), spread on **both** sides of the diagonal. The full checkpoint list / distance table does **not** go on the poster. It is delivered as the **text source-of-truth block in the chat reply** (§27A), never as a painted sidebar that steals map space. ## 1.2 Route orientation Always place: - **START at the bottom** - **DESTINATION at the top** The traveler visually moves **upward through the page** from origin to destination. Do not place the start at the top unless the user explicitly asks for it. ## 1.3 Road layout — HARD RULE The road is the primary visual object, and **its diagonal sweep is non-negotiable.** It MUST: - be **wide** and visually stronger than the surrounding scenery - run on a **strong diagonal** across the page — never a straight, centered, vertical spine - travel corner-to-corner: **bottom-left → top-right** (or the mirrored bottom-right → top-left) using a broad natural S-curve - use the diagonal specifically **so that checkpoint cards can sit on both the left and the right** of the road and the whole page fills up - stretch from near one bottom corner to near the opposite top corner - approximately reflect the real geographic progression of the route - show major turns / highway transitions, but not every small bend ### Why the diagonal matters A vertical road down the middle leaves the left and right thirds empty, which forces text into a sidebar — exactly what we must avoid. A diagonal road uses the page corners, opens balanced space on both sides for cards, and lets the map dominate. Treat a vertical or near-vertical road as a **defect to reject and regenerate** (see §23). Preferred composition: **bottom-left → center → top-right** or the mirrored equivalent if the real route naturally requires it. ## 1.4 Travel direction overlay Add a subtle, semi-transparent direction cue. Examples: - `Overall direction: South-East` - `Overall direction: North / North-East` - a small compass rose - a transparent arrow following the overall journey The direction indicator should be visible but should never compete with the route. --- # 2. Required Inputs Try to obtain or infer the following: - Starting location - Destination - Departure time - EV model - Battery capacity - Starting SOC - Preferred charging strategy - Whether the user wants hotels / food / scenic stops - Any route preference Accepted start/destination formats: - Google Maps link - coordinates - address - landmark - hotel - city Example: ```text Start: https://maps.app.goo.gl/... Destination: 9°57'29.5"N 78°07'54.3"E Departure: 4:30 AM Vehicle: Mahindra XEV 9e 79 kWh Starting SOC: 95% ``` If a route link can be resolved, use the resolved location instead of guessing from the link text. --- # 3. Route Research Workflow Before designing the pamphlet, determine the actual trip corridor. ## Step 1 — Resolve origin and destination Resolve: - exact start point - exact destination point Then determine: - road distance - major highway(s) - primary city sequence - meaningful junctions - major highway changes ## Step 2 — Build the route skeleton Do not overload the pamphlet with every town. Create only the useful route skeleton. Checkpoint candidates: - start - point where the main highway is joined - major highway change - major junction - large city - strategic EV charging zone - final charging decision point - destination For a long highway drive, approximately **7–12 total checkpoints** is usually ideal. ## Step 3 — Calculate cumulative distance Distances shown on the map should be **cumulative from the starting point**. Example: ```text Start 0 km Join main highway 25 km City A 95 km City B 210 km Final charger 435 km Destination 455 km ``` Use `~` or the word `Approx.` if exact route distance cannot be verified. Never present rough distances as precision navigation data. ## Step 4 — Verify every on-map fact BEFORE plotting (mandatory) Verification comes before artwork. Using the tools available (web search, Google Maps / Search, the user's route screenshot, Street View), confirm the real, best-available: - **chargers** — primary + backup (operator, power, connector, guns, hours, recent evidence of operation) - **hotels** — actual, well-reviewed hotels near the route (real name + rating + proximity), not placeholders or famous-but-irrelevant names - **food stops** — real, verifiable restaurants / known stops - **road side & U-turns** — LEFT/RIGHT, same/opposite, and U-turn distances from real map evidence (§6, §6A, §6B) - **nearby landmarks** — see Step 5 Only after this verification pass do you plot the map. If a specific item cannot be verified after a genuine attempt, mark only that item unverified (§6B) — do not invent it, and do not skip the attempt. ## Step 5 — Keep geography and landmarks real - Plot checkpoints in the **correct geographic order and relative position** for the real route; the road shape should approximate the real corridor. - You may show a **nearby notable place / landmark** at each checkpoint (as the reference example does — e.g. the Krishnagiri fort/hill near Krishnagiri). Every named landmark must be **real and genuinely near that checkpoint**, verified by search. If unsure, omit it. Never invent a temple, fort, hill, beach, or monument for decoration. - Illustration style may be artistic, but **named places and their locations must be factually correct**. The real map wins over a nicer-looking layout. --- # 4. Highway Simplification Rules The visual should simplify navigation intelligently. ## Show prominently - primary national highway - important highway switch - bypass / major junction if it changes how the traveler proceeds - first major road transition after leaving the city ## Do not show - every service road - every flyover - every city turn - every small local road - excessive turn-by-turn navigation The infographic is a **highway overview**, not a replacement for live navigation. If most of the journey stays on one highway, say so clearly. Example: ```text Mostly NH44 after Bengaluru ``` Use small highway shields on the road itself. --- # 5. Checkpoint Design Every important checkpoint must be visibly attached to the road. Preferred checkpoint style: - bright circular marker directly on the road - short **orange connector** - small **orange flag** - compact label box Do not place checkpoint text floating far away without a visual connection to the road. ## Minimum checkpoint information A normal checkpoint should contain only: ```text CITY / STOP Approx. cumulative km LEFT / RIGHT ``` A strategic stop may additionally include: ```text charger food hotel special note ``` Keep the copy short. --- # 6. LEFT / RIGHT Side-of-Road Logic This is important. It is the rule most often broken, so read it carefully. For each optional stop, determine whether it is on the: - **LEFT** - **RIGHT** relative to the **actual direction of travel**. Do not use left/right merely for graphic layout. The label must describe the real side of the route where practical. ## 6.0 Side is a property of the road, NOT of the page `LEFT` / `RIGHT` and `same side` / `opposite side` describe the **real road relative to the direction of travel**. They have **nothing to do with where the label is drawn on the page**. A checkpoint label may be placed on either side of the page purely for layout reasons. That placement must **never** change its side value. ### Two independent facts These are two separate questions and must be answered independently: 1. **Which side of the road is the stop on?** → `LEFT` or `RIGHT` (relative to travel heading). 2. **Can the traveler enter it without crossing to the opposite carriageway?** → `same side` or `opposite side`. For left-hand-traffic countries (India, UK, etc.): the carriageway the traveler is already on is the **left** carriageway in their direction of travel, so a `LEFT` stop is normally `same side`, and a `RIGHT` stop normally requires a crossover → `opposite side`. > **If the trip is in a right-hand-traffic country (US, most of Europe, etc.), invert > this: a `RIGHT` stop is normally `same side` and a `LEFT` stop is `opposite side`.** But do **not** apply this mechanically — divided highways, service roads, dedicated slip-lanes, and nearby interchanges can make a nominally-opposite stop reachable without a U-turn, and vice versa. Verify from map evidence; the heading rule is only the default. ### Worked micro-example (heading south, left-hand traffic) ```text Stop A — fuel/charge plaza on the LEFT of the southbound road → LEFT • same side (enter directly, no U-turn) Stop B — restaurant on the RIGHT, reachable via a slip road 0.4 km ahead → RIGHT • opposite side (U-turn / crossover 0.4 km) Stop C — charger on the RIGHT, but a service lane connects it to your carriageway → RIGHT • same side (no U-turn — RIGHT does NOT always mean opposite) ``` Notice `RIGHT` appears as both `same side` and `opposite side`. The side-of-road and the same/opposite status are decided by geometry and verified map evidence — never by the label's position on the page. ### Anti-rule (do NOT do this) - Do **not** correlate page side with road side. It is normal and expected for several `same side` stops to be drawn on the **right** of the page, and `opposite side` stops on the **left**. - Do **not** attach a U-turn marker to a stop just because its label sits on the right of the page. A U-turn marker may appear **only** on a stop verified as `opposite side` (see §6A). - Do **not** alternate `same side` / `opposite side` to make the graphic look balanced. If the side cannot be verified from map evidence, write `SIDE NOT VERIFIED` and do not show a U-turn for it. ## Same-side preference Prefer stops that are on the **same side of the carriageway as the traveler**. For India, remember traffic is left-hand traffic. The goal is to minimize: - U-turns - median crossings - backtracking - unsafe highway crossings - unnecessary detours When two similarly good charging options exist, prefer the one that is easier to enter and exit while traveling in the intended direction. Optional badge: ```text LEFT • same side ``` or ```text RIGHT • opposite side ``` (An `opposite side` stop additionally shows a U-turn marker and verified U-turn distance — see §6A.) If the side cannot be verified reliably, do **not invent it**. Use: ```text SIDE NOT VERIFIED ``` instead. --- # 7. EV Charger Selection Rules Do not fill the map with every charger. The map should show the **best practical options**. Research should favor: 1. DC fast charging 2. suitable connector for the user's vehicle 3. high charging power 4. recent evidence that the location exists and is operational 5. 24×7 access where possible 6. multiple charging guns 7. food/restroom availability 8. easy highway access 9. low detour 10. same-side access 11. backup chargers nearby For each selected charger, try to confirm: - network/operator - charger power - connector - number of usable DC guns - hours - restaurant/restroom - hotel availability - detour from highway - recent review/operational confidence - LEFT/RIGHT side of travel ## Charger label format Keep map text concise. Good: ```text ZEON • 2×120 kW Food + restroom ``` Avoid: ```text This location contains two CCS2 DC charging connectors with a maximum charging power of... ``` Move detailed facts to a small side note only if essential. --- # 8. EV Strategy Logic Use the user's: - EV model - battery size - starting SOC - expected highway range - destination distance to decide whether early charging is necessary. General principle: - do not force an early charge if the car can comfortably reach a later strategic charging zone - maintain a sensible reserve - use a final decision point before the destination Recommended map wording: ```text Preferred charge: [late-route charger] Fallback: [earlier reliable charger] ``` For a high-SOC departure, use: ```text Skip early charging if SOC is healthy ``` Do not promise an exact arrival SOC unless consumption assumptions are explicitly modeled. --- # 9. Hotel Selection Only show hotels that genuinely help the road trip. Prefer: - directly at a charger - within about **1 mile / 1.6 km** - easy highway access - strong rating, ideally around **4.5★ or better** - useful for rest, breakfast, or overnight stop Compact label example: ```text Radisson Blu ~1 km • 4.5★ ``` Avoid listing hotels merely because they are famous. They should support the route. --- # 10. Food Stop Selection Show food stops when they improve the charging stop. Prefer: - restaurant attached to charger - famous local food very close to route - clean restrooms - breakfast availability for early departures - reliable chain / known stop - minimal detour Compact examples: ```text Breakfast + charge ``` ```text Food + restroom ``` ```text RK Bakers / Subbanna ``` --- # 11. Scenic Stops Scenic points are optional. Only add them when: - they are directly on the route, OR - they are very close to a selected food/charging/hotel stop Do not add a scenic stop if it requires a meaningful diversion only for sightseeing. Good use: ```text FAST CHARGE + hill viewpoint nearby ``` Bad use: ```text Detour 25 km for scenic view ``` The map is first a practical travel tool. --- # 12. Visual Hierarchy The viewer should understand the map in approximately this order: 1. Start 2. Road 3. Destination 4. Highway 5. Checkpoints 6. LEFT / RIGHT side 7. Charger / hotel / food 8. Scenic detail 9. Strategy note The road should never disappear behind text. --- # 13. Preferred Color System Avoid using the same color for multiple primary functions. Recommended palette: ## Route / highway Use: - deep teal - cyan-blue - turquoise - blue-green gradient Do **not** use the same green as the start marker. Example visual role: ```text Route = teal / cyan-blue ``` ## Start Use: ```text amber / warm orange ``` or green only if the route is not green. ## Destination Use: ```text red ``` ## Checkpoint flag Use: ```text orange ``` ## Text panels / side guides Use: ```text blue / navy ``` ## Charging Use: ```text green ``` ## Food Use: ```text orange ``` ## Hotel Use: ```text blue / indigo ``` ## Scenic point Use: ```text purple ``` Use subtle gradients and shadows, not flat oversaturation everywhere. --- # 14. Road Styling The road should look like a highway, not a thin route trace. Preferred styling: - thick road body - subtle blue/teal gradient - soft outer shadow - white dashed lane marking - highway shields placed directly on road - gentle realistic curvature - enough width to place checkpoint markers visibly The road should be one of the widest graphical elements on the page. --- # 15. Label Styling Use compact cards. Each stop label can contain: ```text LEFT SALEM 210 km Hotel • Charge • Food ``` or: ```text RIGHT DINDIGUL 383 km 2×120 kW • Decision point ``` ## Typography priority 1. city / checkpoint 2. LEFT / RIGHT 3. km 4. utility note 5. hotel/charger detail Do not use paragraphs. --- # 16. Page Composition Recommended A4 composition: ```text ┌──────────────────────────────────────┐ │ compact title + EV info │ │ │ │ START at bottom │ │ ╲ │ │ ╲ wide diagonal route │ │ ╲ │ │ labels ↔ checkpoints ↔ labels │ │ ╲ │ │ ╲ │ │ DESTINATION at top │ │ │ │ small legend / subtle compass │ │ compact strategy strip │ └──────────────────────────────────────┘ ``` Actual road should generally run: ```text BOTTOM → TOP ``` with diagonal movement across the page. --- # 17. Header Rules Keep header small. Include only: ```text [Origin] to [Destination] – EV Route Map Start [time] • [EV model] • Starting SOC [x%] ``` Also place a small **verification-mode chip** in the header or footer so the reader knows how trustworthy the sides are: ```text Sides verified from Google Maps ``` or, when they are not: ```text Sides unverified — confirm live ``` Do not use a large decorative banner that consumes valuable map space. --- # 18. Footer Rules Footer must also be compact. Preferred content: ```text Trip strategy: Skip early charge • Preferred: Ayyankottai • Fallback: Dindigul ``` It should normally use less than ~7–9% of the page height. --- # 19. Direction / Compass Rules Calculate the broad direction between origin and destination. Possible labels: - North - North-East - East - South-East - South - South-West - West - North-West Display as: ```text Overall direction: South / South-East ``` or as a translucent arrow. The direction is an orientation aid only. --- # 20. Information Density The map should feel rich but not text-heavy. Use: - icons - flags - km badges - highway shields - LEFT/RIGHT badges - short phrases Avoid: - paragraphs - long explanations - large legends - repeated information - giant strategy boxes --- # 21. Accuracy Rules Never invent: - charger power - charger operational status - road-side direction - hotel rating - detour distance - route highway - cumulative km When uncertain: ```text Approx. ``` or: ```text Verify live before departure ``` A live navigation app remains the authority for real-time: - closures - traffic - temporary diversions - charger availability - road works --- # 22. Pre-Generation Research Checklist Before generating the artwork, verify: - [ ] origin resolved - [ ] destination resolved - [ ] main route identified - [ ] main highway(s) identified - [ ] cumulative checkpoint distances calculated - [ ] EV specs noted - [ ] starting SOC noted - [ ] strategic charger(s) selected - [ ] charger power verified - [ ] backup charger selected - [ ] LEFT/RIGHT side verified where possible - [ ] same-side stops prioritized - [ ] hotel rating verified - [ ] detour kept small - [ ] scenic stop only added if convenient --- # 23. Visual QA Checklist Before accepting the final pamphlet, inspect the image. Reject/regenerate if: - [ ] start is not at the bottom - [ ] destination is not at the top - [ ] **the road runs straight / vertical / down the center instead of a strong corner-to-corner diagonal** (hard fail — see §1.3) - [ ] **there is a tall text/detail/table column down one side of the page** (hard fail — see §1.1) - [ ] the map does not fill the full width of the page - [ ] road is too thin - [ ] road is not visually dominant - [ ] route is not diagonal enough - [ ] checkpoint cards are not spread across both sides of the road - [ ] header is too large - [ ] footer is too large - [ ] road and start marker use nearly identical colors - [ ] checkpoint flags are hard to see - [ ] LEFT/RIGHT badges are unclear - [ ] LEFT/RIGHT or same/opposite appears to track page placement instead of travel direction - [ ] a U-turn marker is shown on a same-side stop - [ ] every stop is marked "SIDE NOT VERIFIED" (means sides were never checked — go verify, see §6B) - [ ] text overlaps the road - [ ] too much text is present - [ ] important km labels are unreadable - [ ] map has large unused blank areas - [ ] charger/hotel icons dominate more than the route - [ ] route sequence is geographically backwards - [ ] origin/destination are reversed --- # 24. Preferred Output Structure The final artifact should normally contain: ### Top ```text Bangalore to Madurai – EV Route Map Start 4:30 AM • XEV 9e 79 kWh • SOC 95% ``` ### Map Large diagonal route with checkpoint flags. ### Checkpoint callouts Alternating around road. ### Small legend Icons only. ### Subtle direction indicator Compass / arrow. ### Bottom One-line EV strategy. --- # 25. Example — Bangalore to Madurai Example source data: ```text Origin: Sri Sri Manor, Bengaluru Destination: 9°57'29.5"N 78°07'54.3"E Departure: 4:30 AM Vehicle: Mahindra XEV 9e 79 kWh Starting SOC: 95% ``` Possible route skeleton: ```text 0 km Bengaluru – Sri Sri Manor 25 km Join NH44 near Electronic City 45 km Hosur 95 km Krishnagiri 148 km Dharmapuri 210 km Salem 265 km Namakkal 305 km Karur 383 km Dindigul 435 km Ayyankottai 455 km Madurai ``` Strategic EV emphasis: ```text Primary late charge: Ayyankottai – Temple City Xpress Fallback: Dindigul Comfort stop: Salem – Radisson Blu + fast charging ``` Visual flow: ```text MADURAI / DESTINATION ▲ ╱ Ayyankottai ╱ Dindigul ╲ Karur ╲ Salem ╲ Krishnagiri ╲ Hosur ╲ BENGALURU / START ``` The final design should be more organic and visually attractive than the ASCII sketch. --- # 26. Reusable Image-Generation Prompt Template Use the following structure when generating the final map image: ```text Create a polished A4 portrait EV road-trip infographic. TRIP: Origin: {{START}} Destination: {{DESTINATION}} Departure: {{DEPARTURE_TIME}} Vehicle: {{EV_MODEL}} Battery: {{BATTERY_KWH}} Starting SOC: {{START_SOC}} PAGE: - A4 portrait - Start at bottom - Destination at top - Map fills the FULL WIDTH of the page and dominates it - NO vertical sidebar or text/table column down either side — all stop info is in small cards attached to the road, spread on both sides - Small header - Small footer - Small verification-mode chip: "{{VERIFICATION_MODE}}" (e.g. "Sides verified from Google Maps" or "Sides unverified — confirm live") ROAD: - Wide highway on a STRONG DIAGONAL, corner to corner (bottom-left to top-right, or mirrored) - Must NOT be a straight, centered, vertical road - The diagonal opens balanced space on BOTH sides for checkpoint cards - Rich teal/cyan-blue road - White dashed lane markings - Natural S-curves - Bottom-left toward top-right where geographically sensible - Stretch across most of the page - Show major highway shields CHECKPOINTS: {{CHECKPOINTS_WITH_KM}} For every major checkpoint: - place marker directly on road - orange circular node - orange flag - short connector - clearly show LEFT or RIGHT relative to travel direction STOP PREFERENCE: - prioritize same-side stops - avoid median crossings and U-turns - charger/hotel/food stops should be close to the route EV STOPS: {{EV_STOP_DETAILS}} HOTELS: {{HOTEL_DETAILS}} FOOD: {{FOOD_DETAILS}} SCENIC: {{SCENIC_DETAILS}} COLORS: - route = teal/cyan-blue - start = amber/orange - destination = red - checkpoints = orange - label frames = blue/navy - charging = green - food = orange - hotel = blue/indigo - scenic = purple DIRECTION: Show a subtle transparent compass or direction arrow: “Overall direction: {{DIRECTION}}” STYLE: - vibrant - professional - modern travel-pamphlet - print-friendly - concise labels - no dense paragraphs - road is the strongest visual element - use scenic illustrations only as supporting context ``` --- # 27. Final Response Behavior When delivering the result: - show the final image - **always include the text source-of-truth block (see §27A) together with the image** - do not dump all research into the answer - mention only important caveats - if useful, offer a print-ready PDF version - if the user changes the visual style, edit the existing image instead of rebuilding from scratch - preserve all route facts during stylistic edits unless the user asks to change them --- # 27A. Mandatory Text Source-of-Truth Block Image generation cannot be trusted to render small text and digits accurately — a figure like `405 km` may come out garbled, and a U-turn chip may show the wrong number. Therefore **every final map must be accompanied by a compact text block that is the authoritative source of truth.** The image is illustrative; the text block is correct. Emit it directly below the image, in the same response. ## Template ```text ROUTE — SOURCE OF TRUTH (image is illustrative; trust this table) → • Main highway: Google Maps: ~ • ~ • Route confirmed by user Side verification: VERIFIED FROM GOOGLE MAPS (or: UNVERIFIED — confirm sides live before departure) # Checkpoint Cum km Side Stop / notes 1 0 km START — 2 ~ LEFT • same side 3 ~ RIGHT • opposite U-turn ~0.4 km (verified) • … n ~ DESTINATION EV strategy: preferred • fallback • Unverified items: ``` ## Rules - Cumulative km and U-turn distances in the table must match the **confirmed Google Maps route** — never a different or older route version. - Mark anything unverified explicitly (`SIDE NOT VERIFIED`, `U-turn distance not verified`) rather than omitting it or guessing. - A U-turn distance appears in the table **only** for a row marked `opposite side`. - **If the image and this table disagree, the table wins.** Tell the user to trust the table for exact numbers and sides. --- # 28. Non-Negotiable Defaults Unless explicitly overridden: ```text START = bottom DESTINATION = top ROAD = wide ROAD = strong diagonal (corner to corner), NEVER straight/vertical/centered ROAD = dominant LAYOUT = map fills full page width LAYOUT = NO side text column / NO checkpoint table painted on the poster CHECKPOINT CARDS = spread on BOTH sides of the diagonal road CHECKPOINT = visible on road CHECKPOINT = flag + connector STOP SIDE = LEFT / RIGHT relative to travel direction (verified, not page placement) PREFERENCE = same-side stop HEADER = compact FOOTER = compact MAP = uses most of A4 page ROUTE COLOR ≠ START COLOR ``` These rules represent the preferred house style for this skill. # 6A. Opposite-Side Stops and U-turn Logic When a selected charger, restaurant, or hotel is on the **opposite carriageway** and still worth recommending, the map must explicitly show that fact. ## Required behavior For any opposite-side stop: - mark it as **Opposite side** - add a visible **U-turn** symbol or curved arrow - add the **U-turn distance only** (not total trip distance) - keep the main cumulative trip km separately in the normal stop badge A U-turn marker belongs **only** to a verified `opposite side` stop. A `same side` stop never shows one, regardless of where its label sits on the page (see §6.0). Example label pattern: ```text RIGHT • OPPOSITE SIDE U-turn ~0.6 km ``` or ```text U-turn ↺ 0.4 km ``` ## Verification rule A U-turn distance must be added **only after it is verified from Google Maps** (or from the user-provided Google Maps screenshot / route confirmation source). If the U-turn distance cannot be verified reliably, do **not invent it**. Use one of these instead: ```text U-turn required ``` or ```text U-turn distance not verified ``` ## Priority rule Prefer same-side stops by default. Choose an opposite-side stop only when it is still worth recommending because of one or more of the following: - significantly better charger reliability - much better hotel or restaurant quality - well-known / highly preferred stop - strategic value for the route ## Visual rule Opposite-side stops should stand out clearly from same-side stops. Recommended styling: - orange curved U-turn arrow - orange/red mini badge reading `U-turn` - small distance chip such as `0.5 km` # 6B. Verify Sides and Distances BEFORE Putting Them on the Map `SIDE NOT VERIFIED` is a last resort, not a default. A map where **every** stop reads `SIDE NOT VERIFIED` (as can happen if the model skips the check) is a failed map — it means the real work of verifying was never done. Anything printed **on the map** as a fact must be verified first: - **Cumulative km** — read from the confirmed Google Maps route. Only the trip total is usually exact; intermediate figures may be `~approx` but must still come from the real route, not be made up. - **LEFT / RIGHT and same / opposite** — determine from the actual carriageway and travel direction (§6, §6.0), using the Google Maps route / Street View / the user's screenshot. - **U-turn distance** — the local crossover distance from Google Maps, for verified opposite-side stops only. ## The order of operations 1. **Try to verify** each side and U-turn distance from the available map evidence (the user's screenshot, Google Maps, Street View, the confirmed route). Make a genuine attempt — do not jump straight to "not verified." 2. If, after a real attempt, a specific side or distance still cannot be confirmed, mark **only that item** `SIDE NOT VERIFIED` / `U-turn distance not verified`. 3. If **most** stops end up unverified, say so plainly to the user and offer to verify against a Google Maps screenshot (Option A) before finalizing — do not quietly ship a map that is unverified end to end. Honesty beats invention, but a real verification attempt beats a lazy blanket "not verified." The verification-mode chip (§17) must reflect reality: use `Sides verified from Google Maps` only when they genuinely were. # 2A. Mandatory Route-Confirmation Flow This skill should preferably begin from a **Google Maps screenshot** supplied by the user. That screenshot acts as the route-confirmation source for: - chosen corridor / route path - total route distance - total route duration - visible city sequence - road closures / diversions indicators if shown - candidate opposite-side U-turn confirmation where visible or later verified ## User confirmation workflow Before the final polished pamphlet is created, the assistant should do this: ### Step 1 — Input collection Collect either: - a Google Maps screenshot, plus - the start and destination points or ask the user to provide them. ### Step 2 — Draft flow map Create a simpler **flow map / route skeleton draft** first. This draft should confirm: - start point - destination - selected route corridor - checkpoint order - approximate cumulative km sequence ### Step 3 — User confirmation Ask for confirmation that the draft follows the intended Google Maps route. Only after confirmation should the assistant create the final A4 polished map. If the user already clearly confirms the screenshot route, the assistant may proceed directly to the final map.