Agent skill · software engineering · pproenca
12-factor-app
The Twelve-Factor App methodology for building scalable, maintainable cloud-native applications. Use when designing backend services, APIs, microservices, or any software-as-a-service application. Triggers on deployment patterns, configuration management, process architecture, logging, and infrastructure decisions.
Why this skill is useful
Provides specific deployment patterns and configuration management practices that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-07-24. 192 stars on the source repository.
What this skill does
Community Cloud-Native Applications Best Practices Comprehensive methodology for building modern software-as-a-service applications that are portable, scalable, and maintainable. Contains 51 rules across 12 categories, covering the entire application lifecycle from codebase management to production operations. When to Apply Reference these guidelines when: Designing new backend services or APIs Containerizing applications for Kubernetes or Docker Setting up CI/CD pipelines Managing configuration across environments Implementing logging and monitoring Planning application scaling strategy Debugging deployment or environment issues Rule Categories by Priority Priority Category Impact Prefix ---------- ---------- -------- -------- 1 Codebase & Version Control CRITICAL code- 2 Dependencies CRITICAL dep- 3 Configuration CRITICAL config- 4 Backing Services HIGH svc- 5 Build, Release, Run HIGH build- 6 Processes & State HIGH proc- 7 Concurrency & Scaling HIGH scale- 8 Disposability HIGH disp- 9 Port Binding MEDIUM port- 10 Dev/Prod Parity MEDIUM parity- 11 Logging MEDIUM log- 12 Admin Processes MEDIUM admin- Quick Reference 1. Codebase & Version Control (CRITICAL) code-single-codebase - Maintain one codebase per application in version control code-one-app-one-repo - Enforce one-to-one correlation between codebase and application code-deploys-not-branches - Use deploys not branches to represent environments code-shared-as-libraries - Factor shared code into libraries managed by dependency manager 2. Dependencies (CRITICAL) dep-explicit-declaration - Declare all dependencies explicitly in a manifest file dep-isolate-execution - Isolate dependencies to prevent system package leakage dep-no-system-tools - Never rely on implicit system tools being available dep-deterministic-builds - Use lockfiles for deterministic dependency resolution 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pproenca/12-factor-app