← ClaudeAtlas

fifteen-factor-applisted

Cloud-native SaaS architecture methodology extending Twelve-Factor with three additional factors (API First, Telemetry, Security). Use when planning SaaS tools, product software architecture, microservices design, PRPs/PRDs, or cloud-native application development; when the user says "fifteen factor", "12 factor", "SaaS architecture", "cloud-native design", "application architecture", "microservices best practices"; or when in a planning/architecture session. Do NOT use for greenfield monolith design without cloud-native constraints, internal tooling that will never ship as a service, or local-only scripts.
henkisdabro/wookstar-claude-plugins · ★ 86 · AI & Automation · score 75
Install: claude install-skill henkisdabro/wookstar-claude-plugins
# Fifteen-Factor App Methodology ## Overview The Fifteen-Factor App methodology extends the original Twelve-Factor App principles (created by Heroku in 2012) with three additional factors essential for modern cloud-native applications: API First, Telemetry, and Security. This methodology provides architectural principles and guidelines for building software-as-a-service applications that are: - **Performant** - Optimised for speed and efficiency - **Scalable** - Designed for horizontal scaling without significant changes - **Manageable** - Easy to deploy, monitor, and maintain - **Resilient** - Robust against failures with graceful degradation ## When to Apply This Methodology Apply the Fifteen-Factor principles during: 1. **Architecture Planning** - When designing new applications or microservices 2. **PRP/PRD Creation** - When documenting technical requirements and specifications 3. **Code Reviews** - When evaluating whether implementations follow best practices 4. **Migration Planning** - When modernising legacy applications for cloud deployment 5. **Technical Debt Assessment** - When identifying architectural improvements ## The Fifteen Factors at a Glance | Factor | Principle | Key Concept | |--------|-----------|-------------| | I. Codebase | One codebase, many deploys | Single repo per app, version controlled | | II. Dependencies | Explicitly declare and isolate | No implicit system-wide packages | | III. Config | Store in environment | Never hardcode configur