菜单
Data architecture - models, relationships. Use when designing data structures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Abuse prevention - rate limiting, moderation, bad actors. Use when fighting abuse.
Account security - MFA, sessions, recovery. Use when protecting user accounts.
Admin panel - RBAC, config, admin tools. Use when building admin UI.
Application security - OWASP, validation, secrets. Use when securing the app.
Authentication patterns - sign-in, SSO, passkeys, sessions. Use when implementing auth flows.
Billing - Stripe, webhooks, subscriptions. Use when implementing payments.
| name | data-architecture |
| description | Data architecture - models, relationships. Use when designing data structures. |
Data architecture determines what's possible and what's painful. Good architecture makes new features easy; bad architecture makes everything hard. The question isn't "does it work today?" but "will it work when requirements change?"
Consider the boundaries between domains, the flow of data through the system, and the consistency guarantees at each step. Where are implicit assumptions that will break? Where is complexity hidden that will cause bugs?
