devverse-supabase-auth
Supabase auth, favorites, and security boundaries for DevVerse. Use when changing files under supabase/, auth or favorites UI, or the verify-email and reset-password API routes.
Datos de origen
- Repositorio
- hoangsonww/DevVerse-SWE-Blog
- Última actividad en el origen
- 28 de febrero de 2026 a las 11:47
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 15
- Forks
- 13
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Explorador de archivos
3 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- devverse-supabase-auth
- description
- Supabase auth, favorites, and security boundaries for DevVerse. Use when changing files under supabase/, auth or favorites UI, or the verify-email and reset-password API routes.
# DevVerse Supabase Workflow
1. Keep anon and service-role responsibilities separate.
Browser-facing auth, favorites, and storage helpers use the anon client. Service-role usage must stay server-only.
2. Treat verify-email and reset-password routes as security-sensitive.
Those routes are publicly callable and currently enumerate users via `listUsers({ perPage: 1000 })`.
3. Do not move service-role code into shared modules imported by client code.
4. Remember what Supabase is and is not used for here.
Supabase handles auth, favorites, and some profile/storage helpers. It is not the runtime source of article content.
5. Read the runtime boundaries before changing auth or favorites behavior.
@references/runtime-boundaries.md
6. After auth route changes, run repo tests and state any real-env validation you could not perform.
Ver en GitHub