skills.rest
dhruvb14
dhruvb14COMMUNITY
Explore all skills by this author →
GitHub

plenum-architecture-contract

Document critical invariants and design contracts for Plenum smart thermostat architecture.

6|1|Updated Apr 9, 2026
Search Tags:#architecture#software design#home assistant#hvac#temperature units#plenum#cycle engine
One-click install
npx skills add https://github.com/dhruvb14/smart-thermostat-with-vents --skill plenum-architecture-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plenum-architecture-contract
Source: https://github.com/dhruvb14/smart-thermostat-with-vents/tree/main/.claude/skills/plenum-architecture-contract
Command: npx skills add https://github.com/dhruvb14/smart-thermostat-with-vents --skill plenum-architecture-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or inconsistent changes to Plenum by documenting the canonical architecture contracts, invariants, and dependency relationships that keep the smart HVAC zoning system reliable.

Core Features & Use Cases

  • Architecture Guidance: Provides verified component maps, ownership boundaries, and design invariants for Plenum backend, frontend, scheduler, engine, and Home Assistant integrations.
  • Safety Contract Reference: Explains temperature-unit handling, cycle-engine rules, MCP routing, persistence expectations, and known weak points before making changes.
  • Use Case: Use this Skill when modifying temperature fields, HVAC control logic, API routes, database behavior, or integrations and you need to understand the constraints that prevent regressions.

Quick Start

Use the plenum-architecture-contract skill to review the architectural invariants before changing the cycle engine or temperature conversion logic.

Frequently Asked Questions about plenum-architecture-contract

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

FAQPage Schema
How do I safely modify HVAC zoning logic without breaking smart thermostat integrations?▼

Safe HVAC zoning modifications require reviewing documented architecture contracts and design invariants that govern component ownership and safety guard ordering. The Plenum architecture contract provides these verified component boundaries to prevent regressions when changing HVAC control logic.

What are the temperature conversion boundaries in smart thermostat software design?▼

Temperature conversion boundaries define strict ownership limits for temperature-unit handling within the cycle engine and Home Assistant integrations. Documented persistence constraints and scheduler rules ensure temperature fields maintain unit consistency across API routes and database operations.

How does the cycle engine work in HVAC zoning systems with Home Assistant?▼

The cycle engine operates using verified scheduler rules and safety guard ordering to manage HVAC control logic within Home Assistant integrations. Architecture contracts document these cycle-engine rules and MCP routing expectations to prevent unsafe modifications.

Can I change API routes and database behavior in a smart thermostat without causing regressions?▼

Changing API routes and database behavior safely requires adherence to documented persistence constraints and dependency relationships within the thermostat architecture. The architecture contract identifies known weak points and component ownership boundaries to prevent system regressions.

When do I need to review architecture contracts before modifying Home Assistant HVAC integrations?▼

Architecture contracts must be reviewed before any modifications to temperature fields, HVAC control logic, API routes, or database behavior in Home Assistant integrations. The documented invariants and safety guards prevent inconsistent changes to the smart HVAC zoning system.

Why does changing temperature units in my HVAC system cause cycle engine errors?▼

Cycle engine errors occur when temperature-unit handling violates documented conversion boundaries and safety guard ordering within the thermostat architecture. The architecture contract specifies verified component ownership and scheduler rules to maintain temperature consistency.

Related Skills

Explore More Software Engineering Skills→
dhruvb14dhruvb14
6

hvac-zoning-reference

Explain HVAC zoning concepts and safety controls for Plenum thermostat automation.

Community
Advanced
jacob-balslevjacob-balslev
1

performance-engineering

Measure bottlenecks and validate performance changes with regression guards.

Community
Advanced
bolander72bolander72
2

ecobee

Automate Ecobee thermostat control through the Home Assistant REST API.

Community
Intermediate
dhruvb14dhruvb14
6

plenum-failure-archaeology

Retrieve historical Plenum HVAC failure analyses and established fixes.

Community
Advanced