cloud-architect

Discover cloud-architecture guidance for deployment planning across AWS, Azure, GCP, Kubernetes, and Terraform.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill cloud-architect-ldilov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloud-architect
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/cloud-architect
Command: npx skills add https://github.com/ldilov/harness-forge --skill cloud-architect-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-discoverable wrapper that surfaces architecture guidance for cloud deployment planning by delegating to the underlying cloud-architect SKILL.

Core Features & Use Cases

  • Auto-discovery of the core cloud-architect SKILL.md and the related references to inform decision making.
  • Activation based on cloud topology, deployment design, distributed systems, or platform reliability concerns across AWS, Azure, GCP, Kubernetes, Terraform, and multi-service rollouts.
  • Use Case: Plan scalable cloud architectures, compare deployment strategies, and validate design choices with architecture-first recommendations.

Quick Start

Invoke the cloud-architect wrapper when planning a cloud deployment to receive architecture guidance.

Frequently Asked Questions about cloud-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan scalable cloud architecture for distributed systems across AWS or Azure?▼

Cloud deployment design guidance is auto-discovered by invoking the cloud-architect wrapper, which surfaces architecture recommendations with explicit trade-offs, risks, and validation steps across AWS, Azure, and GCP.

What is the best way to validate Kubernetes deployment design choices for platform reliability?▼

Kubernetes deployment design choices are validated by retrieving architecture-first recommendations from the cloud-architect wrapper, which provides explicit risks, trade-offs, and validation guidance for multi-service rollouts.

Can I use Terraform topology planning to compare deployment strategies for multi-service rollouts?▼

Yes, Terraform topology planning can compare deployment strategies by leveraging the cloud-architect wrapper to auto-discover architecture guidance, evaluating distributed systems design options and platform reliability concerns with explicit trade-offs.

Does cloud architecture guidance support multi-cloud environments across AWS, Azure, and GCP?▼

Cloud architecture guidance supports multi-cloud environments across AWS, Azure, and GCP by activating the auto-discovery wrapper for cloud topology, deployment design, and distributed systems planning with platform-specific validation recommendations.

When do I need architecture-first recommendations for cloud topology and platform reliability?▼

Architecture-first recommendations for cloud topology are needed when planning scalable distributed systems, designing multi-service rollouts, or validating deployment design choices to ensure platform reliability and mitigate explicit risks across cloud providers.

What trade-offs and risks should I consider when designing distributed systems on Kubernetes?▼

Trade-offs and risks for distributed systems on Kubernetes are surfaced through the cloud-architect wrapper, which returns architecture-oriented recommendations detailing explicit platform reliability concerns, deployment design limitations, and validation guidance.