Sams Architecture
Automatically triggered when designing system architecture, planning new projects, creating implementation plans, conducting architecture reviews, or auditing existing codebases for consistency. Applies when discussing: system design, technology choices, architectural patterns, infrastructure decisions, API design, testing strategies, CI/CD pipelines, security architecture, or code organization. Works for Python web APIs, infrastructure/DevOps, Garmin/embedded systems, and frontend projects. Distinguishes between personal projects (strict standards) and client work (adaptive approach).
Install
/plugin marketplace add sam-dumont/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sam-dumont/claude-skills --skill sams-architecturegit clone --depth 1 https://github.com/sam-dumont/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/sams-architecture/skills/sams-architecture ~/.claude/skills/sams-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Sam's Architecture Standards This skill codifies Sam's mature architectural patterns developed across 31+ personal projects and several client projects. It automatically applies during project planning, architecture reviews, and codebase audits. --- ## CRITICAL: Zero-Tolerance Anti-Patterns These are **NEVER acceptable** in Sam's personal projects. Flag immediately if detected: ### Over-Engineering Anti-Patterns ❌ **Premature Microservices**: Breaking into microservices before you understand the domain boundaries - Sam's rule: Start monolithic with clear module boundaries, split only when you have operational pain - Example: Don't create separate services for "user-service", "auth-service", "notification-service" in a new project ❌ **YAGNI Violations**: Building features "because we might need them later" - Sam's rule: Build what you need now, refactor when you need more - Example: Don't add multi-tenancy support to a single-user API ❌ **Abstraction Astronauts**: Creating generic frameworks when specific solutions work - Sam's rule: Three uses before abstracting. Copy-paste twice, abstract on third use - Example: Don't create a "BaseAPIClient" with complex inheritance when you have one API client ❌ **Configuration Complexity**: Making everything configurable "for flexibility" - Sam's rule: Hard-code sensible defaults, make configurable only when you need to change it - Example: Don't create config files for things that never change per environment
Details
- Skill name
sams-architecture- Repository
- sam-dumont/claude-skills
- Path
plugins/sams-architecture/skills/sams-architecture/SKILL.md- License
- MIT
- Repo updated
- 3 November 2026
FAQ
What does the Sams Architecture skill do?
Automatically triggered when designing system architecture, planning new projects, creating implementation plans, conducting architecture reviews, or auditing existing codebases for consistency. Applies when discussing: system design, technology choices, architectural patterns, infrastructure decisions, API design, testing strategies, CI/CD pipelines, security architecture, or code organization. Works for Python web APIs, infrastructure/DevOps, Garmin/embedded systems, and frontend projects. Distinguishes between personal projects (strict standards) and client work (adaptive approach).
How do I install the Sams Architecture skill?
Claude Code plugin: /plugin marketplace add sam-dumont/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Sams Architecture popular?
It lives in sam-dumont/claude-skills, which has 38 GitHub stars and 4 forks.
Related skills
Advanced Code Quality
38sam-dumont/claude-skills
Use when going beyond basic linting to enforce advanced Python code quality gates. Triggers on: cognitive complexity, code duplication detection, architectural enforcement, import boundaries, dependency hygiene, test quality beyond coverage, mutation testing, docstring coverage, type coverage, AI-generated code detection, AI slop detection, complexipy, jscpd, import-linter, deptry, diff-cover, mutmut, interrogate, sloppylint, refurb, pylint design checks, wily, radon maintainability, pytestarch, griffe, "bulletproof Python", "tighten quality gates", "advanced quality checks", "beyond ruff and
Code Quality
38sam-dumont/claude-skills
Automatically triggered when setting up Python code quality tooling, configuring linters, adding type checking, improving code standards, running code quality checks, setting up pre-commit hooks, or auditing Python code for quality issues. Applies when discussing: ruff setup, mypy configuration, code formatting, linting rules, cyclomatic complexity, dead code detection, file length limits, pre-commit hooks, Makefile targets for quality, uv-based workflows, pyproject.toml configuration, or "check my code quality". Also triggers on: "set up linting", "add type checking", "configure ruff", "forma
Code Security
38sam-dumont/claude-skills
Automatically triggered when running security scans, auditing code for vulnerabilities, checking dependencies for CVEs, reviewing code for security issues, or hardening Python applications. Applies when discussing: security audit, vulnerability scan, bandit, pip-audit, dependency vulnerabilities, OWASP, injection, path traversal, secrets detection, insecure deserialization, auth bypass, or "is this code secure?". Also triggers on: "run security checks", "find vulnerabilities", "security review", "check for CVEs", "audit dependencies", "security lint", "pen test this code", "harden this applica
Simplifying Control Flow
43obra/clank
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
Safe Refactor
62ElliotJLT/Claude-Skill-Potions
When refactoring, rewriting, or migrating critical code paths, orchestrate a safe cycle: assess risks → implement → verify → document. Chains pre-mortem and prove-it with built-in implementation phase. Prevents "refactor broke production" disasters. Activates on "refactor", "rewrite", "migrate", or "clean up" for non-trivial code.
Single Purpose Variables
43obra/clank
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.