This skill provides a systematic thinking framework for deconstructing problems to their fundamental truths and reconstructing solutions under constraints. Based on the SACL (Strip-Atomize-Constraint-Leverage) methodology, it helps you find asymmetric advantages when facing resource limitations (time, money, skills).
Use this skill when:
问题输入 (Problem)
↓
[S] 剥离层 (Strip) → 去除类比/惯例/历史路径
↓
[A] 基元化 (Atomize) → 拆解到不可再分的物理/逻辑单元
↓
[C] 约束映射 (Constraint) → 区分硬约束 vs 软约束
↓
[L] 杠杆重构 (Leverage) → 用现有资源重新组合基元
↓
行动输出 (Action)
Purpose: Clear path dependencies and industry conventions
Self-Check Triad:
Tool: Write a "Taboo List" — list everything "everyone must do" in this industry, then cross each out and ask: "What happens if I don't do this?"
Purpose: Deconstruct until indivisible, but avoid over-decomposition (good enough is enough)
Atomic Unit Criteria:
Quick Decomposition Formula:
Input [X] → through [Y] → transforms to [Z], consuming [Resource W]
Example (SEO Problem):
Key Insight: Algorithm weight (Y) is just an intermediary. The truly indivisible element is the direct match X→Z — this explains why Reddit answers outperform official articles (bypass Y's cold start period).
Domain Atomic Units Reference:
| Domain | Atomic Units | Combination Rules |
|---|---|---|
| -------- | --------------- | ------------------- |
| Physics | Energy, mass, information, spacetime, fundamental forces | Conservation laws, entropy increase, relativity constraints |
| Chemistry | Elements, chemical bonds, crystal defects | Electronegativity, orbital hybridization, thermodynamic equilibrium |
| Biology | DNA, cells, ATP, natural selection | Central dogma, dissipative structures, niche competition |
| Math | Sets, logic operations, functions, axioms | Associativity/distributivity, isomorphism, recursion |
| CS | Bits, Turing machines, logic gates, complexity | Turing completeness, information entropy, abstraction layers |
| Business | Transactions, trust, scarcity, time preference | Comparative advantage, marginal utility, network effects |
| Psychology | Perception, working memory (4±1 chunks), emotion, cognitive bias | Associative learning, reinforcement learning, cognitive dissonance |
| Sociology | Individuals, connections (strong/weak ties), consensus, power | Dunbar's number (150), structural holes, social identity |
Purpose: Distinguish "real obstacles" from "fake obstacles", turn real constraints into design parameters
Constraint Classification Table:
| Hard Constraints (Physical/Logical) | Soft Constraints (Resources/Conventions) | Pseudo-Constraints (Cognitive Myths) |
|---|---|---|
| ------------------------------------- | ------------------------------------------ | -------------------------------------- |
| Time irreversibility | Limited funds | "Must build own traffic" |
| Finite attention | Single skill | "Must use professional PR" |
| Light speed/bandwidth limits | Limited connections | "Must have authority before doing SEO" |
| Thermodynamics (2nd law) | Geographic location | "Content must be on my domain" |
| Google sandbox period (6-12 months) | Zero budget | "Must pay for ads to promote" |
Operation: Transform soft constraints into resource equations:
I have [A time] + [B skills] + [C existing assets], need to produce [D results]
Find: Non-linear leverage points — combinations where 20% resources yield 80% results
Purpose: Build asymmetric advantages within constraints using atomic units
Four Leverage Patterns:
Before starting any problem-solving with first principles:
☐ Can I describe the minimum closed loop of this domain in one sentence?
Example: Business = Value Creation + Value Capture
☐ Are there mathematically inviolable theorems?
Example: Shannon limit in communication, Halting Problem in computation
☐ If all existing solutions were erased, which steps are absolutely essential to rebuild from stone age?
(Remove historical path dependencies)
☐ Which "common sense" elements are actually analogies/metaphors rather than atomic units?
Example: "Website authority" is analogy; "Eigenvector of link graph" is the atomic unit
This sub-problem is:
├── Temporarily don't know, but can learn?
│ → Create learning plan, set deadline
├── Already solved by others, can acquire?
│ → Purchase / Partner / Outsource
├── Truly unsolvable (physical/logical limits)?
│ → Return to upper layer, modify decomposition path or goal
└── Solution cost too high, not worthwhile?
→ Find alternative solutions or narrow problem scope
Match your available resources to strategy:
| Your Resource | Leverage Strategy | Avoid |
|---|---|---|
| --------------- | ------------------- | ------- |
| Abundant time | Do depth, automation, long-term assets | Manual grunt work (e.g., 1000 forum posts) |
| Coding ability | Tools generate content/data for natural spread | Pure tech blogs (unless solving specific problems) |
| Strong writing | Write "answers" on platforms, "systems" on your site | Stack articles on low-traffic site waiting for visitors |
| Weak connections | Use "data/insights" as social currency instead of networking | Cold email asking for shares (no trust atomic unit) |
> First principles doesn't make you omniscient — it makes you the optimal designer under specific constraints.
Your limitations ("can only write articles and build small tools") are not flaws — they are precisely defined design parameters. With these parameters, you can design solutions that large companies cannot replicate (because they have budgets and disdain for this kind of "time-for-space dirty work").
Problem: New website, no authority, zero budget, only time and coding skills
Running SACL Framework:
S (Strip):
A (Atomize):
C (Constraint Mapping):
L (Leverage Reconstruction):
Turn this framework into a template. When facing any difficult problem:
Key mindset: Knowing what you cannot do is equally important as knowing what you can do.
共 1 个版本