| name | azure-gcp-de-para-article |
| description | Add or review an Azure-to-GCP service equivalence ("de-para") section in a technical article on orafaelferreira.com — a comparison table plus practical differences, framed as trade-offs rather than marketing claims. Use when writing or updating an article whose primary subject is an Azure resource/service/architecture, or when reviewing Azure-centric technical content for a multi-cloud comparison. |
Azure↔GCP De-Para for Articles
Ported from ai/skills/azure-gcp-de-para-article.SKILL.md into Claude Code skill format.
Pairs with article-authoring-site-context (editorial rules) and mcp-research-orchestrator
(sourcing) — use all three together when writing an Azure-centric article.
When to use
- Writing an article about an Azure resource, service, or architecture
- Updating an existing Azure article to add a multi-cloud comparison
- Reviewing Azure-centric technical text to make GCP equivalences explicit
When not to use
- Articles unrelated to cloud
- Purely opinion pieces with no technical substance
- Comparisons that would require a formal benchmark you don't have real data for
Goal
Every article centered on an Azure service should include a clear de-para with GCP,
highlighting real equivalences, behavioral differences, and the limits of the comparison —
never implying full parity where there isn't any.
Before writing
Load article-authoring-site-context's editorial rules, ai/mcp/source-of-truth-policy.md
for sourcing rules, and TECH_STACK.md for project context.
Required rules
- For every Azure resource that's a primary subject of the article, map the GCP equivalent.
- Always flag partial equivalence — never claim full parity.
- Explain differences across at least 3 dimensions: operation, pricing, technical limits.
