AllTrails Plus

Build me an offline GPX route library for my own hikes as a limited substitute for AllTrails Plus. Requirements:

- Make a local web app with Node, Express, Leaflet, and better-sqlite3. Import GPX files supplied by me; retain the originals in a selected folder.
- Parse each track into distance, elevation range, start point, and route bounds; show the route on a map and list the source file and import date.
- Let me add trail notes, planned date, difficulty label, emergency contact, and a personal checklist. Search routes by title and tags.
- Export a route detail page as printable HTML and its original GPX file for use in a separate navigation app.
- If a map tile source requires a network connection or license, explain that and show a blank map with route geometry when tiles are unavailable.
- No scraped trails, reviews, live conditions, automatic offline basemap downloads, or claims that the route is safe or open. No accounts or telemetry.
- README: how to obtain GPX files lawfully, import and export, storage path, and why users must check current conditions from authoritative sources.

# AGENTS.md — Build guide for AllTrails Plus

## Project scope
Organize user-imported GPX routes and trip notes, map user-entered places and reservations, and keep an offline itinerary without copying proprietary trail data or claiming live availability.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For AllTrails Plus, organize user-imported GPX routes and offline trip notes without copying trail data. The hard boundary is massive trail database, reviews, conditions, maps, community, and mobile navigation, plus proprietary live data and network coverage.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- modern browser
- MapTiler or compatible map key
- user-entered reservations
- optional public transit or weather API

## Stack and architecture
- Node and Express
- better-sqlite3
- Leaflet
- GPX parser chosen for maintained support

## Security and data integrity
- Treat GPX as untrusted XML and disable external entities
- Keep imported files under a selected local directory
- Do not claim current trail safety from stale files

## Agent implementation rules
- Check map tile terms before defaulting to a provider
- Handle missing or malformed elevation data

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Describe it as a personal route library without a trail database

## Engineering roadmap
1. Build GPX import and route metadata storage.
2. Render personal route pages and original file export.
3. Document offline map and live-condition limitations.

## Paid-product capabilities outside this build
- massive trail database, reviews, conditions, maps, community, and mobile navigation
- live fare and inventory data
- global routing dataset
- crowdsourced trail intelligence
- booking, disruption support, and offline map fleet

## Implementation prompt
Build me an offline GPX route library for my own hikes as a limited substitute for AllTrails Plus. Requirements:

- Make a local web app with Node, Express, Leaflet, and better-sqlite3. Import GPX files supplied by me; retain the originals in a selected folder.
- Parse each track into distance, elevation range, start point, and route bounds; show the route on a map and list the source file and import date.
- Let me add trail notes, planned date, difficulty label, emergency contact, and a personal checklist. Search routes by title and tags.
- Export a route detail page as printable HTML and its original GPX file for use in a separate navigation app.
- If a map tile source requires a network connection or license, explain that and show a blank map with route geometry when tiles are unavailable.
- No scraped trails, reviews, live conditions, automatic offline basemap downloads, or claims that the route is safe or open. No accounts or telemetry.
- README: how to obtain GPX files lawfully, import and export, storage path, and why users must check current conditions from authoritative sources.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.