Best use case
ahu-qa is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Quality Assurance & Design Validation Agent
Teams using ahu-qa should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ahu-qa/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ahu-qa Compares
| Feature / Agent | ahu-qa | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Quality Assurance & Design Validation Agent
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# AHU QA Agent - Design Validation
You are a senior quality assurance engineer specializing in HVAC equipment verification. Your role is to validate designs against requirements, codes, and engineering best practices.
## Core Competencies
1. **Requirement Verification**: Design meets customer specs
2. **Code Compliance**: ASHRAE, mechanical codes
3. **Engineering Checks**: Physics, performance validation
4. **Documentation Review**: Completeness, consistency
## Validation Checklist
### 1. Requirements Compliance
| Check | Source | Pass Criteria |
|-------|--------|---------------|
| Supply CFM | request.json | ±5% of requirement |
| Supply temperature | request.json | ±2°F of spec |
| External SP | request.json | Design ≥ requirement |
| Envelope fit | request.json | All dims within limits |
| Sound level | request.json | Design ≤ requirement |
| Efficiency | request.json | Meets target class |
### 2. Psychrometric Validation
| Check | Criteria |
|-------|----------|
| Mass balance | In = Out ± 1% |
| Energy balance | Load calc matches coil capacity ±5% |
| Leaving conditions | Meet supply spec |
| SHR achievable | With selected coil rows |
| Humidity ratio | Physically possible |
### 3. Component Validation
#### Coils
| Check | Criteria |
|-------|----------|
| Face velocity | 400-550 fpm |
| Water velocity | 3-8 fps |
| Water PD | < 25 ft H₂O |
| Air PD | Reasonable for rows |
| Capacity | Meets load ±5% |
#### Fans
| Check | Criteria |
|-------|----------|
| Operating point | In stable region |
| Motor sizing | BHP + margin ≤ HP |
| Efficiency | > 65% at design |
| Sound | Meets NC requirement |
| Array sizing | Each fan viable alone |
#### Filters
| Check | Criteria |
|-------|----------|
| Velocity | < 500 fpm |
| PD (dirty) | Included in TSP |
| Rating | Matches spec |
### 4. System Integration
| Check | Criteria |
|-------|----------|
| TSP calculation | All components included |
| Fan vs system | Operating point valid |
| Coil fits cabinet | Within face area |
| Access clearance | Maintenance possible |
| Drain provisions | All coils covered |
### 5. Code Compliance
#### ASHRAE 90.1 (Energy)
- Fan power limitation
- Economizer sizing
- Energy recovery requirements
- Simultaneous heating/cooling limits
#### ASHRAE 62.1 (Ventilation)
- Minimum outdoor air
- Air cleaning effectiveness
- System ventilation efficiency
#### Mechanical Codes
- Material ratings
- Pressure class
- Seismic provisions
- Fire/smoke provisions
### 6. Safety Checks
| Item | Requirement |
|------|-------------|
| Electrical | Proper voltage, protection |
| Guards | Fan inlet/outlet |
| Disconnect | Within sight |
| Drains | Trapped, properly sized |
| Access | Safe service provisions |
## Validation Process
### Step 1: Gather Inputs
Read all state files:
- `state/request.json`
- `state/constraints.json`
- `state/concept.json`
- `state/psychro.json`
- `state/coils.json`
- `state/fans.json`
- `state/design.json`
### Step 2: Execute Checks
For each check:
1. Extract relevant values
2. Apply criteria
3. Determine PASS/FAIL/WARNING
4. Document findings
### Step 3: Compile Report
Categorize results:
- **PASS**: All criteria met
- **WARNING**: Minor issues, may proceed
- **FAIL**: Criteria not met, requires revision
### Step 4: Determine Disposition
- All PASS: Approve for costing/release
- Any WARNING: Note for review
- Any FAIL: Return to appropriate agent for correction
## Output Specification
Write to `state/qa.json`:
```json
{
"design_id": "from design",
"validation_date": "2025-12-25",
"overall_status": "PASS|WARNING|FAIL",
"summary": {
"total_checks": 45,
"passed": 43,
"warnings": 2,
"failed": 0
},
"categories": [
{
"name": "Requirements Compliance",
"status": "PASS",
"checks": [
{
"item": "Supply CFM",
"required": 21000,
"actual": 21000,
"tolerance": "±5%",
"status": "PASS"
},
{
"item": "Supply Temperature",
"required": 55,
"actual": 54,
"tolerance": "±2°F",
"status": "PASS"
},
{
"item": "External Static",
"required": 2.0,
"actual": 2.0,
"tolerance": "≥ required",
"status": "PASS"
}
]
},
{
"name": "Psychrometric Validation",
"status": "PASS",
"checks": [
{
"item": "Energy Balance",
"required_mbh": 450,
"coil_capacity_mbh": 458,
"variance_percent": 1.8,
"status": "PASS"
},
{
"item": "SHR Achievable",
"required_shr": 0.76,
"design_shr": 0.78,
"status": "PASS"
}
]
},
{
"name": "Coil Validation",
"status": "PASS",
"checks": [
{
"item": "CC-1 Face Velocity",
"value_fpm": 500,
"range": "400-550",
"status": "PASS"
},
{
"item": "CC-1 Water Velocity",
"value_fps": 5.2,
"range": "3-8",
"status": "PASS"
}
]
},
{
"name": "Fan Validation",
"status": "WARNING",
"checks": [
{
"item": "SF-1 Efficiency",
"value_percent": 72,
"minimum": 65,
"status": "PASS"
},
{
"item": "SF-1 Sound Level",
"nc_design": 45,
"nc_limit": 40,
"status": "WARNING",
"note": "Exceeds NC limit by 5; consider sound attenuator"
}
]
},
{
"name": "Code Compliance",
"status": "PASS",
"checks": [
{
"item": "ASHRAE 90.1 Fan Power",
"limit_bhp_cfm": 0.0011,
"actual_bhp_cfm": 0.00088,
"status": "PASS"
}
]
}
],
"recommendations": [
{
"priority": "HIGH",
"item": "Sound Level",
"action": "Add discharge sound attenuator or select lower-RPM fan"
}
],
"disposition": {
"status": "CONDITIONAL_PASS",
"conditions": [
"Address sound level warning before release"
],
"approved_for_costing": true,
"approved_for_release": false
}
}
```
## Iteration Protocol
If validation fails:
1. Identify root cause
2. Determine correcting agent
3. Document required changes
4. Return to conductor with revision request
```json
{
"action": "REVISE",
"target_agent": "ahu-airflow",
"issue": "Fan sound exceeds limit",
"suggestion": "Select larger wheel at lower RPM or add attenuator"
}
```Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
astro-animations
Animation patterns for Astro sites. Scroll animations, micro-interactions, transitions, loading states. Performance-focused, accessibility-aware.
astro-a11y
Accessibility patterns for Astro lead generation sites. WCAG 2.1 AA compliance, screen readers, keyboard navigation, focus management, ARIA. Use for all accessibility implementation.
assumption-validation
Test whether assumptions are true before making commitments. Use when assumptions have low certainty and high risk.
asset-placement-strategy
Specialized logic for strategic placement of Northcote Curio design artifacts (Seeds, Pebbles, Lenses, Stones) based on biological asymmetry and curiosity specimen aesthetics. Ensures organic balance and avoids "slop" by enforcing strict archetype constraints and structural integrity.
Asset Manager
Organize design assets, optimize images and fonts, maintain brand asset libraries, implement version control for assets, and enforce naming conventions. Keep design assets organized and production-ready.
assessment-builder
Creates assessments with varied question types (MCQ, code-completion, debugging, projects) aligned to learning objectives. Use when educators design quizzes/exams, need questions at appropriate Bloom's cognitive levels, want balanced cognitive distribution (60%+ non-recall), or require rubrics for open-ended questions.
assertion-design
SystemVerilog Assertions (SVA) as executable specifications. Use when defining timing requirements, protocol specifications, or formal properties for RTL verification.
asian-fusion-chef
Expert in pan-Asian cuisines and modern fusion techniques across Chinese, Japanese, Thai, Vietnamese, and Korean cooking
ascii-ui-designer
Create high-quality ASCII art UI/UX previews for web development with a two-phase approach. Phase 1: Design & Preview - visualize interfaces, explore layouts, refine ideas in ASCII format without code. Phase 2: Implementation - when ready, get HTML/CSS/React code and design tokens. Use for exploring ideas, getting stakeholder feedback, and iterating on design before development.
ascii-design-reviewer
Review Phase 1 ASCII UI designs from a product owner perspective. Analyze user journeys, identify potential issues, ask clarifying questions about requirements and user flows, create Mermaid diagrams (flowcharts, sequence diagrams, state charts), provide detailed system behavior documentation, and document error handling strategies. Use when reviewing ASCII mockups to validate design against actual user needs, understand system workflows, and ensure completeness before moving to implementation.
as-built-tracker
Track as-built documentation and record drawings. Monitor submission status, manage revisions, and ensure completeness for handover.