Aws architecture
Architect AWS infrastructure and application integrations with production-grade service selection, boundaries, rollout thinking, and verification. Use when the user asks for AWS architecture, infra design, service selection, or AWS-backed implementation planning. Do not use for repo-specific Nova guidance unless the active repo adapter calls into it.From its SKILL.md
npx -y skills add BjornMelin/dev-skills --skill aws-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 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.
SKILL.md
1.2 KB, as published. Nobody here has run it
AWS Architecture
Use this skill for reusable AWS architecture work, not repo-specific policy.
Workflow
- Read the repo
AGENTS.md. - Run
~/.codex/skill-support/bin/repo-inventory detect --cwd <repo> --out <json>if the repo context matters. - Read the relevant AWS references before finalizing service choices.
- Prefer managed services and the simplest correct topology.
- 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
What ships with it: 2 files
768 B alongside SKILL.md
agents/
- openai.yaml516 B
references/
- aws-services.md252 B
Gives 0 of the 12 instructions most architecture codebase skills give
Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06
- Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
- Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
- Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
- Document architecture decision recordsin 20 of 858, across 12 files
- Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
- Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
- Write HTML report to the system temp directoryin 17 of 858, across 14 files
- Read product marketing context before asking questionsin 16 of 858, across 6 files
- Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
- Ensure every page has at least one internal linkin 15 of 858, across 5 files
- Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
- Enforce lowercase URLs with hyphensin 15 of 858, across 5 files
Said here and by no other author read
- Read the repository AGENTS.md
- Run the repository inventory tool
- Read relevant AWS references
- Prefer managed services
- Select the simplest correct topology
- Output architecture and tradeoffs
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.