How do I install the Knowledge Twelve Factor skill?

Run npx skillmds@latest add deankelly751/knowledge-twelve-factor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Knowledge Twelve Factor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Knowledge Twelve Factor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Knowledge Twelve Factor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Knowledge Twelve Factor?

DeanKelly751 (@deankelly751) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Knowledge Twelve Factor by deankelly751

Name: Knowledge Twelve Factor
Author: DeanKelly751

Knowledge Twelve Factor

Twelve-Factor App methodology for building cloud-native services. Covers all 12 factors with modern interpretations and practical decision guidance. Use when designing services for cloud deployment, containerization, or reviewing application portability.

DeanKelly751 Updated Sep 21, 2026

File contents

Twelve-Factor App

Purpose

Design applications that are portable, scalable, and suitable for modern cloud platforms.

The Twelve Factors

#	Factor	Principle	Modern interpretation
1	Codebase	One codebase, many deploys	Monorepo or single repo per service
2	Dependencies	Explicitly declare and isolate	Lock files, container images
3	Config	Store in environment	Env vars, config maps, secrets managers
4	Backing services	Treat as attached resources	Connection strings, service discovery
5	Build, release, run	Strict separation of stages	CI/CD pipeline stages
6	Processes	Stateless processes	No sticky sessions, external state stores
7	Port binding	Export services via port	Container port exposure
8	Concurrency	Scale via process model	Horizontal pod autoscaling
9	Disposability	Fast startup, graceful shutdown	Container orchestration, health checks
10	Dev/prod parity	Keep environments similar	Containers, IaC, feature flags
11	Logs	Treat as event streams	stdout/stderr, log aggregation
12	Admin processes	Run as one-off processes	Kubernetes Jobs, migration containers

Most Commonly Violated

Config in code (Factor 3): Hardcoded URLs, credentials in source
Stateful processes (Factor 6): In-memory sessions, local file storage
Dev/prod parity (Factor 10): "Works on my machine" problems
Slow startup (Factor 9): Heavy initialization blocking readiness

When to Bend the Rules

Factor 6 (stateless): Acceptable for single-instance tools, CLIs, PoCs
Factor 8 (concurrency): Vertical scaling is fine when simpler and sufficient
Factor 11 (logs): Structured logging to stdout is the minimum; file-based logs acceptable for local dev

Related Skills

infrastructure/knowledge-cloud-architecture — cloud patterns built on 12-factor
infrastructure/execution-containerization — containers enforce many factors
deployment/execution-cicd-pipeline — factor 5 in practice

---name: knowledge-twelve-factordescription: Twelve-Factor App methodology for building cloud-native services. Covers all 12 factors with modern interpretations and practical decision guidance. Use when designing services for cloud deployment, containerization, or reviewing application portability.---# Twelve-Factor App## PurposeDesign applications that are portable, scalable, and suitable for modern cloud platforms.## The Twelve Factors| # | Factor | Principle | Modern interpretation ||---|--------|-----------|---------------------|| 1 | Codebase | One codebase, many deploys | Monorepo or single repo per service || 2 | Dependencies | Explicitly declare and isolate | Lock files, container images || 3 | Config | Store in environment | Env vars, config maps, secrets managers || 4 | Backing services | Treat as attached resources | Connection strings, service discovery || 5 | Build, release, run | Strict separation of stages | CI/CD pipeline stages || 6 | Processes | Stateless processes | No sticky sessions, external state stores || 7 | Port binding | Export services via port | Container port exposure || 8 | Concurrency | Scale via process model | Horizontal pod autoscaling || 9 | Disposability | Fast startup, graceful shutdown | Container orchestration, health checks || 10 | Dev/prod parity | Keep environments similar | Containers, IaC, feature flags || 11 | Logs | Treat as event streams | stdout/stderr, log aggregation || 12 | Admin processes | Run as one-off processes | Kubernetes Jobs, migration containers |## Most Commonly Violated1. **Config in code** (Factor 3): Hardcoded URLs, credentials in source2. **Stateful processes** (Factor 6): In-memory sessions, local file storage3. **Dev/prod parity** (Factor 10): "Works on my machine" problems4. **Slow startup** (Factor 9): Heavy initialization blocking readiness## When to Bend the Rules- Factor 6 (stateless): Acceptable for single-instance tools, CLIs, PoCs- Factor 8 (concurrency): Vertical scaling is fine when simpler and sufficient- Factor 11 (logs): Structured logging to stdout is the minimum; file-based logs acceptable for local dev## Related Skills- `infrastructure/knowledge-cloud-architecture` — cloud patterns built on 12-factor- `infrastructure/execution-containerization` — containers enforce many factors- `deployment/execution-cicd-pipeline` — factor 5 in practice

Frequently asked questions