nrpg-workflow

Enforce NRPG Platform authentication, multi-tenancy, and contractor privacy conventions.

1|Updated Sep 14, 2025
One-click install
npx skills add https://github.com/CleanExpo/DR-NRPG --skill nrpg-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nrpg-workflow
Source: https://github.com/CleanExpo/DR-NRPG/tree/main/.codex/skills/nrpg-workflow
Command: npx skills add https://github.com/CleanExpo/DR-NRPG --skill nrpg-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all work on the NRPG Platform adheres to critical security and privacy conventions, preventing common pitfalls related to authentication, multi-tenancy, and contractor privacy.

Core Features & Use Cases

  • Auth Enforcement: Guarantees the use of secure NextAuth cookie sessions and proper API authentication patterns.
  • Privacy Protection: Prevents accidental exposure of contractor identities and enforces role-based access control.
  • Workflow Compliance: Guides developers through the correct implementation steps and verification checks.
  • Use Case: When implementing a new feature that involves user roles or API access, this Skill acts as a checklist to ensure all security and privacy requirements are met before deployment.

Quick Start

Follow the auth and privacy rules when implementing changes in this repository.

Frequently Asked Questions about nrpg-workflow

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

FAQPage Schema
How do I enforce NextAuth cookie sessions and server-side role checks during development?

To enforce NextAuth cookie sessions and server-side role checks, follow the NRPG workflow conventions by scanning for auth-token usage and verifying server-side checks. This validates secure API authentication patterns and role-based access.

How do I prevent contractor identity exposure in a multi-tenancy application?

Preventing contractor identity exposure requires enforcing privacy guardrails that restrict client-side data access. The workflow validates implementation steps to ensure contractor identities are not accidentally leaked to clients during multi-tenancy feature development.

What is the correct workflow for validating authentication and privacy conventions before deployment?

The correct authentication and privacy workflow involves scanning for auth-token usage, verifying server-side role checks, and running lint, test, and build commands. This ensures all NRPG security and privacy requirements are met before deployment.

Does this workflow guardrail support multi-tenancy role-based access control?

Yes, the workflow guardrail supports multi-tenancy by enforcing server-side role checks and NextAuth cookie sessions. It validates role-based access control implementation to ensure proper privacy and authentication across tenant boundaries.

Why does my NRPG platform feature fail privacy and authentication checks?

NRPG platform features fail privacy and authentication checks when they skip NextAuth cookie sessions or expose contractor identities to clients. The workflow requires scanning auth-token usage and running lint, test, and build commands to prevent these issues.