How kijimoshi/padellic works
Padellic is a web app for creating and running Americano and Mexicano padel tournaments, with Swiss described as forthcoming. Organizers sign in, create tournaments, manage players and settings, generate rounds, record scores, and view standings; spectators can follow standings through a shared public link without an account. Tournament data and authentication use Supabase. The repository also exposes an MCP integration. Some routes and integrations were not excerpted, so their internal call paths are not inferred here.
Main entry points: client.ts Supabase client · tournament.$id.tsx Tournament management · t.$code.tsx Public tournament page · auth.tsx Sign-in and signup
Components 21
Web experience
- Landing page
src/routes/index.tsx - Sign-in and signup
src/routes/auth.tsx - Auth guard
src/routes/_authenticated/route.tsx - Public tournament page
src/routes/t.$code.tsx - Site header
src/components/site-header.tsx
Tournament operations
- Tournament dashboard
src/routes/_authenticated/dashboard.tsx - Tournament management
src/routes/_authenticated/tournament.$id.tsx - Pairing algorithms
src/lib/padel.ts - Tournament data access
src/lib/tournament-data.ts - Standings table
src/components/standings-table.tsx - Public tournament functions
src/lib/public-tournament.functions.ts
Identity and data
- Supabase client
src/integrations/supabase/client.ts - Supabase backend
- Preview auth storage
src/integrations/supabase/previewAuthStorage.ts
MCP access
- MCP route
src/routes/mcp.ts - Tournament MCP tools
src/lib/mcp/tools - MCP Supabase access
src/lib/mcp/supabase.ts - Protected-resource metadata
src/routes/[.well-known]/oauth-protected-resource.ts - MCP registry
src/lib/mcp/index.ts
Other components
- Visitor / organizer
- Spectator
Connections 21
- Visitor / organizer → Landing page: opens
src/routes/index.tsx - Landing page → Sign-in and signup: starts tournament
src/routes/index.tsx - Visitor / organizer → Sign-in and signup: signs in
src/routes/auth.tsx - Sign-in and signup → Supabase client: authenticates with
src/routes/auth.tsx - Auth guard → Supabase client: checks user
src/routes/_authenticated/route.tsx - Tournament dashboard → Tournament data access: loads and saves
src/routes/_authenticated/dashboard.tsx - Tournament dashboard → Supabase client: queries
src/routes/_authenticated/dashboard.tsx - Tournament management → Tournament data access: loads data
src/routes/_authenticated/tournament.$id.tsx - Tournament management → Supabase client: updates tournament
src/routes/_authenticated/tournament.$id.tsx - Tournament management → Pairing algorithms: generates rounds and standings
src/routes/_authenticated/tournament.$id.tsx - Tournament management → Standings table: renders standings
src/routes/_authenticated/tournament.$id.tsx - Public tournament page → Public tournament functions: loads public data
src/routes/t.$code.tsx - Public tournament page → Standings table: renders standings
src/routes/t.$code.tsx - Spectator → Public tournament page: follows link
README.md - Site header → Supabase client: reads auth and signs out
src/components/site-header.tsx - Supabase client → Preview auth storage: configures auth storage
src/integrations/supabase/client.ts - Supabase client → Supabase backend: connects
src/integrations/supabase/client.ts - MCP route → Tournament MCP tools: dispatches tools
- Tournament MCP tools → MCP Supabase access: uses data access
src/lib/mcp/tools/get-tournament.ts - MCP Supabase access → Supabase backend: accesses data
- Protected-resource metadata → MCP registry: reads metadata
src/routes/[.well-known]/oauth-protected-resource.ts