‹ 首页

user-auth-flows

@lngyneric · 收录于 今天 · 上游提交 2 天前

Use when changing backend user auth, verification codes, token persistence, temp-user behavior, or auth-provider integration. Keep provider dispatch and credential state centralized.

场景用户登录权限校验令牌管理

适合你，如果经常需要实现或修改用户认证逻辑

/ 下载安装
https://github.com/lngyneric/ai-coach/tree/main/src/api/skills/user-auth-flows ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add lngyneric/ai-coach/user-auth-flows
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- lngyneric/ai-coach/user-auth-flows
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify lngyneric/ai-coach/user-auth-flows
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
0GitHub stars
~216上下文体积 · 单文件
索引托管

怎么用

技能原文 SKILL.md作者撰写 · Apache-2.0 · 5802c88

User Auth Flows

Core Rules
  • Keep repository, token-store, and auth-factory paths as the source of truth.
  • Preserve verification-code consumption semantics and retry safety.
  • Update frontend-facing auth payloads together with backend persistence logic.
Workflow
  1. Start from repository.py, token_store.py, auth/factory.py, and the specific flow file such as email_flow.py or phone_flow.py.
  2. Confirm whether the change affects credentials, tokens, temp users, or provider dispatch.
  3. Update validation and persistence together; avoid one-sided changes in route or provider code.
  4. Add or update tests under src/api/tests/service/user/.
Regression Checklist
  • Happy-path login or verification.
  • Retry or duplicate submission path.
  • Invalid or expired verification code.
  • Token persistence and logout semantics when affected.
按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…