Azure Smart City IoT Architect
Azure Smart City IoT Architect是一款design方向的AI技能，核心价值是Design Azure IoT and Smart City architectures with clear platform engineering reasoning, requiring mandatory review of Azure IoT Edge documentation before recommending edge solutions，可用于解决开发者在design领域的实际问题，帮助用户提升效率、自动化重复任务或优化工作流。
Design Azure IoT and Smart City architectures with clear platform engineering reasoning, requiring mandatory review of Azure IoT Edge documentation before recommending edge solutions.
mkdir -p ./skills/azure-smart-city-iot-architect && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/azure-smart-city-iot-architect/SKILL.md -o ./skills/azure-smart-city-iot-architect/SKILL.mdRun in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# Azure Smart City IoT Architect
You are an Azure cloud architect focused on IoT and Smart City platforms.
Mandatory Documentation Gate
Before providing any edge-related recommendation, review:
- https://learn.microsoft.com/azure/iot-edge/
- https://learn.microsoft.com/es-es/azure/iot-edge/
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:
1. Context and assumptions
2. Proposed architecture and data flow
3. Why IoT Edge is or is not necessary
4. Security and operations model
5. Cost and scaling considerations
6. Implementation phases
🎯 Best For
- Engineering teams doing code reviews
- Open source maintainers
- Technical writers
- API documentation teams
- UI designers
💡 Use Cases
- Reviewing pull requests for security vulnerabilities
- Checking code style consistency
- Generating JSDoc/TSDoc comments
- Writing README files for new projects
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Azure Smart City IoT Architect to Your Work
Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.
- 4
Review and Refine
Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.
❓ Frequently Asked Questions
Does this skill check for OWASP Top 10?
Security-focused review skills often include OWASP checks. Check the skill content for specific vulnerability categories covered.
Does it follow my documentation style?
Most documentation skills respect existing style. Provide a style guide or example in your prompt.
Does this work with Figma?
Some design skills integrate with Figma plugins. Check the Works With section for supported tools.
Does Azure Smart City IoT Architect generate production-ready design specs?
It generates detailed specifications that developers can use directly. Review and adjust for your specific design system.
How do I install Azure Smart City IoT Architect?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/azure-smart-city-iot-architect/SKILL.md, ready to use.
⚠️ Common Mistakes to Avoid
Blindly accepting AI suggestions
Always verify AI-generated review comments. Some suggestions may not apply to your specific codebase conventions.
Auto-generating without reviewing
AI documentation can contain inaccuracies. Always verify technical accuracy.
Skipping usability testing
AI-generated designs should be validated with real users before development.
Not reading the full skill
Skills contain important context and edge cases beyond the quick start.