503c29613b
- Introduced SKILL.md outlining the principles and processes for effective interface design. - Added critique.md for evaluating design outputs and ensuring craft over correctness. - Created example.md to illustrate the application of subtle layering principles in design decisions. - Developed principles.md detailing core craft principles for consistent design quality. - Implemented validation.md for memory management and pattern reuse in the design system. - Established system.md for the Playzer design system, defining direction, domain concepts, and design decisions. - Added StatusBadge component for displaying booking statuses with appropriate styles and labels. - Updated skills-lock.json to include the new interface-design skill.
Playzer Monorepo
Este repositorio contiene:
apps/frontend: React + Vite + TanStack Router/Query.apps/backend: Bun + Hono + Prisma + Better Auth.packages/api-contract: contratos Zod/tipos compartidos.
Requisitos
- Bun reciente
- PostgreSQL disponible
Setup rápido
- Instalar dependencias:
bun install
- Configurar backend:
cp apps/backend/.env.example apps/backend/.env
- Configurar frontend:
cp apps/frontend/.env.example apps/frontend/.env
- Ejecutar migraciones:
bun --filter backend prisma:migrate
Variables de entorno
Backend (apps/backend/.env)
DATABASE_URLBETTER_AUTH_SECRETBETTER_AUTH_URLAPP_BASE_URLCORS_ORIGIN
Frontend (apps/frontend/.env)
VITE_API_BASE_URL
Desarrollo
Backend:
bun run dev:backend
Frontend:
bun run dev:frontend
Todo junto:
bun run dev
Prisma
Regenerar cliente después de cambios de schema:
bun --filter backend prisma:generate
Autenticación
El proyecto usa Better Auth con sesión por cookie.
- Backend:
c.get('user')yc.get('session')en contexto Hono. - Frontend:
authClientconfetchOptions.credentials = 'include'. - Frontend API: Axios con
withCredentials = true. - Backend CORS:
credentials: true.
Deploy (Docker)
- Build context: raíz del monorepo (
./) - Dockerfile:
./Dockerfile - Build args requeridos:
DATABASE_URLVITE_API_BASE_URLBETTER_AUTH_SECRETBETTER_AUTH_URL
Flujo recomendado de cambios de API
- Actualizar contrato en
packages/api-contract. - Implementar backend en
apps/backend. - Consumir contrato desde frontend (
@repo/api-contract).