PokePlaybook

The premise is that building a competitive team is mostly bookkeeping. You are tracking type coverage, shared weaknesses, which moves a species can actually learn in the format you are playing, and what the standard answers to your team look like. PokePlaybook keeps that state for you: teams are scoped to a generation, game, or open competitive rules, and the pickers only offer what is legal in that context.

Coverage analysis updates as you build, so you can see your offensive gaps and stacked weaknesses while there are still open slots to fix them. On top of that is an AI review that reads the team and talks through its problems, and will fill empty slots with suggestions that fit what you already have. The model keys live as Supabase Edge Function secrets and the app never sees them, which was the design constraint from the start.

It is one SwiftUI codebase across iPhone, Mac, and Vision Pro. Architecture is MVVM with observable view models over actor-isolated services, which keeps the I/O boundaries obvious and the business logic testable behind protocol mocks. Teams persist on device and sync to Supabase when signed in. Still in progress, but the core loop works.