Dex TroveA trove of dexterities for your agents
InstructionMITv1.0.0awesome-copilot

azure-iot-edge-architecture

Require Azure IoT Edge documentation review before proposing edge IoT architectures or Azure implementation guidance.

At a glance

Kind
Instruction · Ananke prompt
Reference
awesome-copilot/azure-iot-edge-architecture · ananke://prompt/awesome-copilot/azure-iot-edge-architecture@1.0.0
Applies to
**/*.bicep,**/*.tf,**/*iot*.md,**/*smart-city*.md,**/*edge*.md
Files
1 · 1.3 KB
How it's used
Instructions apply automatically to files matching their applyTo glob in GitHub Copilot. For Claude Code, reference the file from CLAUDE.md.

Upstream metadata

applyTo**/*.bicep,**/*.tf,**/*iot*.md,**/*smart-city*.md,**/*edge*.md

Documentation

View upstream ↗

Azure IoT Edge Architecture Instruction

When the task includes Azure IoT, Smart City, edge processing, gateway design, or disconnected edge scenarios, do this before providing architecture recommendations:

  1. Review Azure IoT Edge documentation first:
  2. Confirm key constraints from the documentation:
    • Runtime architecture
    • Supported systems
    • Version/release status
    • Relevant Linux/Windows quickstart path
  3. Explicitly state that you reviewed the documentation, or state that it could not be consulted.
  4. If the documentation was not accessible, continue with clearly labeled assumptions.

Response Rules

  • Never jump directly to a list of services without validating edge applicability first.
  • Always explain why IoT Edge is or is not required.
  • Include operational implications: update strategy, observability, and support model.
  • Prioritize secure defaults: managed identity, least privilege, secret management, and network isolation.