How zeus-pr/cutly works
CUTLY is a customer-facing salon/barber discovery and booking product, with separate partner operations and admin surfaces. The main customer journey is sign-in, find a nearby shop or service, select a booking time, place a hold, review and confirm, then manage visits. The README describes backend availability, booking-state, payment-provider, and relational-model capabilities; only some backend routes were excerpted, so uncertain internal calls are omitted. The repository tree does not include the documented Prisma schema, so no schema or database node is asserted.
Main entry points: server.ts REST API routes · api.ts Mobile API boundary · review.tsx Booking review · index.tsx Shop discovery
Components 24
Customer app
- Customer sign-in
app/auth.tsx - Shop discovery
app/search/index.tsx - Service results
app/search/[service].tsx - Shop selection
app/shop/[id]/index.tsx - Booking selection
app/booking.tsx - Booking review
app/booking/review.tsx - Booking management
app/booking/[id].tsx - Visit history
app/visits.tsx
Booking backend
- REST API routes
backend/src/server.ts - Availability engine
backend/src/availability.ts - Booking transitions
backend/src/bookingState.ts - Customer services
backend/src/customer.ts - Payment provider
backend/src/payment.ts
Partner operations
- Partner workspace
app/partner/(tabs)/index.tsx - Partner operations
backend/src/partner.ts - Partner history
backend/src/partnerHistory.ts
Admin and web
- Partner lead site
site/src/App.tsx - Lead submission API
site/src/api.ts - Admin console
admin/src/App.tsx - Catalogue management
backend/src/catalogueAdmin.ts
Shared app services
- Mobile API boundary
services/api.ts - Place and location
store/usePlaceStore.ts - Secure session
store/useSessionStore.ts
Other components
- Customer
Connections 27
- Customer → Customer sign-in: signs in
README.md - Customer sign-in → Secure session: stores session
app/auth.tsx - Customer → Shop discovery: finds shops
README.md - Shop discovery → Mobile API boundary: queries shops
app/search/index.tsx - Shop discovery → Place and location: uses active place
app/search/index.tsx - Customer → Service results: chooses service
README.md - Service results → Mobile API boundary: loads shop results
app/search/[service].tsx - Customer → Shop selection: selects shop
README.md - Customer → Booking selection: selects time
README.md - Booking selection → Mobile API boundary: requests availability
- Customer → Booking review: reviews booking
README.md - Booking review → Mobile API boundary: creates booking
app/booking/review.tsx - Booking review → Booking review: notifies shop
app/booking/review.tsx - Customer → Booking management: checks booking
README.md - Customer → Visit history: views visits
README.md - Mobile API boundary → REST API routes: calls REST API
- REST API routes → Customer services: routes customer actions
backend/src/server.ts - REST API routes → Booking transitions: routes booking actions
backend/src/server.ts - REST API routes → Availability engine: uses availability
- REST API routes → Payment provider: uses provider contract
- Customer → Partner workspace: partner signs in
README.md - Partner workspace → Partner operations: manages operations
- Partner workspace → Partner history: views history
- Partner lead site → Lead submission API: submits partner lead
site/src/App.tsx - Lead submission API → REST API routes: submits lead
- Admin console → REST API routes: administers product
- REST API routes → Catalogue management: routes catalogue edits
backend/src/server.ts