project-domain-rules

Enforce data privacy, political neutrality, and API security invariants for the Political Authority Highlighter platform.

1|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/rodrigorjsf/political-authority-highlighter --skill project-domain-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-domain-rules
Source: https://github.com/rodrigorjsf/political-authority-highlighter/tree/main/.gemini/antigravity/skills/project-domain-rules
Command: npx skills add https://github.com/rodrigorjsf/political-authority-highlighter --skill project-domain-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the core business logic and invariants of the Political Authority Highlighter platform are strictly adhered to, preventing common anti-patterns and ensuring data integrity and user privacy.

Core Features & Use Cases

  • Invariant Enforcement: Guarantees adherence to critical rules like data privacy (CPF non-exposure), political neutrality, and public data sourcing.
  • Code Review Guidance: Provides explicit checklists and anti-patterns to guide developers and reviewers.
  • Use Case: When developing a new API endpoint that exposes politician data, this Skill's rules ensure that sensitive information like CPF numbers is never leaked and that the scoring remains unbiased.

Quick Start

Use the project-domain-rules skill to verify that no sensitive data is exposed in the new API endpoint.

Frequently Asked Questions about project-domain-rules

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

FAQPage Schema
How do I enforce data privacy and prevent sensitive data exposure in API endpoints?

You can enforce data privacy by validating API endpoints against non-negotiable invariants like CPF non-exposure. This guarantees sensitive politician data remains protected and maintains strict user privacy compliance.

What is invariant enforcement for business logic and how does it work?

Invariant enforcement validates business logic, scoring algorithms, and data ingestion against critical domain rules. It guarantees strict adherence to data privacy, political neutrality, and public data sourcing requirements.

How do I ensure political neutrality and unbiased scoring in data processing?

To ensure political neutrality and unbiased scoring, enforce domain rules that validate scoring algorithms against non-negotiable invariants. This prevents common anti-patterns and maintains strict data integrity throughout processing.

Can I use code review checklists to validate frontend security and data ingestion rules?

Yes, code review guidance provides explicit checklists and anti-patterns to validate frontend security and data ingestion. This ensures compliance with critical domain rules like silent exclusion and data availability correlation.

What are the limitations when enforcing domain rules for public data sourcing?

Domain rule enforcement is limited to validating non-negotiable invariants for public data sourcing and data availability correlation. It does not modify data sources but ensures strict compliance with business logic constraints.

When do I need domain rule validation for political authority data platforms?

Domain rule validation is needed when developing API endpoints or data ingestion processes for political authority platforms. It prevents anti-patterns and ensures strict compliance with privacy, neutrality, and sourcing invariants.