Well-Architected Guardrails

Well-Architected Guardrails is a DevOps skill for Claude Code, published by aws-samples in sample-well-architected-skills-and-steering.

256 stars42 forkson aws-samples/sample-well-architected-skills-and-steeringAdded 2026/09/02+3% in starsRepository updated 2026/08/27

View source on GitHub Download repo ZIP

ai-coding-agentsampantigravityawsaws-well-architectedclaude-codeclinecodexcursordevops-agentgemini-cligithub-copilotjuniekirokiro-clikiro-ideopenclawskillssteeringwindsurf

Install in seconds

Install Well-Architected Guardrails

Copy Well-Architected Guardrails into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/aws-samples/sample-well-architected-skills-and-steering/tree/main/skills/wa-guardrails ~/.claude/skills/wa-guardrails

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/aws-samples/sample-well-architected-skills-and-steering.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/wa-guardrails/SKILL.md in aws-samples/sample-well-architected-skills-and-steering
Installs to: ~/.claude/skills/wa-guardrails
Collection: One of 6 skills cataloged from this repository
Category: DevOps — 828 skills

What Well-Architected Guardrails does

Well-Architected Guardrails generates preventive and detective AWS controls from an assessment or codebase. Use it to enforce best practices in CI, at deploy time, and continuously so misconfigurations and drift are blocked or flagged.

Well-Architected Guardrails is cataloged under DevOps on DirSkills. Well-Architected Guardrails comes from a repository tagged ai-coding-agents, amp, antigravity, aws and aws-well-architected.

Documentation

README

Excerpt

Well-Architected Guardrails

This skill generates preventive and detective controls that keep a workload Well-Architected over time. Unlike the assessment skills (which find gaps) or remediation (which fixes a specific finding once), guardrails codify best practices so non-compliant changes are blocked or flagged automatically — in CI, at deploy time, and continuously in the account.

What you'll produce: ready-to-commit control files (Config rules, SCPs, CI policy checks, alarms), each tied to the WA Question/Best Practice ID it enforces, with a note on whether the control is preventive (blocks the bad change) or detective (flags it after the fact).

Step 1: Gather context

Ask the user (skip any already provided or inferable from the codebase):

This is the opening of the README. Read the full README on GitHub.

Commands Well-Architected Guardrails provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/aws-well-architected-framework-review

Frequently asked about Well-Architected Guardrails

What else does aws-samples publish alongside Well-Architected Guardrails?
Well-Architected Guardrails is one of 6 skills that DirSkills catalogs from aws-samples/sample-well-architected-skills-and-steering, the repository it ships in. Its siblings there include AWS Well-Architected Review, Example Skill Template and Migration Readiness. Each one is a separate skill with its own page in this directory, installs the same way Well-Architected Guardrails does, and is maintained by aws-samples in that same repository. The rest of the collection is listed on the aws-samples/sample-well-architected-skills-and-steering page.
How does Well-Architected Guardrails compare to other DevOps skills?
Well-Architected Guardrails ranks #732 by stars among the 828 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Well-Architected Guardrails against them. Open each page to compare what they document and how they install.