What this prompt does
This prompt asks the AI to design a smart home IoT dashboard across seven modules: a home overview, per-room device controls, an automation rules engine, energy monitoring, a security center, voice assistant integration, and a framework-specific implementation section. It grounds every screen in your product through [product_name], [device_ecosystem], [home_size], and [primary_users], so the AI designs for a brand-agnostic Matter/Zigbee hub rather than a single-vendor app.
The [automation_level] variable is the key lever — it decides whether the rules engine is template-driven for beginners or a Node-RED-style canvas for power users, which changes the whole automation module. And [framework] (defaulting to React + TypeScript + Tailwind + MQTT.js) forces the AI to reason about real-time state, an offline path for locks and lights, and sub-200ms toggle response — the engineering that actually makes a smart home dashboard feel responsive.
When to use it
- You're scoping a smart home control app and need every module mapped before wiring the real-time layer.
- You want the automation rules engine designed for both novices and power users via
[automation_level]. - You're supporting multiple device protocols and need a brand-agnostic device-card pattern.
- You need energy monitoring, security, and voice integration specced as first-class modules.
- You're targeting wall-mounted displays and want touch targets and offline control thought through.
Example output
Expect a structured design document: each module broken into named screens with component detail — a floor-plan overview with device icons, per-room control cards (brightness sliders, thermostat dials, camera grids), a visual IF/THEN rule builder, and energy charts with cost estimates. The closing [framework] section reads as an implementation checklist covering MQTT/WebSocket state updates, offline local-network control, response-time targets, and accessibility — a spec to build against, not finished code.
Pro tips
- Set
[automation_level]deliberately: beginner templates and a Node-RED-style canvas are very different builds, so pick what your users actually need. - Keep
[device_ecosystem]accurate — listing protocols you don't support makes the AI design controls you can't ship. - Use
[primary_users]to split the UX: a power user and a family member need different default views of the same home. - If you're not using MQTT.js, swap
[framework]so the real-time and offline guidance matches your transport. - The offline path for locks and lights is safety-critical — design and test it before trusting the rest.
- Re-prompt module by module after the overview ("expand the Automation Rules Engine to wireframe detail") to go deeper where complexity lives.
