Authorization

Browse prompts in this category.

Prompts

ABAC Architect
Design ABAC systems with XACML-style PDP/PEP/PIP/PAP separation, typed subject/resource/action/environment attributes, deny-overrides combination algorithms, and purpose-built policy languages (Rego, Cedar, Polar). Use when modeling attribute-driven access policies or externalizing authZ.
Casbin Developer
Design Casbin PERM models (request, policy, matchers, effect) supporting ACL, RBAC with domains, ABAC, and RESTful keyMatch2 patterns, plus DB adapters and watcher-based multi-instance sync. Use when writing Casbin .conf/.csv files or enforcer code in Go, Java, Node, Python, or Rust.
Cedar Policy Developer
Design Cedar permit/forbid policies with typed entity schemas, scoped principal/action/resource clauses, when/unless conditions, template-linked sharing grants, and Amazon Verified Permissions integration. Use when writing Cedar policies, schemas, or AVP-backed authorization services.
OpenFGA Developer
Implement OpenFGA authorization models with DSL type/relation/permission definitions, contextual tuples, conditional relationships, Check/ListObjects/ListUsers/Expand APIs, consistency tokens, and multi-store tenant isolation. Use when integrating OpenFGA or evolving FGA schemas.
Open Policy Agent Architect
Design OPA policy-as-code in Rego with default-deny, undefined-vs-false discipline, package modularity, JWT verification via io.jwt.decode_verify, bundles, decision logging, and opa test coverage. Use when authoring Rego policies, OPA bundles, or policy-engine integrations.
RBAC Architect
Design RBAC systems with action:resource permissions, DAG role hierarchies, static and dynamic separation of duties, deny precedence, time-bounded assignments, and privilege-creep audits against role explosion. Use when modeling roles, permissions, or reviewing existing RBAC schemas.
ReBAC Architect
Design Zanzibar-style ReBAC models with relationship tuples, computed permissions (union/intersection/exclusion), hierarchical containment, userset rewriting, and Zookie consistency tokens preventing the new-enemy problem. Use when modeling graph-based authorization or Check APIs.
SpiceDB Developer
Implement SpiceDB schemas with definitions, permission operators (+, &, -), caveats for conditional access, CheckPermission/LookupResources/Watch APIs, ZedTokens for new-enemy-safe consistency, and zed validate assertions. Use when writing AuthZed schemas or integrating SpiceDB.