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.
来源信息
- 仓库
- hoangsonww/DevVerse-SWE-Blog
- 最近来源活动
- 2026年2月28日 11:47
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 15
- 分支
- 13
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- 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.
- user-invocable
- false
# 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.
在 GitHub 查看