Claude Code Plugins

Community-maintained marketplace

Feedback

Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, application methodology, and validation checklist. Version 1.0-beta definitive reference.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name hummbl-framework
description Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, application methodology, and validation checklist. Version 1.0-beta definitive reference.

HUMMBL Base120 Mental Models Framework Skill

Version: 1.0-beta (Definitive Reference)
Source: Google Drive (Created 10/16/2025)
Status: PRODUCTION – DO NOT MODIFY WITHOUT APPROVAL


Overview

Comprehensive reference for the HUMMBL Base120 framework, featuring 120 validated mental models across 6 transformation categories with precise codes, official names, and one-line definitions.
Use this skill for: mental model reference, model selection, transformation analysis, MCP server development, agent training, and problem-solving.

Base120 Architecture

  • 6 Transformations × 20 Models Each = 120 Total Models
  • Coding: [TRANSFORMATION][NUMBER] (e.g., P1, IN15, CO7)
  • Validation Date: October 16, 2025
  • Quality Score: 9.2/10 average
  • Priority Levels: P1–P7 (empirically derived usage frequency)

The 6 Transformations and Models

P — Perspective / Identity (P1–P20)

Transform: Frame and name what is. Anchor or shift point of view.

Code Name One-Line Definition
P1 First Principles Framing Reduce complex problems to foundational truths that cannot be further simplified
P2 Stakeholder Mapping Identify all parties with interest, influence, or impact in a system or decision
P3 Identity Stack Recognize that individuals operate from multiple nested identities simultaneously
P4 Lens Shifting Deliberately adopt different interpretive frameworks to reveal hidden aspects
P5 Empathy Mapping Systematically capture what stakeholders see, think, feel, and do in their context
P6 Point-of-View Anchoring Establish and maintain a consistent reference frame before analysis begins
P7 Perspective Switching Rotate through multiple viewpoints to identify invariants and blind spots
P8 Narrative Framing Structure information as causal stories with conflict, choice, and consequence
P9 Cultural Lens Shifting Adjust communication and interpretation for different cultural contexts and norms
P10 Context Windowing Define explicit boundaries in time, space, and scope for analysis or action
P11 Role Perspective-Taking Temporarily inhabit specific roles to understand constraints and priorities
P12 Temporal Framing Organize understanding across past causes, present states, and future implications
P13 Spatial Framing Scale perspective from local details to global patterns and back
P14 Reference Class Framing Select comparable situations to inform judgment and avoid uniqueness bias
P15 Assumption Surfacing Explicitly identify and document beliefs underlying plans or models
P16 Identity-Context Reciprocity Recognize how identities shape interpretations and contexts reinforce identities
P17 Frame Control & Reframing Consciously select or reshape interpretive frames to enable new solutions
P18 Boundary Object Selection Choose representations that bridge multiple perspectives while remaining meaningful
P19 Sensemaking Canvases Deploy structured templates to systematically capture and organize observations
P20 Worldview Articulation Make explicit the fundamental beliefs and values that drive interpretation and action

IN — Inversion (IN1–IN20)

Transform: Reverse assumptions. Examine opposites, edges, negations.

Code Name One-Line Definition
IN1 Subtractive Thinking Improve systems by removing elements rather than adding complexity
IN2 Premortem Analysis Assume failure has occurred and work backward to identify causes
IN3 Problem Reversal Solve the inverse of the stated problem to reveal insights
IN4 Contra-Logic Argue the opposite position to stress-test assumptions and expose weak reasoning
IN5 Negative Space Framing Study what is absent rather than what is present
IN6 Inverse/Proof by Contradiction Assume a claim is false, derive logical impossibility, thus proving the claim true
IN7 Boundary Testing Explore extreme conditions to find system limits and breaking points
IN8 Contrapositive Reasoning Use logical equivalence that "if A then B" equals "if not B then not A"
IN9 Backward Induction Begin with desired end state and work backward to determine necessary steps
IN10 Red Teaming Organize adversarial review to find vulnerabilities through simulated attack
IN11 Devil's Advocate Protocol Assign explicit role to argue against group consensus or preferred option
IN12 Failure First Design Begin planning by identifying all possible failure modes and designing to prevent them
IN13 Opportunity Cost Focus Evaluate options by what must be forgone rather than what is gained
IN14 Second-Order Effects (Inverted) Trace negative downstream consequences rather than immediate benefits
IN15 Constraint Reversal Temporarily remove assumed constraints to explore alternative solution space
IN16 Inverse Optimization Maximize worst outcomes to understand system vulnerabilities
IN17 Counterfactual Negation Imagine outcomes if key decision had been reversed
IN18 Kill-Criteria & Stop Rules Define conditions that trigger project termination before launch
IN19 Harm Minimization (Via Negativa) Improve by removing harmful elements rather than adding beneficial ones
IN20 Antigoals & Anti-Patterns Catalog Document failure modes to avoid rather than success patterns to emulate

