architecture-serverless
Architecture Serverless
Overview
Use this skill to design serverless systems that are cost-aware, failure-tolerant, and operationally predictable.
Scope Boundaries
- Traffic is variable or bursty and elastic scaling is valuable.
- Team capacity for infrastructure operations is limited.
- Workloads are naturally event-driven or request/response with bounded execution.
Core Judgments
- Compute model: function granularity, execution time bounds, and concurrency profile.
- State model: where session/process state lives outside function runtime.
- Integration model: event source guarantees, retry semantics, and idempotency.
- Cost model: invocation frequency, cold-start impact, data transfer/storage economics.
Practitioner Heuristics
- Keep functions narrow by business action, not by tiny technical helpers.
- Externalize state deliberately (DB/cache/object store) and design for retries.
- Control concurrency at event source and downstream dependency limits.
- Treat timeouts as business behavior decisions, not only platform defaults.
Workflow
- Profile workload shape and latency/cost sensitivity.
- Design event and request paths with explicit idempotency rules.
- Choose managed services for state, orchestration, and messaging.
- Define concurrency limits and backpressure behavior.
- Model cost and failure behavior under peak and degraded conditions.
- Record escape hatches for workloads that outgrow serverless constraints.
Common Failure Modes
- Hidden coupling through shared environment variables and broad IAM policies.
- Unbounded retries causing duplicate side effects.
- Cost surprises from chatty event chains and storage/egress growth.
Failure Conditions
- Stop when critical workflows cannot tolerate at-least-once delivery semantics.
- Stop when latency SLOs are incompatible with runtime startup behavior.
- Escalate when concurrency or cost risk cannot be bounded.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9