| schemaVersion | 2026-04-11T00:00:00.000Z |
| skillId | backend/auth-authorization-backend |
| name | auth-authorization-backend |
| displayName | Backend Auth Authorization |
| description | Use when working on authentication, authorization, sessions, API keys, RBAC, ABAC, and tenant boundaries. Focus on least privilege, secure defaults, session safety, and auditable permission checks. |
| aliases | ["auth-authorization-backend","Backend Auth Authorization","auth authorization backend","authauthorizationbackend","后端鉴权","接口授权","租户边界","权限检查","认证","权限","RBAC","ABAC","服务端","server side","auth","authorization","登录页面"] |
| version | 0.1.0 |
| sourceHash | sha256:35bfe393f0b974dc59f9a35eac23fd2502d41aea90fba48098442b49df44a26b |
| domain | backend |
| departmentTags | ["backend-platform"] |
| sceneTags | ["architecture","security-audit"] |
Backend Auth Authorization
Use this skill when the task involves authentication, authorization, sessions, API keys, RBAC, ABAC, and tenant boundaries.
Goal: produce reliable engineering guidance and implementation steps focused on least privilege, secure defaults, session safety, and auditable permission checks.
Working model
- Identify the affected system, data, users, and failure modes.
- Define invariants, inputs, outputs, ownership, and rollback needs.
- Prefer small, auditable changes with explicit validation.
- Call out security, performance, concurrency, and data-loss risks when relevant.
- Finish with concrete verification steps and residual risks.
Rules
- Ground recommendations in the current codebase or runtime evidence.
- Prefer explicit contracts, typed boundaries, and defensive validation.
- Do not hide operational concerns behind generic best practices.
- Include negative cases, edge cases, and failure behavior.
- For review tasks, list findings first with file and line references when possible.
- For test or performance tasks, define the workload, success criteria, and measurement method.
Checklist
- Are assumptions and ownership boundaries explicit?
- Are risky changes reversible or safely deployable?
- Are observability and diagnostics sufficient for production issues?
- Are tests or validation steps targeted to the actual risk?
- Are security and data-integrity concerns addressed?
