Turn an urban IoT idea, such as connected lighting or traffic monitoring, into an Azure architecture and delivery plan. Define device connections, data flows, security, operations, cost controls, and phased implementation tasks.
Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts.
Review the instructions the agent will receive before you install.
Use this skill to rebuild and standardize a complete workflow for Azure IoT and Smart City solutions.
Use this skill when the user asks for things like:
Before proposing architecture or technology decisions that involve edge computing, review Azure IoT Edge documentation first:
Minimum pages to review:
If documentation cannot be consulted, state this explicitly and continue with clearly marked assumptions.
Collect and confirm:
Split the platform into layers:
Define and document:
Create a phased execution:
For each phase, include:
There are two sources of skills:
skills/.If they are available in the execution environment, delegate to these specialized skills for deeper guidance:
azure-kubernetesazure-messagingazure-observabilityazure-storageazure-rbacazure-costazure-validateazure-deployWhen runtime skills are not available, prioritize existing local skills in this repository:
azure-architecture-autopilot for architecture generation and refinement.azure-resource-visualizer for resource relationship diagrams.azure-role-selector for role selection guidance.az-cost-optimize and azure-pricing for cost and pricing analysis.azure-deployment-preflight for pre-deployment checks.appinsights-instrumentation for telemetry instrumentation patterns.If no specialized skill is available, continue with this skill and keep assumptions explicit.
Always provide these outputs:
Use references/smart-city-solution-template.md to standardize outputs for each scenario, with this response structure:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.
Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.
Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.
Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.
Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.
Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.