CO — Composition (CO1–CO20)

Transform: Combine parts into coherent wholes.

Code Name One-Line Definition
CO1 Synergy Principle Design combinations where integrated value exceeds sum of parts
CO2 Chunking Group related elements into meaningful units to reduce cognitive load
CO3 Functional Composition Chain pure operations where output of one becomes input of next
CO4 Interdisciplinary Synthesis Merge insights from distinct fields to generate novel solutions
CO5 Emergence Recognize higher-order behavior arising from component interactions
CO6 Gestalt Integration Perceive and leverage whole patterns rather than isolated components
CO7 Network Effects Exploit increasing value as user base or connections grow
CO8 Layered Abstraction Separate concerns into hierarchical levels with clear interfaces between them
CO9 Interface Contracts Define explicit agreements about data structures and behavior between components
CO10 Pipeline Orchestration Coordinate sequential stages with explicit handoffs and error handling
CO11 Pattern Composition (Tiling) Combine repeating elements to construct complex structures efficiently
CO12 Modular Interoperability Ensure independent components work together through standardized connections
CO13 Cross-Domain Analogy Transfer solution patterns from one domain to solve problems in another
CO14 Platformization Extract common capabilities into reusable infrastructure serving multiple use cases
CO15 Combinatorial Design Systematically explore option combinations to find optimal configurations
CO16 System Integration Testing Verify assembled components work correctly together, not just in isolation
CO17 Orchestration vs Choreography Choose between centralized coordination or distributed peer-to-peer interaction
CO18 Knowledge Graphing Represent information as interconnected entities and relationships
CO19 Multi-Modal Integration Synthesize information from different sensory or data modalities
CO20 Holistic Integration Unify disparate elements into coherent, seamless whole where boundaries dissolve

DE — Decomposition (DE1–DE20)

Transform: Break complex systems into constituent parts.

Code Name One-Line Definition
DE1 Root Cause Analysis (5 Whys) Iteratively ask why problems occur until fundamental cause emerges
DE2 Factorization Separate multiplicative components to understand relative contribution of each factor
DE3 Modularization Partition system into self-contained units with minimal interdependencies
DE4 Layered Breakdown Decompose from system to subsystem to component progressively
DE5 Dimensional Reduction Focus on most informative variables while discarding noise or redundancy
DE6 Taxonomy/Classification Organize entities into hierarchical categories based on shared properties
DE7 Pareto Decomposition (80/20) Identify vital few drivers producing most impact versus trivial many
DE8 Work Breakdown Structure Hierarchically divide project into deliverable-oriented components with clear ownership
DE9 Signal Separation Distinguish meaningful patterns from random variation or confounding factors
DE10 Abstraction Laddering Move up and down conceptual hierarchy to find appropriate solution level
DE11 Scope Delimitation Define precise boundaries of what is included versus excluded from consideration
DE12 Constraint Isolation Identify specific limiting factor preventing performance improvement
DE13 Failure Mode Analysis (FMEA) Enumerate potential failure points with severity, likelihood, and detectability ratings
DE14 Variable Control & Isolation Hold factors constant to measure single variable's causal impact
DE15 Decision Tree Expansion Map choices and their consequences as branching paths
DE16 Hypothesis Disaggregation Break compound claim into testable sub-hypotheses
DE17 Orthogonalization Ensure factors vary independently without correlation or interdependence
DE18 Scenario Decomposition Partition future possibilities into discrete, mutually exclusive scenarios
DE19 Critical Path Unwinding Trace longest sequence of dependent tasks determining minimum project duration
DE20 Partition-and-Conquer Divide problem into independent subproblems solvable separately then combined

RE — Recursion (RE1–RE20)

Transform: Apply operations iteratively, with outputs becoming inputs.

