fifteen-factor-app

Name: fifteen-factor-app
Author: henkisdabro

26installs9forks

How to install fifteen-factor-app?

henkisdabro/wookstar-claude-plugins/fifteen-factor-app

$npx -y skills add henkisdabro/wookstar-claude-plugins --skill fifteen-factor-app

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Fifteen-Factor App Methodology
2
3	## Overview
4
5	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.
6
7	This methodology provides architectural principles and guidelines for building software-as-a-service applications that are:
8
9	- Performant - Optimised for speed and efficiency
10	- Scalable - Designed for horizontal scaling without significant changes
11	- Manageable - Easy to deploy, monitor, and maintain
12	- Resilient - Robust against failures with graceful degradation
13
14	## When to Apply This Methodology
15
16	Apply the Fifteen-Factor principles during:
17
18	1. Architecture Planning - When designing new applications or microservices
19	2. PRP/PRD Creation - When documenting technical requirements and specifications
20	3. Code Reviews - When evaluating whether implementations follow best practices
21	4. Migration Planning - When modernising legacy applications for cloud deployment
22	5. Technical Debt Assessment - When identifying architectural improvements
23
24	## The Fifteen Factors at a Glance
25
26	\| Factor \| Principle \| Key Concept \|
27	\|--------\|-----------\|-------------\|
28	\| I. Codebase \| One codebase, many deploys \| Single repo per app, version controlled \|
29	\| II. Dependencies \| Explicitly declare and isolate \| No implicit system-wide packages \|
30	\| III. Config \| Store in environment \| Never hardcode configuration \|
31	\| IV. Backing Services \| Treat as attached resources \| Databases, caches are swappable resources \|
32	\| V. Build, Release, Run \| Strict separation \| Immutable releases, no runtime changes \|
33	\| VI. Processes \| Stateless and share-nothing \| Horizontal scaling, no sticky sessions \|
34	\| VII. Port Binding \| Export via port \| Self-contained, no runtime injection \|
35	\| VIII. Concurrency \| Scale out via process model \| Horizontal over vertical scaling \|
36	\| IX. Disposability \| Fast startup, graceful shutdown \| Maximise robustness \|
37	\| X. Dev/Prod Parity \| Keep environments similar \| Continuous deployment \|
38	\| XI. Logs \| Treat as event streams \| Separate generation from processing \|
39	\| XII. Admin Processes \| Run as one-off processes \| Same environment as app \|
40	\| XIII. API First \| Design contracts first \| Enable parallel development \|
41	\| XIV. Telemetry \| Monitor everything \| APM, health checks, domain metrics \|
42	\| XV. Security \| Authentication & Authorisation \| RBAC, identity per request \|
43
44	## Architecture Checklist
45
46	When creating a PRP, PRD, or architecture plan, evaluate the design against each factor. Use this checklist for quick validation:
47
48	```
49	□ Single codebase in version control
50	□ All dependencies explicitly declared
51	□ Configuration externalised to environment
52	□ Backing services abstracted and swappable
53	□ Build, release, run stages separated
54	□ Stateless processes (no sticky sessions)
55	□ Services self-contained with port binding
56	□ Designed for horizontal scaling
57	□ Fast startup and graceful shutdown
58	□ Dev/staging/prod environments aligned
59	□ Logs streamed to external aggregator
60	□ Admin tasks automated and reproducible
61	□ API contracts defined before implementation
62	□ Telemetry: APM, health checks, metrics
63	□ Security: Authentication and authorisation
64	```
65
66	## Resources
67
68	Detailed documentation for each factor is available in the references directory:
69
70	- `references/overview.md` - Complete factor summary with diagrams
71	- `references/original-factors.md` - Factors I-XII with implementation examples
72	- `references/modern-extensions.md` - Factors XIII-XV (API First, Telemetry, Security)
73	- `references/setup-and-tools.md` - Tooling recommendations and quick start
74
75	Read the appropriate reference file for detailed guidance on specific factors.

People who liked this also viewed

