中文版

Context Minimization Principle (CMP)

Context-Cost-Driven Software Design

Software design is for modification.

Correct modification requires sufficient context.

Good design makes that context cheaper to acquire.

This series examines software design through Context Cost: the cost of acquiring sufficient context for correct modification. The Context Minimization Principle (CMP) is its core principle. Depth, Breadth, and Context Transformation are its analytical tools; boundaries, locality, architecture, testing, and language mechanisms are its applications.

The design objective is to make required context cheaper to acquire. More explicit types, tests, or documentation can serve that objective even when an agent reads more tokens.

The core principle — CMP

For the modifications a system must realistically support, a design is better when the sufficient context required for correct modification is cheaper to acquire.

What CMP contributes

CMP proposes a common evaluation criterion: use it to explain, compare, and sometimes reject familiar design choices for the modifications at hand.

Core Thesis & Contributions →

Citation

The series builds on the fixed Zenodo preprint, published as Context Minimization Principle. For academic or technical writing, cite that edition:

@misc{zhang2026cmp,
  author  = {Zhang, Lianghui},
  title   = {Context Minimization Principle},
  year    = {2026},
  version = {v1.0.1},
  doi     = {10.5281/zenodo.21331759},
  url     = {https://doi.org/10.5281/zenodo.21331759},
  note    = {Preprint},
}

Zenodo preprint (DOI) · GitHub repository · CITATION.cff

Put CMP into your agent

The series also offers two Agent Skills that apply CMP in Cursor, Claude Code, and other coding agents: a pre-task planner and a post-task reflection loop.

CMP Skills — download & install