azure-smart-city-iot-solution-builder
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.
- License 许可
- MIT
- 最近更新
- 2026-08-19
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- azure-smart-city-iot-solution-builder
- description
- 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.
02 资源文件 1
03 SKILL.md 正文
Azure Smart City IoT Solution Builder
Use this skill to rebuild and standardize a complete workflow for Azure IoT and Smart City solutions.
When to use it
Use this skill when the user asks for things like:
- "I want to build an IoT solution on Azure"
- "Smart City architecture for traffic, lighting, or waste"
- "How do I connect devices, analytics, and alerts?"
- "I need a roadmap and backlog for an urban platform"
Objectives
- Convert a high-level idea into a deployable architecture.
- Reuse existing Azure-focused skills whenever possible.
- Produce concrete artifacts the team can implement.
Workflow
0) Mandatory documentation review (before any architecture)
Before proposing architecture or technology decisions that involve edge computing, review Azure IoT Edge documentation first:
Minimum pages to review:
- What is Azure IoT Edge
- Runtime architecture
- Supported systems
- Version history/release notes
- Relevant Linux/Windows quickstarts for the scenario
If documentation cannot be consulted, state this explicitly and continue with clearly marked assumptions.
1) Scope and constraints
Collect and confirm:
- City domain: mobility, parking, air quality, water, energy, public safety, waste, etc.
- Scale: number of devices, telemetry frequency, retention, regions.
- Latency and availability objectives.
- Regulatory and privacy constraints.
- Existing systems to integrate (SCADA, GIS, ERP, ticketing, APIs).
2) Capability map
Split the platform into layers:
- Device and edge: onboarding, identity, firmware, OTA, edge processing.
- Ingestion and messaging: command and control, event routing, buffering.
- Data and analytics: hot path vs cold path, dashboards, historical analysis.
- Operations: observability, incident flow, SLOs.
- Governance: RBAC, secrets, policies, network isolation.
3) Azure service selection (reference)
- Device connectivity: Azure IoT Hub, Azure IoT Operations, IoT Edge.
- Event streaming: Event Hubs, Service Bus, Event Grid.
- Storage: Blob Storage, Data Lake, Cosmos DB, SQL.
- Analytics: Azure Data Explorer, Stream Analytics, Fabric/Synapse.
- APIs and applications: API Management, App Service, Container Apps, Functions.
- Monitoring: Azure Monitor, Application Insights, Log Analytics.
- Security: Key Vault, Defender for IoT, Private Endpoints, Managed Identity.
4) Non-functional design
Define and document:
- Reliability model (zones/regions, retries, dead-letter handling, replay).
- Security controls (zero trust, encryption, secret rotation, least privilege).
- Cost controls (retention tiers, rightsizing, autoscaling, workload scheduling).
- Data lifecycle (raw, curated, aggregated, archived).
5) Delivery plan
Create a phased execution:
- Phase 1: Pilot district or single use case.
- Phase 2: Multi-domain integration.
- Phase 3: City-scale rollout and optimization.
For each phase, include:
- Exit criteria
- Dependencies
- Risks and mitigations
- KPI set
Reuse other skills first
There are two sources of skills:
- Runtime-provided skills (external to this repository): only available when the Copilot host environment exposes them.
- Local repository skills (this repository): available as local files under
skills/.
Runtime-provided Azure skills (optional)
If they are available in the execution environment, delegate to these specialized skills for deeper guidance:
azure-kubernetesazure-messagingazure-observabilityazure-storageazure-rbacazure-costazure-validateazure-deploy
Local repository alternatives (use in this repo)
When runtime skills are not available, prioritize existing local skills in this repository:
azure-architecture-autopilotfor architecture generation and refinement.azure-resource-visualizerfor resource relationship diagrams.azure-role-selectorfor role selection guidance.az-cost-optimizeandazure-pricingfor cost and pricing analysis.azure-deployment-preflightfor pre-deployment checks.appinsights-instrumentationfor telemetry instrumentation patterns.
If no specialized skill is available, continue with this skill and keep assumptions explicit.
Required output artifacts
Always provide these outputs:
- Smart City solution summary (scope, assumptions, constraints).
- Reference architecture (components and data flow).
- Security and governance checklist.
- Cost and scaling strategy.
- Phased implementation backlog (epics and milestones).
Output template
Use references/smart-city-solution-template.md to standardize outputs for each scenario, with this response structure:
- Context and objectives
- Proposed architecture
- Technology decisions and trade-offs
- Security, operations, and cost controls
- Phased implementation plan
- Risks and open questions
Guidelines
- Do not jump to deployment before validating prerequisites.
- Do not recommend single-region production for critical city workloads.
- Do not omit operational ownership (who handles incidents, SLAs, change windows).
- Clearly separate assumptions from confirmed facts.
04 同仓库更多 Skills
youtube-transcript
Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com/watch?v=, youtu.be/, or similar). Supports output with or without timestamps.
youtube-thumbnail-design
YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A/B testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image
youtube-short-maker
Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: "youtube short", "make a youtube short", "shorts video", "short-form video". NOT for long-form or landscape video.
xcode-project-setup
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
x-twitter-scraper
Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.