6 picks

Type

fifteen-factor-app

26installs9forks

View on GitHub

How to install fifteen-factor-app?

henkisdabro/wookstar-claude-plugins/fifteen-factor-app

$npx -y skills add henkisdabro/wookstar-claude-plugins --skill fifteen-factor-app

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Fifteen-Factor App Methodology
2
3	## Overview
4
5	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.
6
7	This methodology provides architectural principles and guidelines for building software-as-a-service applications that are:
8
9	- Performant - Optimised for speed and efficiency
10	- Scalable - Designed for horizontal scaling without significant changes
11	- Manageable - Easy to deploy, monitor, and maintain
12	- Resilient - Robust against failures with graceful degradation
13
14	## When to Apply This Methodology
15
16	Apply the Fifteen-Factor principles during:
17
18	1. Architecture Planning - When designing new applications or microservices
19	2. PRP/PRD Creation - When documenting technical requirements and specifications
20	3. Code Reviews - When evaluating whether implementations follow best practices
21	4. Migration Planning - When modernising legacy applications for cloud deployment
22	5. Technical Debt Assessment - When identifying architectural improvements
23
24	## The Fifteen Factors at a Glance
25
26	\| Factor \| Principle \| Key Concept \|
27	\|--------\|-----------\|-------------\|
28	\| I. Codebase \| One codebase, many deploys \| Single repo per app, version controlled \|
29	\| II. Dependencies \| Explicitly declare and isolate \| No implicit system-wide packages \|
30	\| III. Config \| Store in environment \| Never hardcode configuration \|
31	\| IV. Backing Services \| Treat as attached resources \| Databases, caches are swappable resources \|
32	\| V. Build, Release, Run \| Strict separation \| Immutable releases, no runtime changes \|
33	\| VI. Processes \| Stateless and share-nothing \| Horizontal scaling, no sticky sessions \|
34	\| VII. Port Binding \| Export via port \| Self-contained, no runtime injection \|
35	\| VIII. Concurrency \| Scale out via process model \| Horizontal over vertical scaling \|
36	\| IX. Disposability \| Fast startup, graceful shutdown \| Maximise robustness \|
37	\| X. Dev/Prod Parity \| Keep environments similar \| Continuous deployment \|
38	\| XI. Logs \| Treat as event streams \| Separate generation from processing \|
39	\| XII. Admin Processes \| Run as one-off processes \| Same environment as app \|
40	\| XIII. API First \| Design contracts first \| Enable parallel development \|
41	\| XIV. Telemetry \| Monitor everything \| APM, health checks, domain metrics \|
42	\| XV. Security \| Authentication & Authorisation \| RBAC, identity per request \|
43
44	## Architecture Checklist
45
46	When creating a PRP, PRD, or architecture plan, evaluate the design against each factor. Use this checklist for quick validation:
47
48	```
49	□ Single codebase in version control
50	□ All dependencies explicitly declared
51	□ Configuration externalised to environment
52	□ Backing services abstracted and swappable
53	□ Build, release, run stages separated
54	□ Stateless processes (no sticky sessions)
55	□ Services self-contained with port binding
56	□ Designed for horizontal scaling
57	□ Fast startup and graceful shutdown
58	□ Dev/staging/prod environments aligned
59	□ Logs streamed to external aggregator
60	□ Admin tasks automated and reproducible
61	□ API contracts defined before implementation
62	□ Telemetry: APM, health checks, metrics
63	□ Security: Authentication and authorisation
64	```
65
66	## Resources
67
68	Detailed documentation for each factor is available in the references directory:
69
70	- `references/overview.md` - Complete factor summary with diagrams
71	- `references/original-factors.md` - Factors I-XII with implementation examples
72	- `references/modern-extensions.md` - Factors XIII-XV (API First, Telemetry, Security)
73	- `references/setup-and-tools.md` - Tooling recommendations and quick start
74
75	Read the appropriate reference file for detailed guidance on specific factors.

People who liked this also viewed

6 picks

Type