ahu-qa

Validate HVAC equipment designs against requirements and codes from state files.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/toneron2/RWS --skill ahu-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ahu-qa
Source: https://github.com/toneron2/RWS/tree/main/.claude/skills/ahu-qa
Command: npx skills add https://github.com/toneron2/RWS --skill ahu-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs quality assurance and design validation to ensure all aspects of the AHU design meet requirements, codes, and best practices before release.

Core Features & Use Cases

  • Requirements Compliance: Verify specs align with customer request.
  • Code Compliance: Check against ASHRAE and mechanical codes.
  • Documentation Review: Ensure completeness and consistency of state files.
  • Use Case: Generate a QA report confirming that the design passes all checks or highlighting issues for revision.

Quick Start

Run after design and subsystem outputs are generated to produce state/qa.json.

Frequently Asked Questions about ahu-qa

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

FAQPage Schema
How do I validate HVAC AHU designs against code compliance?

AHU validation automates checks against ASHRAE standards and mechanical codes by reading design state files and applying predefined verification criteria. It outputs a structured QA report with PASS, WARNING, and FAIL dispositions across requirements, psychrometric calculations, coil and fan performance, system integration, and safety checks.

What checks does an AHU design validation report include?

AHU validation covers requirements compliance against customer specs, ASHRAE code adherence, psychrometric analysis, coil and fan performance verification, system integration checks, safety validation, and documentation completeness. Each check produces a disposition indicating pass status or issues requiring revision.

When should I run AHU design validation in my workflow?

Run AHU validation after design and subsystem outputs are generated and state files are complete. It produces a structured QA report confirming design compliance or identifying issues for revision before release.

Can AHU validation work with existing design state files?

Yes, AHU validation reads input state files containing design data and applies verification criteria without requiring additional configuration. It processes existing outputs to generate compliance reports.

What does AHU design validation output?

AHU validation outputs state/qa.json, a structured QA report documenting compliance status across all verification categories with PASS, WARNING, or FAIL dispositions for each check.