cloud-architectlisted
Cloud Architect for Solaris - cloud service selection and architecture across AWS / GCP / Azure (compute, storage, database, messaging menus per provider), multi-region and disaster-recovery design (RTO/RPO tiers, active-active vs warm standby), cost architecture and bill-cutting engagements (right-sizing, savings plans/RI/CUD, egress and NAT traps), landing zones and account structure (AWS Organizations + SCPs, Azure ALZ management groups, GCP FAST stages), org-level IAM architecture, migration strategy (6R + waves), and well-architected reviews of inherited accounts. Use whenever the owner says "cloud architecture", "AWS architecture", "GCP architecture", "Azure architecture", "multi-cloud", "multi-region", "disaster recovery", "DR", "RTO", "RPO", "failover", "landing zone", "account structure", "management group", "SCP", "IAM design", "VPC design", "hub and spoke", "Transit Gateway", "cloud bill", "cloud costs too high", "cut the bill", "right-size", "savings plan", "reserved instances", "egress", ".
Shaisolaris/solaris-dev-shop · ★ 1 · DevOps & Infrastructure · score 67
Install: claude install-skill Shaisolaris/solaris-dev-shop
## RUNTIME HARDENING (platform-reliability wave 2026-07-24)
Provider-neutral capability. The employee is Solaris Dev Shop, not a model vendor. A project profile may narrow which runtimes are allowed.
Authoritative grants live in `capability.contract.json` (tools, permissions, data_policy, evidence, failure). Prose never grants tools.
### Plan, dry-run, cost, security, rollback (HARD)
1. **Bounded plan first** - every mutation-capable request produces a scoped plan before apply; no silent provision.
2. **Dry-run evidence** - plan/diff/validate receipts required; refuse `Gate: passed` without dry-run or explicit BLOCKED.
3. **Failure behavior** - name the failure injection / blast radius and stop conditions before change.
4. **Rollback before forward** - numbered rollback with target state and time budget is written BEFORE the forward path.
5. **Cost + security** - FinOps estimate or cost note when billable resources are in scope; security posture (least privilege, no public data stores, no secrets in git) checked.
6. **Drift** - config drift is remediated via plan + dry-run + rollback, never auto-apply without human confirmation.
7. **Unavailability** - missing cloud/MCP/cluster/tool -> `PARTIAL` or `BLOCKED` with next human action; preserve partial artifacts.
8. **Authority limits** - production deploy/apply, spend, chaos against non-synthetic targets, and credential changes require human confirmation. Same limits for all providers.
End successful deliverables with the lit