ag-referencia-seguranca-rules

Name: ag-referencia-seguranca-rules
Availability: InStock
Author: andregusman-raiz

Enforce RLS, audit trails, LGPD compliance, and PII masking across data systems.

19|4|Updated Mar 7, 2026

Search Tags:#security #rls #compliance #data-protection #audit-trail #lgpd #pii-masking

Ready to run

npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill ag-referencia-seguranca-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ag-referencia-seguranca-rules
Source: https://github.com/andregusman-raiz/a-gusman-claude/tree/main/skills/ag-referencia-seguranca-rules
Command: npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill ag-referencia-seguranca-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes non-negotiable security rules to ensure data protection, auditability, and regulatory compliance across systems.

Core Features & Use Cases

RLS enabled on all tables to enforce row-level access control
Mandatory audit trail with a dedicated audit_logs table storing who, what, when, where, and outcome
LGPD-compliant data handling with data minimization and documented bases
Automatic PII masking in AI contexts and logs
Defined permission levels: superadmin, core_team, external_agent, client
Playbooks and checklists for secure feature development and audits

Quick Start

Load and apply the Security reference rules to your data workflows.

Frequently Asked Questions about ag-referencia-seguranca-rules

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

FAQPage Schema

How do I enforce row-level security and LGPD compliance across my database?▼

You enforce row-level security and LGPD compliance by enabling RLS on all database tables, maintaining a structured audit_logs table, and applying automatic PII masking to ensure data minimization and regulatory adherence.

What is the best way to implement PII masking in AI contexts and application logs?▼

The best way to implement PII masking in AI contexts and logs is by applying standardized security reference rules that automatically detect and redact sensitive personally identifiable information before data reaches processing pipelines.

How do I set up an audit trail that logs who, what, when, where, and outcome for data access?▼

You set up a comprehensive audit trail by creating a dedicated audit_logs table that captures structured logging entries, recording the user, action, timestamp, source, and outcome for every data interaction across your systems.

Does this security rules approach work for both APIs and data processing pipelines?▼

Yes, this security rules approach works for APIs and data processing pipelines by applying universal data handling rules that enforce row-level access control, auditability, and LGPD-compliant data minimization across all system layers.

Can I define custom permission levels like superadmin and external agent for data access?▼

Yes, you can define granular permission levels because the security rules framework explicitly supports structured access tiers including superadmin, core_team, external_agent, and client roles to restrict data visibility appropriately.

When do I need PII masking and structured audit logs for LGPD compliance?▼

You need PII masking and structured audit logs for LGPD compliance whenever your systems process, store, or transmit personally identifiable information, ensuring data minimization, documented legal bases, and full traceability of access events.