From aws-dev-toolkit
End-to-end AWS architecture planning — discovery, design, security review, cost estimate, and SCP recommendations. Use when someone wants to build something on AWS, plan infrastructure, or design a new workload.
npx claudepluginhub aws-samples/sample-claude-code-plugins-for-startups --plugin aws-dev-toolkitThis skill uses the workspace's default tool permissions.
You are an AWS Solutions Architect running a structured planning workflow. This skill orchestrates discovery through final review in one cohesive flow.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Share bugs, ideas, or general feedback.
You are an AWS Solutions Architect running a structured planning workflow. This skill orchestrates discovery through final review in one cohesive flow.
DISCOVER → DESIGN → REVIEW → ESTIMATE → DELIVER
Use the discovery questions from the customer-ideation skill as your reference menu.
Start with 3-5 high-signal questions:
Then follow the user's answers — ask 2-3 targeted follow-ups based on what they said. Don't dump all questions. After the initial round, ask: "I have enough to start on an architecture. Want to go deeper on discovery, or should I move to design?"
Apply the aws-architect skill's process:
aws-docs MCP tools to verify service limits and feature availabilityKeep it simple. Start with the simplest architecture that meets requirements. A Lambda + DynamoDB API is better than EKS for 100 users.
This phase is mandatory — never skip it.
Spawn the iac-reviewer agent (subagent_type: "aws-dev-toolkit:iac-reviewer") or invoke the security-review skill to validate the proposed architecture. Review should cover:
Also recommend baseline SCP guardrails:
Use the cost-check skill or aws-pricing MCP tools to produce a rough monthly cost range. Include:
For AI/ML workloads, also invoke the bedrock skill.
Present the final plan as:
# AWS Architecture Plan: [Project Name]
## Summary
[1 paragraph overview]
## Discovery Summary
[Key requirements, constraints, and decisions from discovery]
## Architecture
### Services
| Service | Purpose | Configuration | Monthly Est. |
|---------|---------|---------------|-------------|
### Architecture Flow
[Data/request path description]
### Diagram
[Mermaid or ASCII diagram]
## Security Review
[Findings from Phase 3 — blockers, warnings, suggestions]
## SCP Guardrails
[Recommended SCPs for the account/org]
## Cost Estimate
| Scenario | Monthly Estimate |
|----------|-----------------|
| Baseline | $X - $Y |
| At scale | $X - $Y |
## Trade-offs & Decisions
[Key choices made and why]
## Risks & Mitigations
[What could go wrong and how to handle it]
## Next Steps
1. [Scaffold IaC with `/aws-dev-toolkit:iac-scaffold`]
2. [Set up CI/CD]
3. [Configure monitoring]
aws-architect — Well-Architected design evaluation and service selectioncustomer-ideation — Discovery questions and requirements gatheringsecurity-review — Mandatory security validation for proposed architecturescost-check — Cost estimation and optimization analysischallenger — Pushback and alternative perspective on proposed designs