aria-engineer

Enforce ARIA engineering standards for data integrity and fact-based decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Yoshi-Dai-1/ARIA --skill aria-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aria-engineer
Source: https://github.com/Yoshi-Dai-1/ARIA/tree/main/.agent/skills/aria-engineer
Command: npx skills add https://github.com/Yoshi-Dai-1/ARIA --skill aria-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The ARIA engineering constitution codifies strict guidelines that ensure decisions are based on verifiable facts, prevent undisciplined changes, and embed risk assessment early in the software lifecycle.

Core Features & Use Cases

  • Fact-based decision making: require empirical evidence (code, types, and logs) as the basis for changes.
  • RaW-V discipline: mandate snapshots before destructive ops and rollback on failures.
  • Data integrity enforcement: prohibit silent NaN/Null coercions and enforce strict type handling with validators.
  • Audit-ready governance: provide documented audit methodologies, self-healing hints, and CI safety guards to catch regressions.
  • Use Case: when evolving CatalogManager or snapshotting data, follow these norms to maintain reproducibility and traceability.

Quick Start

Adopt the ARIA Engineer constitution to enforce fact-based decisions and robust data integrity in your codebase.

Frequently Asked Questions about aria-engineer

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

FAQPage Schema
How do I enforce data integrity and prevent silent NaN or Null coercions in Python?

To prevent silent NaN or Null coercions and enforce data integrity, apply strict type handling with Pydantic validators. This prohibits silent coercions and ensures empirical evidence like code and logs supports data changes.

What is RaW-V verification and when do I need snapshots for rollback?

RaW-V verification mandates taking snapshots before destructive operations and rolling back on failures. You need this discipline when evolving components like CatalogManager to maintain reproducibility and traceability.

How do I set up CI safety guards for audit-ready engineering governance?

To set up CI safety guards for audit-ready governance, implement documented audit methodologies and self-healing hints. These guards catch regressions by embedding risk assessment and fact-based decisions in CI pipelines.

Does Pydantic support strict type handling for fact-based engineering decisions?

Yes, Pydantic supports strict type handling for fact-based decisions by enforcing validators that prohibit silent NaN and Null coercions. This ensures changes require empirical evidence from code, types, and logs.

What are the limitations of relying on manual audits for data integrity risk management?

Manual audits lack automated CI safety guards and self-healing hints needed to catch regressions reliably. Without strict type validators and mandated snapshots, manual risk management fails to prevent undisciplined changes and silent coercions.