Use Claude to build offline trip apps from a skill
Komugi @ PowerPlatform first hand-built a travel app for a Los Angeles trip, including flights, an itinerary, maps, shared expenses and Disney planning. Rebuilding that structure for each destination would have taken several more days, so the author created a reusable Claude Code skill called trip-app.
note.com
Original prompt
Shared by the source author. See source notes for context.
新都市のスポットを勝手にでっち上げない（幻覚防止）
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Komugi @ PowerPlatform
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Generated offline trip apps with itineraries, maps, costs and preparation tasks, including Hong Kong and Amsterdam examples and opening-day warnings.
- Human involvement
- The author defined rules and reusable inputs; API warnings were produced, but no separate independent review checkpoint is reported.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Collect destination, traveler and pacing requirements in one batch.
- Build the schedule from checked attractions and enrich its guide notes.
- Check opening days and export a self-contained HTML app.
Komugi @ PowerPlatform first hand-built a travel app for a Los Angeles trip, including flights, an itinerary, maps, shared expenses and Disney planning. Rebuilding that structure for each destination would have taken several more days, so the author created a reusable Claude Code skill called trip-app.
The skill gathers requirements together, including travelers, dates, interests, pace, budget and essential stops. A program then builds the itinerary skeleton from a checked attraction pool; Claude enriches the notes with addresses, highlights, prices and alternatives. Before export, Google Places checks the attractions and warns when a proposed visit conflicts with a closed day.
The author reports generating a Hong Kong app after answering questions, building an Amsterdam version with an entry-system preparation reminder, and adding Lisbon through an OpenStreetMap discovery and verification pipeline. The final deliverable is a single HTML file containing the itinerary, maps, flight schedule, expense breakdown and preparation tasks. It opens without a server and can be shared with family.
A rule forbids invented attractions or unsupported opening-hour and price claims. Shared-expense features turn on for multiple travelers and hide for solo trips. The account describes generated apps and API warnings; it does not report an independent review of every recommendation or completed bookings.
Prompt
Original prompt
Source: note.com · Komugi @ PowerPlatform
Frequently asked questions
Why keep attraction selection outside the language model?
The author used a checked pool and program to prevent invented locations; Claude handled descriptions and personalization.
What opening-day issue was caught?
The verification log warned that two proposed Monday visits conflicted with attractions closed on Mondays.
Does the app require hosting?
The build packs its code and data into a single HTML file that opens locally and can be shared.
More details
About this account
Claude followed the trip-app skill, enriched guide notes and assembled the offline app alongside programmed selection and API checks.
Firsthand source opened and read. Prompt is a verbatim excerpt of the published original instruction.
Credit: Komugi @ PowerPlatform
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · trip-app skill · Google Places API · OpenStreetMap · HTML
Offline trip app · Shared travel costs · Opening-day checks
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.