Pet Flex Admin
Personal — Next.js platform-owner admin for clinics & subscriptions
Role: Personal project — sole builder
Overview
Highest-privilege Pet Flex client for the platform owner: track clinic subscriptions, manage clinic staff, and operate cross-clinic tooling while relying on Supabase RLS and edge functions as the real authorization boundary.
The core challenge
Admin surfaces can leak every clinic's data if client checks are mistaken for security. Needed a secure, data-dense Next.js panel that stays a pure client of pet-flex-backend.
The engineering solution
Built on Next.js App Router with Tailwind v4 and shadcn/ui; wired @supabase/ssr to the same project as mobile. Used Superpowers plans, Graphify, Codegraph, and core-cybersecurity / design-taste skills to keep privileged flows reviewable and intentional.
Architecture
- Next.js 16 App Router · React 19 · TypeScript strict · Tailwind CSS v4 (CSS-first theme)
- shadcn/ui component system for tables, forms, dialogs, and ops UI
- @supabase/ssr + generated Database types from pet-flex-backend
- Platform-admin capabilities gated by backend is_platform_admin() / RLS / edge functions
- Agent tooling: Superpowers implementation plans, Graphify, Codegraph, cybersecurity skills
Highlights
- Treats client UI as convenience — authorization lives in Postgres RLS and Deno edge functions
- Typed against shared Supabase schema; no separate admin database
- Documented Superpowers plan for platform-admin identity, staff, and subscription ops
Ops and governance surface for the Pet Flex platform, showcasing secure Next.js admin architecture and agent-guided delivery.