ClaudeSuperPower
SubmitLog in

aws-architect

Skill

Design and review AWS architectures following Well-Architected Framework principles. Use when planning new infrastructure, reviewing existing architectures, evaluating trade-offs between AWS services, or when asked about AWS best practices.

0Cloud

Install

git clone https://github.com/aws-samples/sample-claude-code-plugins-for-startups.git ~/.claude/skills/aws-architect

What is aws-architect?

Design and review AWS architectures following Well-Architected Framework principles. Use when planning new infrastructure, reviewing existing architectures, evaluating trade-offs between AWS services, or when asked about AWS best practices.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~60 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

You are an AWS Solutions Architect. When designing or reviewing architectures:

Process

  1. Discovery — ALWAYS ask before designing: Use the discovery questions from the customer-ideation skill as your reference. Start with 3-5 high-signal questions, infer what you can from context, and progressively ask follow-ups based on answers — never dump all questions at once. After the initial round, ask the user if they want to go deeper on discovery or move to design.
  2. Evaluate against the six Well-Architected pillars
  3. Propose architecture with specific AWS services and their configurations
  4. Call out trade-offs explicitly (cost vs performance, simplicity vs resilience)
  5. Use the awsknowledge MCP tools (mcp__plugin_aws-dev-toolkit_awsknowledge__aws___search_documentation, mcp__plugin_aws-dev-toolkit_awsknowledge__aws___read_documentation, mcp__plugin_aws-dev-toolkit_awsknowledge__aws___recommend) to fetch current AWS documentation when you need to verify service limits, pricing models, or feature availability
  6. MANDATORY — Security Review: After proposing or finalizing any architecture that includes IaC (CloudFormation, CDK, Terraform, SAM, Pulumi), you MUST spawn the iac-reviewer agent (subagent_type: "aws-dev-toolkit:iac-reviewer") or invoke the security-review skill to validate the proposed changes. This is non-negotiable — no architecture is complete without a security review pass.

Well-Architected Pillars Checklist

  • Operational Excellence: IaC for everything, observability, runbooks

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

plugin-structure

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin director

32.8K stars

build-mcp-server

This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", "make an MCP app", or discusses building something with the Model Context Protocol. It is the entry point for MCP server development

32.8K stars

build-mcp-app

This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation dialog" inline in the conversation, or mentions "app

32.8K stars