How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

plan-workoutTracker - Prompt

Name: plan-workoutTracker
Author: delislejp

# Workout Tracker Development Plan ## Project Overview A progressive web app (PWA) for tracking strength and cardio workouts, built with React, Vite, and Tailwind CSS. The app persists data locally and is deployed to GitHub Pages. ## Current State - [x] **Project Setup**: Vite + React + TypeScript + Tailwind CSS (v4). - [x] **Core Features**: - [x] Log Strength Workouts (Exercise name, dynamic sets w/ weight & reps). - [x] Log Cardio Workouts (Bike: Time & Distance). - [x] "Recent Sessions" list with delete functionality. - [x] Progress visualization using Recharts (Max Weight, Volume, Time, Distance). - [x] Automatic "last set" and "last session" pre-filling for convenience. - [x] **Data Persistence**: `localStorage` used for saving workouts. - [x] **Infrastructure**: - [x] GitHub Pages deployment via `gh-pages`. - [x] PWA support (Manifest, Icons, Service Worker) using `vite-plugin-pwa`. - [x] CI/CD via manual `npm run deploy` script. ## Technical Stack - **Framework**: React 18+ - **Build Tool**: Vite - **Language**: TypeScript - **Styling**: Tailwind CSS - **Icons**: Lucide React - **Charts**: Recharts ## Roadmap & Refinement Opportunities ### 1. Refactoring (High Priority) - The entire application logic currently resides in `App.tsx`. - **Action**: Split into sub-components: - `components/Layout.tsx` - `components/WorkoutForm.tsx` (Split further into Strength/Bike forms) - `components/HistoryList.tsx` - `components/ProgressCharts.tsx` - **Action**: Extract logic into custom hooks (e.g., `useWorkouts`). ### 2. Feature Enhancements - [x] **Per Arm Toggle**: Option to specify if weight is per arm (e.g. dumbbells) for accurate volume calculation. - [ ] **Edit Functionality**: Allow users to edit details of a logged workout. - [ ] **More Activity Types**: Support Running, Swimming, etc. - [ ] **Data Management**: - [ ] internal Import/Export of data (JSON) so users don't lose data on cache clear. - [ ] Cloud sync (requires backend/Auth). - [ ] **Advanced Analytics**: - [ ] 1RM (One Rep Max) estimation. - [ ] Weekly/Monthly volume aggregation. ### 3. UI/UX Improvements - [ ] Add toast notifications for "Workout Saved" or "Deleted". - [ ] Implement a calendar view for workout history. - [ ] Dark mode toggle (Tailwind config exists, need UI toggle).

{ "prompt": "# Workout Tracker Development Plan\n\n## Project Overview\nA progressive web app (PWA) for tracking strength and cardio workouts, built with React, Vite, and Tailwind CSS. The app persists data locally and is deployed to GitHub Pages.\n\n## Current State\n- [x] **Project Setup**: Vite + React + TypeScript + Tailwind CSS (v4).\n- [x] **Core Features**:\n - [x] Log Strength Workouts (Exercise name, dynamic sets w/ weight & reps).\n - [x] Log Cardio Workouts (Bike: Time & Distance).\n - [x] \"Recent Sessions\" list with delete functionality.\n - [x] Progress visualization using Recharts (Max Weight, Volume, Time, Distance).\n - [x] Automatic \"last set\" and \"last session\" pre-filling for convenience.\n- [x] **Data Persistence**: `localStorage` used for saving workouts.\n- [x] **Infrastructure**:\n - [x] GitHub Pages deployment via `gh-pages`.\n - [x] PWA support (Manifest, Icons, Service Worker) using `vite-plugin-pwa`.\n - [x] CI/CD via manual `npm run deploy` script.\n\n## Technical Stack\n- **Framework**: React 18+\n- **Build Tool**: Vite\n- **Language**: TypeScript\n- **Styling**: Tailwind CSS\n- **Icons**: Lucide React\n- **Charts**: Recharts\n\n## Roadmap & Refinement Opportunities\n\n### 1. Refactoring (High Priority)\n- The entire application logic currently resides in `App.tsx`.\n- **Action**: Split into sub-components:\n - `components/Layout.tsx`\n - `components/WorkoutForm.tsx` (Split further into Strength/Bike forms)\n - `components/HistoryList.tsx`\n - `components/ProgressCharts.tsx`\n- **Action**: Extract logic into custom hooks (e.g., `useWorkouts`).\n\n### 2. Feature Enhancements\n- [x] **Per Arm Toggle**: Option to specify if weight is per arm (e.g. dumbbells) for accurate volume calculation.\n- [ ] **Edit Functionality**: Allow users to edit details of a logged workout.\n- [ ] **More Activity Types**: Support Running, Swimming, etc.\n- [ ] **Data Management**:\n - [ ] internal Import/Export of data (JSON) so users don't lose data on cache clear.\n - [ ] Cloud sync (requires backend/Auth).\n- [ ] **Advanced Analytics**:\n - [ ] 1RM (One Rep Max) estimation.\n - [ ] Weekly/Monthly volume aggregation.\n\n### 3. UI/UX Improvements\n- [ ] Add toast notifications for \"Workout Saved\" or \"Deleted\".\n- [ ] Implement a calendar view for workout history.\n- [ ] Dark mode toggle (Tailwind config exists, need UI toggle).", "variables": [], "notes": "Workout Tracker Development Plan", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/delislejp/workout-tracker", "path": ".github/prompts/plan-workoutTracker.prompt.md", "ref": "2d761c57a444d68fa277e894e027e55119354597", "url": "https://github.com/delislejp/workout-tracker/blob/2d761c57a444d68fa277e894e027e55119354597/.github/prompts/plan-workoutTracker.prompt.md", "key": "delislejp/workout-tracker/.github/prompts/plan-workoutTracker.prompt.md" } } }

plan-workoutTracker

About

Workout Tracker Development Plan

Project Overview

Current State

Technical Stack

Roadmap & Refinement Opportunities

1. Refactoring (High Priority)

2. Feature Enhancements

3. UI/UX Improvements

Install plan-workoutTracker and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews