Aws Architecture
- 7 installs
- 5 repo stars
- Updated August 5, 2026
- bjornmelin/dev-skills
Aws-architecture is a Claude Code skill for architecting AWS infrastructure and application integrations with production-grade service selection and rollout planning.
About
Aws-architecture is a Claude Code skill for planning AWS infrastructure and application integrations with production-grade service selection, boundaries, and rollout thinking. Its workflow reads the repo AGENTS.md, optionally runs a repo-inventory detect, consults AWS references, and prefers managed services and the simplest correct topology. It outputs an architecture recommendation, a service map, and a rollout and verification plan. Developers use it for AWS service selection and infra design, not repo-specific policy.
- Guides AWS infrastructure and application-integration architecture decisions
- Prefers managed services and the simplest correct topology
- Outputs an architecture recommendation, service map, and rollout/verification plan
Aws Architecture by the numbers
- 7 all-time installs (skills.sh)
- Ranked #865 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
aws-architecture capabilities & compatibility
- Capabilities
- devops · ci cd
- Works with
- aws
- Use cases
- devops
What aws-architecture says it does
Architect AWS infrastructure and application integrations with production-grade service selection, boundaries, rollout thinking, and verification.
Prefer managed services and the simplest correct topology.
npx skills add https://github.com/bjornmelin/dev-skills --skill aws-architectureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 7 |
|---|---|
| repo stars | ★ 5 |
| Last updated | August 5, 2026 |
| Repository | bjornmelin/dev-skills ↗ |
What it does
Plan AWS infrastructure and service selection with a service map, rollout, and verification plan for a backend build.
Who is it for?
Selecting AWS services and designing a production-grade infra topology with a rollout plan
Skip if: Repo-specific Nova policy, docs-only alignment, or dependency-only work
When should I use this skill?
The user asks for AWS architecture, infra design, service selection, or AWS-backed implementation planning
What you get
A production-grade AWS architecture recommendation with a service map, rollout notes, and verification plan.
- architecture recommendation
- service map
- rollout and verification plan
By the numbers
- 5-step architecture workflow
- 3 named outputs (architecture, service map, rollout/verification)
Files
AWS Architecture
Use this skill for reusable AWS architecture work, not repo-specific policy.
Workflow
1. Read the repo AGENTS.md. 2. Run /home/bjorn/.codex/skill-support/bin/repo-inventory detect --cwd <repo> --out <json> if the repo context matters. 3. Read the relevant AWS references before finalizing service choices. 4. Prefer managed services and the simplest correct topology. 5. Output the architecture, tradeoffs, rollout notes, and verification plan.
Use When
- The task needs AWS service selection or architecture planning.
- The work spans infra design, serverless boundaries, deployment flow, or AWS-backed runtime behavior.
Do Not Use When
- The task is repo-specific Nova policy only.
- The task is only docs alignment or only dependency work.
Outputs
- architecture recommendation
- service map
- rollout and verification plan
interface:
display_name: "AWS Architecture"
short_description: "Plan AWS services, topology, rollout, and verification"
default_prompt: "Use $aws-architecture to choose the simplest strong AWS architecture, explain tradeoffs, and define rollout and verification."
policy:
allow_implicit_invocation: true
dependencies:
tools:
- type: "mcp"
value: "context7"
description: "Current service and library docs"
- type: "mcp"
value: "exa"
description: "Current platform research"
AWS Services
Prefer managed services and clear boundaries. Favor:
1. simple topology 2. least operational burden 3. explicit verification and rollout steps
Avoid inventing custom infrastructure when a managed service already fits the constraint.
Related skills
Azure AiIntegrates Azure AI Content Safety, Document Intelligence, Speech, and Search services into Java-based agents and applications.495k1.4kAzure PrepareGenerate the exact Azure infrastructure files, Dockerfiles, and azure.yaml configuration needed before deploying any new or modernized application.494k1.4kAzure StorageConnect agents and applications to Azure Blob Storage, File Shares, Queues, Tables, and Data Lake without leaving the coding environment.494k1.4kAppinsights InstrumentationAutomatically instrument web applications running on Azure App Service with Application Insights for observability without manual configuration.493k1.4kAzure Resource LookupInstantly list, query, and discover any Azure resources across subscriptions without leaving the agent chat.493k1.4kAzure AigatewayConfigure Azure API Management as a secure, governed gateway for routing traffic to LLMs, MCP servers, and agent tools.493k1.4kFAQ
What does aws-architecture output?
It outputs an architecture recommendation, a service map, and a rollout and verification plan.
When should you not use it?
Do not use it for repo-specific Nova policy only, or when the task is only docs alignment or only dependency work.