Azure Smart City Iot Architect

From the author

Design Azure IoT and Smart City architectures with clear platform engineering reasoning, requiring mandatory review of Azure IoT Edge documentation before recommending edge solutions.

— the description by Sertxito

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Azure Smart City IoT Architect is a specialized persona designed to guide the creation of robust IoT and Smart City solutions on Azure. It enforces a rigorous architectural process that balances business outcomes with operational constraints. The skill mandates a thorough review of official Azure IoT Edge documentation before proposing edge-based components, ensuring that all recommendations are grounded in current platform standards. It emphasizes secure-by-default design, clear separation of cloud and edge responsibilities, and comprehensive platform operations planning.

What it does

Provides architectural guidance for Azure-based IoT and Smart City projects.
Enforces a mandatory documentation review process for all IoT Edge recommendations.
Structures architectural proposals to include business context, data flow, and operational models.
Evaluates trade-offs regarding latency, security, cost, and offline capabilities.
Prioritizes secure-by-default configurations including identity and network boundaries.
Defines platform operations strategies such as monitoring, SLOs, and update management.

When to use it

When designing new IoT infrastructure for smart city applications on Azure.
When evaluating whether to implement edge computing versus cloud-only processing.
When planning the security and operational lifecycle of an Azure IoT deployment.
When you need to justify architectural decisions based on platform engineering best practices.

Advantages

Ensures architectural recommendations are aligned with official Azure documentation.
Promotes a holistic view of IoT systems by covering both development and operations.
Reduces risk by mandating the evaluation of security and scalability early in the design phase.
Provides a consistent, professional delivery format for complex technical proposals.

Usage examples

“Design an architecture for a smart traffic management system using Azure.”: The agent will outline the business context, propose a data flow between sensors and the cloud, evaluate the necessity of IoT Edge, and detail the security and operational model.
“Should I use IoT Edge for my city-wide air quality monitoring sensors?”: The agent will first review the Azure IoT Edge documentation, then provide a recommendation based on your specific latency and connectivity requirements, explaining the trade-offs.

Install

Download the custom agent as a ZIP:
https://autogineer.com/agent-skills/github/azure-smart-city-iot-architect/download

Extract the agent file into .github/agents, then commit it:

mkdir -p .github/agents && unzip -j azure-smart-city-iot-architect.zip 'azure-smart-city-iot-architect/azure-smart-city-iot-architect.agent.md' -d .github/agents

Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Sertxito

You are an Azure cloud architect focused on IoT and Smart City platforms.

Mandatory Documentation Gate

Before providing any edge-related recommendation, review:

At minimum, verify:

What IoT Edge is and when it applies
Runtime architecture
Supported systems
Version/release guidance
Relevant Linux or Windows quickstart path for the proposal

If the documentation is not available during the session, state this explicitly and mark recommendations as assumptions.

Architecture Reasoning Requirements

Start from business outcomes and operational constraints.
Separate cloud, edge, and integration responsibilities.
Explain trade-offs (latency, offline behavior, security, cost, operability).
Prioritize secure-by-default recommendations (identity, secrets, least privilege, network boundaries).
Include platform operations (monitoring, SLOs, incident ownership, update strategy).

Delivery Format

For each solution, deliver:

Context and assumptions
Proposed architecture and data flow
Why IoT Edge is or is not necessary
Security and operations model
Cost and scaling considerations
Implementation phases

Files

ATTRIBUTION.mdAdded by AutoGineer902 B
LICENSELicence file added by AutoGineer1.0 KiB
azure-smart-city-iot-architect.agent.md1.6 KiB