rules-data

Route enterprise data rules to Activity Master, EntityAssist, and Database subsystems.

5|Updated Jul 6, 2025
One-click install
npx skills add https://github.com/GuicedEE/ai-rules --skill rules-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rules-data
Source: https://github.com/GuicedEE/ai-rules/tree/main/.claude/skills/rules-data
Command: npx skills add https://github.com/GuicedEE/ai-rules --skill rules-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route enterprise data governance rules to the correct subsystems and ensure consistent policy enforcement across projects, reducing manual mapping and misconfigurations.

Core Features & Use Cases

  • Route data rules to Activity Master, EntityAssist, and Database contexts for automated governance and consistent policy application.
  • Reference rule inventory and apply exact file lookups using the rules catalog to avoid duplication and errors.
  • Use cases include compliance reporting, policy enforcement, and data-steward guided rule application across client/core/cerial paths.

Quick Start

Start from ../../../../generative/data/README.md and select the data subsystem before consulting the rules catalog.

Frequently Asked Questions about rules-data

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

FAQPage Schema
How do I enforce enterprise data governance rules across multiple subsystems?

To enforce enterprise data governance rules across multiple subsystems, you route data rules to the appropriate contexts like Activity Master, EntityAssist, and Database, ensuring consistent policy application and reducing manual mapping errors.

What is the best way to route compliance data rules to specific enterprise subsystems?

Routing compliance data rules to specific subsystems involves referencing a rules inventory for exact file lookup and applying routing guidance across client, core, and cerial paths before making any edits to ensure policy adherence.

How do I avoid duplication when applying data rules to database contexts?

To avoid duplication when applying data rules to database contexts, you reference the rules catalog inventory for exact file lookups, ensuring inputs are validated and preventing misconfigurations across enterprise projects.

Can I use a rules inventory for compliance reporting and policy enforcement?

Yes, you can use a rules inventory for compliance reporting and policy enforcement by consulting the data subsystem README, selecting the appropriate context, and applying data-steward guided rules across client, core, and cerial paths.

Do I need to validate inputs before consulting the rules catalog for enterprise governance?

Yes, you must ensure inputs are validated before consulting the rules catalog for enterprise governance, as this confirms the correct data subsystem is selected and prevents errors during rule application across database contexts.

Why does manual mapping cause misconfigurations in enterprise data governance?

Manual mapping causes misconfigurations in enterprise data governance because it lacks automated routing to subsystems like Activity Master and EntityAssist, leading to inconsistent policy enforcement and duplicated rule applications across projects.