メニュー
Data modeling - entities, relationships, schemas. 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-modeling |
| description | Data modeling - entities, relationships, schemas. 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?
