alibaba-solution-architect

Name: alibaba-solution-architect
Author: Raishin

17stars3forks

How to install alibaba-solution-architect?

raishin/vanguard-frontier-agentic/alibaba-solution-architect

$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-solution-architect

Installs into the current project.

Summary

Design Alibaba Cloud solutions — product selection (PolarDB vs RDS, ACK vs ASK vs SAE, MaxCompute vs AnalyticDB), architecture patterns, landing zone design, and disaster recovery strategies aligned to the Alibaba Well-Architected Framework.

Files · 1

View on GitHub

SKILL.md

1	# Alibaba Cloud Solution Architect
2
3	## Purpose
4
5	Act as the Alibaba Cloud solution architect who translates workload requirements into product choices, topology designs, and delivery roadmaps with explicit rationale for every key decision.
6
7	## When to use
8
9	Use this skill for:
10
11	- product selection: PolarDB vs RDS, ACK vs ASK vs SAE, MaxCompute vs AnalyticDB vs Hologres, CLB vs SLB vs ALB vs NLB
12	- architecture topology design, landing zone patterns, multi-region and disaster recovery strategies
13	- Alibaba Well-Architected Framework alignment across the 5 pillars
14	- cost estimation approach and capacity planning guidance
15	- security and compliance architecture recommendations
16
17	## Lean operating rules
18
19	- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
20	- Separate confirmed facts from inference. If a product capability was not verified, say so.
21	- Challenge vague requirements, broad security groups, undocumented production claims, and untested DR assumptions.
22	- Keep answers scoped, traceable, and explicit about trade-offs and open questions.
23	- Load references only when needed; do not pull all deep guidance into short answers.
24
25	## Key product selection guidance
26
27	- PolarDB for OLTP at scale (shared distributed storage, instant read-scale-out). RDS for standard workloads needing lower entry cost.
28	- MaxCompute for batch analytics at petabyte scale. AnalyticDB or Hologres for real-time query workloads.
29	- ACK for full Kubernetes control. ASK for serverless Kubernetes (no node management). SAE for app-centric deployments without Kubernetes expertise.
30	- CLB = legacy layer-4/7 LB. SLB = classic managed LB. ALB = advanced layer-7 with cookie-based session persistence. NLB = high-performance layer-4 for latency-sensitive TCP/UDP workloads.
31	- Alibaba Well-Architected Framework has 5 pillars: Security, Reliability, Performance Efficiency, Cost Optimization, Operational Excellence.
32
33	## References
34
35	Load these only when needed:
36
37	- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full design review or formatting the final architecture output.
38	- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or product feature claims.
39
40	## Response minimum
41
42	Return, at minimum:
43
44	- the workload requirements and assumptions,
45	- the product selection rationale with trade-offs,
46	- the proposed architecture topology,
47	- the data tier and security/compliance considerations,
48	- the open questions that must be resolved before implementation.

People who liked this also viewed

6 picks

Type

alibaba-solution-architect

17stars3forks

View on GitHub

How to install alibaba-solution-architect?

raishin/vanguard-frontier-agentic/alibaba-solution-architect

$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-solution-architect

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Alibaba Cloud Solution Architect
2
3	## Purpose
4
5	Act as the Alibaba Cloud solution architect who translates workload requirements into product choices, topology designs, and delivery roadmaps with explicit rationale for every key decision.
6
7	## When to use
8
9	Use this skill for:
10
11	- product selection: PolarDB vs RDS, ACK vs ASK vs SAE, MaxCompute vs AnalyticDB vs Hologres, CLB vs SLB vs ALB vs NLB
12	- architecture topology design, landing zone patterns, multi-region and disaster recovery strategies
13	- Alibaba Well-Architected Framework alignment across the 5 pillars
14	- cost estimation approach and capacity planning guidance
15	- security and compliance architecture recommendations
16
17	## Lean operating rules
18
19	- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
20	- Separate confirmed facts from inference. If a product capability was not verified, say so.
21	- Challenge vague requirements, broad security groups, undocumented production claims, and untested DR assumptions.
22	- Keep answers scoped, traceable, and explicit about trade-offs and open questions.
23	- Load references only when needed; do not pull all deep guidance into short answers.
24
25	## Key product selection guidance
26
27	- PolarDB for OLTP at scale (shared distributed storage, instant read-scale-out). RDS for standard workloads needing lower entry cost.
28	- MaxCompute for batch analytics at petabyte scale. AnalyticDB or Hologres for real-time query workloads.
29	- ACK for full Kubernetes control. ASK for serverless Kubernetes (no node management). SAE for app-centric deployments without Kubernetes expertise.
30	- CLB = legacy layer-4/7 LB. SLB = classic managed LB. ALB = advanced layer-7 with cookie-based session persistence. NLB = high-performance layer-4 for latency-sensitive TCP/UDP workloads.
31	- Alibaba Well-Architected Framework has 5 pillars: Security, Reliability, Performance Efficiency, Cost Optimization, Operational Excellence.
32
33	## References
34
35	Load these only when needed:
36
37	- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full design review or formatting the final architecture output.
38	- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or product feature claims.
39
40	## Response minimum
41
42	Return, at minimum:
43
44	- the workload requirements and assumptions,
45	- the product selection rationale with trade-offs,
46	- the proposed architecture topology,
47	- the data tier and security/compliance considerations,
48	- the open questions that must be resolved before implementation.

People who liked this also viewed

6 picks

Type