← ClaudeAtlas

cybernetic-thinkinglisted

Thinking-mode skill for LLMs: installs a control-theoretic and systems-theoretic cognitive operating system distilled from two books — Tsien Hsue-shen & Song Jian's "Engineering Cybernetics" (工程控制论) and Jin Guantao's "Cybernetics and Scientific Methodology" (控制论与科学方法论). Shapes how the LLM reasons about systems, not just how it writes patch diffs. Teaches the model to identify state and possibility space, model the plant as a black-box hypothesis, demand observability and information channels, verify stability and convergence, respect bounds, decouple harm, coordinate benefits, recognize ultra-stability and bifurcations, and close the loop before declaring success. Use when designing architecture, writing complex code, refactoring coupled modules, debugging non-deterministic systems, or any task where "correct AND robust" cannot be verified by a single happy path.
ShrimpLeon/cybernetic-thinking · ★ 2 · Code & Development · score 68
Install: claude install-skill ShrimpLeon/cybernetic-thinking
# Cybernetic Thinking A cybernetic worldview for writing and debugging software, distilled from two books: - Tsien Hsue-shen (钱学森) & Song Jian (宋健), *Engineering Cybernetics* (工程控制论) — the mathematical foundations: stability, feedback, multivariable decoupling, disturbance compensation, bounded control, discrete systems. - Jin Guantao (金观涛), *Cybernetics and Scientific Methodology* (控制论与科学方法论) — the epistemological foundations: possibility space, conjugate control, black-box recognition, information–control dependence, ultra-stability, bifurcation, catastrophe. Language- and framework-agnostic: the "plant" can be a web service, data pipeline, compiler pass, or an LLM agent loop. Self-contained and usable on its own — no other skill required. ## Scope To shape how an LLM agent and a developer think before writing or changing code. Reframe every non-trivial change from "write the smallest patch and hope" to *identify the state and possibility space, model the plant as a black box, measure the trajectory, stabilize the plant, then steer*. Apply whenever the work involves coupled concerns, non-deterministic behavior, or refactoring across module boundaries — anywhere "correct AND robust" cannot be verified by a single happy-path test. Do not replace language frameworks, domain knowledge, or basic software-engineering fundamentals; the control lens is a thinking scaffold, not an implementation library. ## Runtime prompt block Copy the block below into the session b