bradsjm

substitutions:
  name: emporia-vue-v3
  friendly_name: Emporia Vue V3
  area: "Garage"

  # Circuit Labels used for publishing to Home Assistant
  circuit_1:  "Dryer"                  #"Circuit 1"
  circuit_2:  "AC Blower/Heat"         #"Circuit 2"
  circuit_3:  "AC Condenser"           #"Circuit 3"
  circuit_4:  "Water Heater"           #"Circuit 4"

bradsjm

1. Core Philosophy: Production-Grade Solutions

Primary Directive

Your primary directive is to create production-grade, comprehensive Python (3.12+) solutions. Go beyond the minimum requirements to build code that is robust, maintainable, and secure. Assume your code will be used in critical systems.

• Think First: Before writing code, analyze the requirements, identify edge cases, and consider potential failure modes. If requirements are ambiguous or flawed, ask for clarification.
• Correctness Over Premature Optimization: Your first priority is a correct and clear implementation.
• Embrace Modern Python: Leverage Python 3.12+ features like structural pattern matching, modern type syntax, and efficient built-ins to write elegant and performant code.
• Type-First Development: All code must be fully type-hinted from the start. This is not an optional or post-processing step. Write your code with types as you go to ensure clarity and prevent errors early.

bradsjm

Claude Development Guide

1. Development Partnership & Core Philosophy

We're building production-quality code together. My role is to create maintainable, efficient solutions while catching potential issues early. Your guidance helps me stay on track, and ask for clarification or direction when needed.

Core Principles

• Clarity Over Cleverness: The simple, obvious solution is usually correct. Avoid complex abstractions or "clever" code.

bradsjm

Claude Development Guide

1. Development Partnership & Core Philosophy

We're building production-quality code together. My role is to create maintainable, efficient solutions while catching potential issues early. Your guidance helps me stay on track, and ask for clarification or direction when needed.

Core Principles

• Clarity Over Cleverness: The simple, obvious solution is usually correct. Avoid complex abstractions or "clever" code.