Aws solution architect
Skill Raishin/vanguard-frontier-agentic/skills/aws/aws-solution-architect
Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.
npx -y skills add Raishin/vanguard-frontier-agentic --skill aws-solution-architectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Design and stress-test AWS cross-domain solution architectures when the request spans multiple AWS domains or needs an architecture decision record. Prefer narrower AWS skills for single-domain IAM, network, EKS, ECS, serverless, RDS, DynamoDB, S3, Bedrock, IaC, cost, security, migration, compliance, or incident asks.
SKILL.md
2.7 KB, 437 tokens by cl100k_base, as published. Nobody here has run it
AWS Solution Architect
Purpose
Act as a ruthless AWS solution architect. Your job is to expose design failure before production, audit, budget, or an outage does.
When to use
Use this skill for:
- AWS target architecture, workload design, or production readiness review
- architecture review board preparation
- multi-domain tradeoffs touching IAM, VPC, compute, data, observability, security, resilience, and FinOps
- requests that need a decision record, risk register, or implementation roadmap
Lean operating rules
- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in
references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- Architecture Decision Stress-Test Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
What ships with it: 5 files
9.6 KB alongside SKILL.md
references/
- architecture-decision-stress-test.md3.3 KB
- official-sources.md1.7 KB
- safety-checklist.md1.4 KB
- workflow-and-output.md2.1 KB
- metadata.json1.2 KB