trails-cool/trails
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
trails/openspec/changes/phase-1-mvp/specs/shared-packages/spec.md
Ullrich Schäfer da2f3c04ba
Add OpenSpec phase-1-mvp change with full specifications 
OpenSpec initialized with Claude Code integration. Created phase-1-mvp
change with all artifacts:

- proposal.md: 9 new capabilities covering Planner, Journal, and infrastructure
- design.md: 8 technical decisions with alternatives considered
- specs/: 9 capability specs with testable WHEN/THEN scenarios
  - planner-session, brouter-integration, map-display
  - journal-auth, route-management, planner-journal-handoff
  - activity-feed, shared-packages, infrastructure
- tasks.md: 11 task groups, 74 implementation tasks

Ready for implementation via /opsx:apply

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-22 11:35:21 +01:00

2.5 KiB
Raw Blame History

ADDED Requirements

Requirement: Shared types package

The @trails-cool/types package SHALL export TypeScript interfaces for Route, Activity, Waypoint, RouteVersion, and RouteMetadata used by both apps.

Scenario: Import types in Planner

  • WHEN the Planner app imports @trails-cool/types
  • THEN it has access to the Waypoint, Route, and RouteMetadata interfaces

Scenario: Import types in Journal

  • WHEN the Journal app imports @trails-cool/types
  • THEN it has access to Route, Activity, RouteVersion, and RouteMetadata interfaces

Requirement: GPX parsing package

The @trails-cool/gpx package SHALL parse GPX XML into structured data (waypoints, tracks, elevation) and generate GPX XML from structured data.

Scenario: Parse GPX to waypoints

  • WHEN the gpx package parses a valid GPX file
  • THEN it returns an array of Waypoint objects with lat, lon, and optional name

Scenario: Generate GPX from waypoints

  • WHEN the gpx package is given an array of waypoints and a track
  • THEN it generates a valid GPX XML string

Scenario: Extract elevation data

  • WHEN the gpx package parses a GPX file with elevation data
  • THEN it returns elevation gain, loss, and a profile array of distance/elevation pairs

Requirement: Map rendering package

The @trails-cool/map package SHALL provide React components for rendering Leaflet maps with configurable base layers and route overlays.

Scenario: Render map component

  • WHEN the map package's MapView component is rendered with a center and zoom
  • THEN a Leaflet map is displayed with the default OSM tile layer

Scenario: Display route on map

  • WHEN the map package's RouteLayer component receives GeoJSON
  • THEN it renders a polyline on the map

Requirement: UI component package

The @trails-cool/ui package SHALL provide shared React components (buttons, layout, form elements) styled with Tailwind CSS.

Scenario: Use Button component

  • WHEN an app renders the Button component from @trails-cool/ui
  • THEN a styled button is displayed consistent with the trails.cool design

Requirement: i18n package

The @trails-cool/i18n package SHALL provide react-i18next configuration and translation strings starting with English and German.

Scenario: Display German translation

  • WHEN a user's browser locale is set to German
  • THEN UI strings are displayed in German

Scenario: Fallback to English

  • WHEN a user's browser locale is not supported
  • THEN UI strings fall back to English