Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Use when migrating an application from another authorization system (OpenFGA, Okta FGA) to SpiceDB - runs the phase pipeline that converts schema, data, application code, and tests, with a pre-flight gate that surfaces every blocking decision before conversion begins.
Skill Claude CodeCodex
Use when converting an OpenFGA, Okta FGA, or Auth0 FGA authorization model and application to SpiceDB - supplies the construct mapping, blocker catalog, identifier normalization, and code mapping needed to convert the schema, data, and application code.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Use when adding a SpiceDB client library to a project in Go, Python, TypeScript, C#, Java, Rust, or Ruby - covers obtaining the prototype client and the common patterns (relationships, consistency, streaming lookups) shared across all seven languages.
Skill Claude CodeCodex
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.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: