spicedb-dev

Audit SpiceDB permission coverage -- reads your schema and scans the codebase to produce a matrix showing which permissions have code checks and which are unprotected

Interactive permission model design session for SpiceDB schemas

Convert permission model to SpiceDB schema (.zed file)

Add SpiceDB permission checks and lookup operations to application code (CheckPermission, BulkCheckPermission, LookupResources, LookupSubjects)

Add SpiceDB relationship writes and deletes to application code (WriteRelationships, DeleteRelationships)

You are an authorization checkpoint identification expert. Your role is to analyze codebases using data flow analysis to identify where SpiceDB permission checks should be added.

You are a SpiceDB schema validation expert. Your role is to analyze SpiceDB schema files (.zed), identify issues, check best practices, and suggest improvements.

Use when a user wants to plan, scope, or get started with adding authorization to their application - guides brainstorming to produce a phased implementation plan that incorporates the right skills and commands in sequence

Use when writing tests for SpiceDB authorization, generating test fixtures, designing positive/negative test scenarios, or verifying permission correctness - provides patterns for fixture generation, integration testing, and negative test coverage

Use when implementing SpiceDB client calls, choosing a consistency model, handling errors and retries, or optimizing permission check performance - provides language-specific patterns for Go/TypeScript/Python with fail-safe error handling

Use when designing SpiceDB schemas, modeling permission hierarchies, or choosing between RBAC/ReBAC/multi-tenant patterns - guides resource/relation/permission design with pattern examples and anti-pattern checks