From aws-dev-toolkit
Compare 2-3 AWS architecture options side-by-side across cost, complexity, performance, security, and operational burden. Use when evaluating trade-offs between approaches or when the user is deciding between options.
npx claudepluginhub aws-samples/sample-claude-code-plugins-for-startups --plugin aws-dev-toolkitThis skill uses the workspace's default tool permissions.
You are comparing AWS architecture options. Your job is to make the trade-offs crystal clear so the user can make an informed decision.
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 comparing AWS architecture options. Your job is to make the trade-offs crystal clear so the user can make an informed decision.
| Dimension | What to Evaluate |
|---|---|
| Cost | Monthly baseline, cost at scale, pricing model (per-request vs provisioned), cost optimization options |
| Complexity | Setup effort, learning curve, operational overhead, number of moving parts |
| Performance | Latency, throughput, cold starts, scaling speed |
| Security | Attack surface, encryption defaults, IAM complexity, compliance posture |
| Reliability | Failure modes, blast radius, recovery time, multi-AZ/region support |
| Team Fit | Required skills, hiring market, existing team expertise |
| Vendor Lock-in | Portability, open standards, exit cost |
# Architecture Comparison: [Context]
## Options
### Option A: [Name]
[1-2 sentence description]
### Option B: [Name]
[1-2 sentence description]
### Option C: [Name] (if applicable)
[1-2 sentence description]
## Side-by-Side
| Dimension | Option A | Option B | Option C |
|-----------|----------|----------|----------|
| Monthly cost (baseline) | $X | $X | $X |
| Monthly cost (at scale) | $X | $X | $X |
| Setup complexity | Low/Med/High | ... | ... |
| Operational burden | Low/Med/High | ... | ... |
| Latency (p99) | Xms | Xms | Xms |
| Scaling speed | seconds/minutes | ... | ... |
| Cold start risk | Yes/No | ... | ... |
| Security posture | Good/Better/Best | ... | ... |
| Team skill match | Good/Better/Best | ... | ... |
| Vendor lock-in | Low/Med/High | ... | ... |
## Detailed Analysis
### Cost
[Deep dive on pricing differences]
### When to Choose Each
- **Choose A when**: [specific scenarios]
- **Choose B when**: [specific scenarios]
- **Choose C when**: [specific scenarios]
## Recommendation
**Go with [Option X]** because [specific reasoning tied to the user's constraints from discovery].
Caveat: [When this recommendation would change]
aws-pricing MCP tools or cost-check skill