skills.rest
tassosgomes
tassosgomesCOMMUNITY
Explore all skills by this author →
GitHub

roles-naming

Standardize role naming across microservices and IdPs using SCREAMING_SNAKE_CASE.

Updated Apr 16, 2026
Search Tags:#microservices#rbac#roles#naming#keycloak#identity-provider
One-click install
npx skills add https://github.com/tassosgomes/poc-iam-service --skill roles-naming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roles-naming
Source: https://github.com/tassosgomes/poc-iam-service/tree/main/.github/skills/common/roles-naming
Command: npx skills add https://github.com/tassosgomes/poc-iam-service --skill roles-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use este skill quando o usuario precisar padronizar nomenclatura de roles (perfis de acesso) em ecossistemas de microserviços entre serviços e provedores de identidade, evitando divergências de nomenclatura e facilitando migrações.

Core Features & Use Cases

  • Define o formato SCREAMING_SNAKE_CASE como padrão obrigatório para nomes de roles.
  • Define a hierarquia entre roles globais e roles de domínio para maior clareza e escalabilidade.
  • Indica diretrizes de integração IdP ↔ microserviços, incluindo a claim de roles e consumo a nível de serviço.

Quick Start

Configure um conjunto de roles seguindo SCREAMING_SNAKE_CASE e aplique as regras de nomenclatura no IdP e nos serviços.

Frequently Asked Questions about roles-naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize role naming across microservices and identity providers?▼

To standardize role naming across microservices, enforce SCREAMING_SNAKE_CASE globally and remove IdP prefixes. This prevents case mismatches and maintains consistent role dictionaries during migrations.

What is the correct role naming format for consistent RBAC in microservices?▼

The correct role naming format for consistent RBAC in microservices is SCREAMING_SNAKE_CASE. It enforces case-sensitive comparisons and removes identity provider prefixes to prevent access mismatches.

How do I handle global and domain-specific roles in a microservices architecture?▼

Handling global and domain-specific roles in a microservices architecture requires defining a clear hierarchy. Domain-specific roles apply to individual services while global roles span the entire ecosystem.

How should microservices retrieve token roles from a Keycloak identity provider?▼

Microservices should retrieve token roles from an identity provider like Keycloak by extracting them directly from a 'roles' claim. This ensures consistent access control across diverse tech stacks.

Why do role prefix and case mismatches happen between Keycloak and microservices?▼

Role prefix and case mismatches happen between Keycloak and microservices due to inconsistent naming conventions. Removing IdP prefixes and enforcing case-sensitive SCREAMING_SNAKE_CASE resolves these integration issues.

Related Skills

Explore More Software Engineering Skills→
qauth-labsqauth-labs
23

auth-engine

Define credential verification, token claim generation, and provider registration rules for QAuth.

Official
Intermediate
zebbernzebbern
4.5k

Windows Privilege Escalation

Enumerate Windows privileges and misconfigurations to identify privilege escalation vectors.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

gateway-security

Configure JWT authentication and policy-based authorization for ASP.NET Core gateway endpoints.

Community
Advanced
RedHatProductSecurityRedHatProductSecurity
47

rbac

Map token claims to internal roles for MCP server authorization.

Official
Intermediate