Well Architected
6-pillar architecture review framework. Adapted from AWS Well-Architected for use by great_cto's architect agent on every non-nano ARCH document. Forces explicit answers across operational excellence, security, reliability, performance, cost, and sustainability — not just feature design.
Install
npx skills add jeremybrasher/grokbot-skills --skill well-architectedgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/well-architected ~/.claude/skills/well-architectedPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Well-Architected — 6 pillars to verify before shipping Every ARCH document for non-nano work must answer the 6 pillar questions below. Skipping a pillar is allowed only if explicitly justified (e.g. "Sustainability: N/A — backend-only, runs in shared infra."). This is adapted from AWS Well-Architected (lens: small-team SaaS / LLM applications), trimmed to questions that matter at <10 engineer scale. ## Pillar 1 — Operational excellence ### Questions 1. **Observability:** What metrics, logs, traces do we emit? How do we tell from a dashboard if this is working in prod? 2. **Deployability:** How do we ship a change? CI gates? Rollback path? 3. **Runbooks:** When this breaks at 3am, what does on-call read? ### Pass criteria - ✅ One metric per business outcome (e.g. webhook-deliveries-acked) - ✅ One log line per request, with request-id correlatable across services - ✅ Deploy path is documented and tested (rollback dry-run executed) - ✅ Runbook covers top-3 failure modes from pre-mortem ### Common fail ❌ "We'll add monitoring later." Monitoring is part of the feature. ## Pillar 2 — Security ### Questions 1. **Trust boundaries:** Where does untrusted data enter? How is it validated/sanitized? 2. **Authn / authz:** Who can call this? Who can read/write the data? 3. **Secrets:** Where are API keys, DB passwords, JWT signing keys stored? 4. **Data classification:** PII? PHI? PCI cardholder data? What's the retention policy? ### Pass criteria
Details
- Skill name
well-architected- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/well-architected/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Well Architected skill do?
6-pillar architecture review framework. Adapted from AWS Well-Architected for use by great_cto's architect agent on every non-nano ARCH document. Forces explicit answers across operational excellence, security, reliability, performance, cost, and sustainability — not just feature design.
How do I install the Well Architected skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill well-architected. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Well Architected popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Activity Program Senior
39lionelsimai/claude-skills-collection
Design activity programs for senior engagement. TRIGGERS - Use when user needs help with activity-program-senior related tasks.
Typescript Best Practices
38jeremybrasher/grokbot-skills
TypeScript best practices. Use when reading or editing any .ts or .tsx file. Observe required inputs first; HOLD when they are missing rather than guessing.
Affiliate Program Designer
39lionelsimai/claude-skills-collection
Design affiliate and referral programs with commission structures and partner materials. TRIGGERS - Use when user wants to create an affiliate program, referral system, or partner program.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.