pricing-app-permissions

Combine role-based permissions with user overrides for backend and frontend access control.

1|2|Updated Oct 1, 2025
One-click install
npx skills add https://github.com/sernafernando/pricing-app --skill pricing-app-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pricing-app-permissions
Source: https://github.com/sernafernando/pricing-app/tree/main/skills/pricing-app-permissions
Command: npx skills add https://github.com/sernafernando/pricing-app --skill pricing-app-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a cohesive authorization framework that combines role-based access control with user-specific overrides to enforce secure, auditable permissions across backend services and frontend UI.

Core Features & Use Cases

  • Hybrid permission model: merges RBAC with per-user permission overrides to grant or revoke access precisely.
  • End-to-end enforcement: supports backend API checks via a PermisosService and frontend gating through a PermisosContext.
  • Auditing & guardrails: enables centralized permission management and consistent UI behavior across modules (e.g., products, configurations, users).

Quick Start

Configure your user roles and permission overrides in the database, then wire the frontend to use the PermisosContext for UI gating. Use the backend service to check permissions in critical endpoints.

Frequently Asked Questions about pricing-app-permissions

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

FAQPage Schema
How do I manage role-based access control with user-specific overrides in my application?

Role-based access control with user-specific overrides is managed by merging RBAC permissions with per-user grants or revocations. This hybrid model ensures precise access enforcement across both backend APIs and frontend UI modules.

How do I enforce permissions consistently across backend APIs and frontend UI?

Permissions are enforced consistently by applying backend service checks at critical endpoints and using a frontend context provider for UI gating. This unified approach maintains secure, auditable access across all application modules.

What is the best way to implement auditable permission checks for backend services?

Auditable permission checks for backend services are best implemented through a centralized permissions service that resolves role-based rules and user overrides. This approach enforces secure access and provides consistent behavior across modules.

How do I gate frontend UI components based on user authorization rules?

Frontend UI components are gated based on user authorization rules by wiring them to a permissions context provider. This context reads cached permission resolutions to conditionally render UI elements like products, configurations, and user management modules.

Does this authorization framework support caching for permission resolution?

The authorization framework supports caching for permission resolution to optimize access checks. By caching role-based permissions and user overrides, it reduces redundant database queries and enforces secure access efficiently across the stack.