Code Name One-Line Definition
RE1 Recursive Improvement (Kaizen) Continuously refine process through small, frequent enhancements
RE2 Feedback Loops Create mechanisms where system outputs influence future inputs
RE3 Meta-Learning (Learn-to-Learn) Improve the process of learning itself, not just domain knowledge
RE4 Nested Narratives Structure information as stories within stories for depth and memorability
RE5 Fractal Reasoning Recognize self-similar patterns repeating across different scales
RE6 Recursive Framing Apply mental models to the process of selecting mental models
RE7 Self-Referential Logic Create systems that monitor, measure, or modify themselves
RE8 Bootstrapping Build capability using currently available resources, then use that to build more
RE9 Iterative Prototyping Cycle rapidly through build-test-learn loops with increasing fidelity
RE10 Compounding Cycles Design systems where gains reinforce future gains exponentially
RE11 Calibration Loops Repeatedly check predictions against outcomes to improve forecasting accuracy
RE12 Bayesian Updating in Practice Continuously revise beliefs as new evidence arrives, weighting by reliability
RE13 Gradient Descent Heuristic Iteratively adjust toward improvement, even without perfect knowledge of optimal direction
RE14 Spiral Learning Revisit concepts at increasing depth, building on previous understanding
RE15 Convergence-Divergence Cycling Alternate between expanding possibilities and narrowing to decisions
RE16 Retrospective→Prospective Loop Use systematic reflection on past to inform future planning
RE17 Versioning & Diff Track changes over time and compare versions to understand evolution
RE18 Anti-Catastrophic Forgetting Preserve critical knowledge while adapting to new information
RE19 Auto-Refactor Systematically improve system structure without changing external behavior
RE20 Recursive Governance (Guardrails that Learn) Establish rules that adapt based on their own effectiveness

SY — Meta-Systems (SY1–SY20)

Transform: Understand systems of systems, coordination, and emergent dynamics.

Code Name One-Line Definition
SY1 Leverage Points Identify intervention points where small changes produce disproportionate effects
SY2 System Boundaries Define what is inside versus outside system scope for analysis or design
SY3 Stocks & Flows Distinguish accumulations from rates of change affecting them
SY4 Requisite Variety Match control system's complexity to system being controlled
SY5 Systems Archetypes Recognize recurring dynamic patterns across different domains
SY6 Feedback Structure Mapping Diagram causal loops showing how variables influence each other
SY7 Path Dependence Acknowledge how early decisions constrain future options through accumulated consequences
SY8 Homeostasis/Dynamic Equilibrium Understand self-regulating mechanisms maintaining stable states despite disturbances
SY9 Phase Transitions & Tipping Points Identify thresholds where gradual changes produce sudden qualitative shifts
SY10 Causal Loop Diagrams Visualize circular cause-effect relationships with reinforcing and balancing dynamics
SY11 Governance Patterns Design decision rights, accountability structures, and coordination mechanisms
SY12 Protocol/Interface Standards Specify rules for interaction enabling coordination without central control
SY13 Incentive Architecture Design reward and penalty structures aligning individual actions with system goals
SY14 Risk & Resilience Engineering Build systems that fail gracefully and recover automatically
SY15 Multi-Scale Alignment Ensure strategy, operations, and execution cohere across organizational levels
SY16 Ecosystem Strategy Position organization within network of partners, competitors, and stakeholders
SY17 Policy Feedbacks Anticipate how rules shape behavior, which creates conditions affecting future rules
SY18 Measurement & Telemetry Instrument systems to capture state, changes, and anomalies for informed response
SY19 Meta-Model Selection Choose appropriate framework or tool for specific problem characteristics
SY20 Systems-of-Systems Coordination Manage interactions between independent systems with emergent behaviors

Model Selection Guidance

  • Reference by code (e.g., "P1", "IN15").
  • NEVER substitute generic models ("OODA Loop", "Hanlon's Razor", etc.).
  • Always validate against this document.
  • Quick Selection Table Example
    Problem Type Transformation Example Codes
    Unclear problem definition Perspective P1, P2, P4
    Conventional thinking stuck Inversion IN1, IN2, IN3
    Assembling solutions Composition CO1, CO2, CO4
    Complex system analysis Decomposition DE1, DE2, DE7
    Feedback/issues Recursion RE1, RE2, RE3
    Strategic challenge Meta-Systems SY1, SY2, SY4

Application Methodology

  • Apply transformation templates using verified codes and names.
  • Use one-line definitions for rapid agent coordination and reasoning.
  • Integrate Base120 reference in agent/server model selection.

Validation Checklist

  • Code matches pattern: [P|IN|CO|DE|RE|SY][1–20]
  • Name matches exactly as listed above
  • Model in correct transformation category
  • No generic substitutions (OODA, Hanlon's, Occam's, etc.)

Source & Provenance

  • Authoritative Document: Google Drive link
  • Owner: Reuben Bowlby rpbowlby@gmail.com
  • Validation Date: 2025-10-16
  • Repository: hummbl-dev/hummbl-claude-skills
  • Version: 1.0-beta (Definitive)