Initial commit
This commit is contained in:
355
commands/cognitive_map.md
Normal file
355
commands/cognitive_map.md
Normal file
@@ -0,0 +1,355 @@
|
||||
---
|
||||
model: claude-opus-4-1
|
||||
allowed-tools: Task, Write, Read, Bash(*), Glob, Grep
|
||||
argument-hint: <concept-area> [--mapping-style=<visualization>] [--depth=<exploration-level>] [--pathway=<learning-approach>]
|
||||
description: Visual understanding relationship mapping with conceptual bridge identification
|
||||
---
|
||||
|
||||
# Cognitive Mapping Engine
|
||||
|
||||
Create visual representations of knowledge relationships, conceptual bridges, and understanding pathways to facilitate learning transfer and pattern recognition. Transform abstract knowledge into concrete visual structures that reveal hidden connections and support deep comprehension.
|
||||
|
||||
## Mapping Style Framework
|
||||
|
||||
### Hierarchical Style (Tree-like knowledge organization)
|
||||
[Extended thinking: Organize concepts in structured hierarchy with clear parent-child relationships and logical categorization. Optimal for understanding domains with clear organizational structure.]
|
||||
|
||||
**Structure Characteristics:**
|
||||
- **Root Concepts**: Fundamental principles that anchor entire knowledge domain
|
||||
- **Branch Categories**: Major subdivisions that organize related concepts
|
||||
- **Leaf Details**: Specific implementations, examples, and concrete applications
|
||||
- **Inheritance Patterns**: How properties and characteristics flow from general to specific
|
||||
- **Abstraction Levels**: Clear distinction between conceptual levels and detail depths
|
||||
|
||||
**Visual Representation:**
|
||||
```
|
||||
Domain Architecture
|
||||
├── Foundational Principles
|
||||
│ ├── Core Concept A
|
||||
│ │ ├── Implementation Pattern 1
|
||||
│ │ ├── Implementation Pattern 2
|
||||
│ │ └── Real-world Application
|
||||
│ └── Core Concept B
|
||||
│ ├── Variation A
|
||||
│ └── Variation B
|
||||
├── Advanced Applications
|
||||
│ ├── Complex Pattern 1
|
||||
│ └── Complex Pattern 2
|
||||
└── Integration Strategies
|
||||
├── Cross-domain Application
|
||||
└── Future Evolution Paths
|
||||
```
|
||||
|
||||
### Network Style (Interconnected concept relationships)
|
||||
[Extended thinking: Map complex interdependencies where concepts connect in multiple ways without clear hierarchy. Optimal for understanding systems with rich interconnections.]
|
||||
|
||||
**Connection Types:**
|
||||
- **Causal Relationships**: How concepts influence or cause other concepts
|
||||
- **Dependency Links**: What concepts require or depend on others
|
||||
- **Similarity Bridges**: How concepts share characteristics or patterns
|
||||
- **Opposition Tensions**: Where concepts create productive tensions or conflicts
|
||||
- **Emergence Paths**: How simple concepts combine to create complex phenomena
|
||||
|
||||
**Visual Representation:**
|
||||
```
|
||||
[Core Concept A] ←→ [Related Concept 1]
|
||||
↕ ↕
|
||||
[Supporting Idea] ←→ [Integration Point] ←→ [Application Domain]
|
||||
↕ ↕ ↕
|
||||
[Implementation] ←→ [Cross-Domain Bridge] ←→ [Future Possibility]
|
||||
```
|
||||
|
||||
### Flow Style (Process and causation mapping)
|
||||
[Extended thinking: Visualize how concepts, information, or processes move and transform over time. Optimal for understanding dynamic systems and temporal relationships.]
|
||||
|
||||
**Flow Elements:**
|
||||
- **Input Sources**: Where processes begin or concepts originate
|
||||
- **Transformation Points**: How concepts change or evolve through processes
|
||||
- **Decision Nodes**: Where different pathways become possible
|
||||
- **Feedback Loops**: How outputs influence inputs and create cycles
|
||||
- **Output Destinations**: Where processes conclude or concepts find application
|
||||
|
||||
**Visual Representation:**
|
||||
```
|
||||
[Initial State] → [Process Step 1] → [Decision Point] → [Outcome A]
|
||||
↓ ↓
|
||||
[Context Input] → [Process Step 2] → [Alternative Path] → [Outcome B]
|
||||
↑ ↑
|
||||
[Feedback Loop] ← [Learning Integration] ← [Synthesis Point]
|
||||
```
|
||||
|
||||
### Matrix Style (Multi-dimensional comparison grids)
|
||||
[Extended thinking: Compare concepts across multiple dimensions simultaneously to reveal patterns and relationships. Optimal for understanding complex trade-offs and multi-criteria analysis.]
|
||||
|
||||
**Matrix Dimensions:**
|
||||
- **Concept Categories**: Different types or classes of concepts being compared
|
||||
- **Evaluation Criteria**: Different dimensions for assessment or analysis
|
||||
- **Context Variables**: Different situations or conditions affecting concept application
|
||||
- **Quality Attributes**: Different characteristics or properties of concepts
|
||||
- **Stakeholder Perspectives**: Different viewpoints on the same concepts
|
||||
|
||||
**Visual Representation:**
|
||||
```
|
||||
| Criteria A | Criteria B | Criteria C
|
||||
Concept 1 | High | Low | Medium
|
||||
Concept 2 | Medium | High | High
|
||||
Concept 3 | Low | Medium | Low
|
||||
Cross-Pattern | Pattern X | Pattern Y | Pattern Z
|
||||
```
|
||||
|
||||
### Journey Style (Learning pathway visualization)
|
||||
[Extended thinking: Map learning progression with waypoints, milestones, and alternative routes. Optimal for understanding skill development and knowledge acquisition paths.]
|
||||
|
||||
**Journey Elements:**
|
||||
- **Starting Point**: Current knowledge state or skill level
|
||||
- **Learning Milestones**: Key understanding achievements along the path
|
||||
- **Skill Checkpoints**: Practical capabilities gained at each stage
|
||||
- **Alternative Routes**: Different approaches to reaching same destination
|
||||
- **Integration Opportunities**: Where different learning paths connect or reinforce
|
||||
|
||||
**Visual Representation:**
|
||||
```
|
||||
[Beginner] → [Foundation] → [Intermediate] → [Advanced] → [Expert]
|
||||
↓ ↓ ↓ ↓ ↓
|
||||
[Practice] → [Pattern Recognition] → [Creative Application] → [Innovation]
|
||||
↑ ↑ ↑ ↑ ↑
|
||||
[Resources] → [Community] → [Projects] → [Mentorship] → [Leadership]
|
||||
```
|
||||
|
||||
## Exploration Depth Framework
|
||||
|
||||
### Surface Level (Basic concept relationships)
|
||||
[Extended thinking: Focus on obvious, direct relationships between concepts without deep analysis. Suitable for initial orientation and basic understanding.]
|
||||
|
||||
**Mapping Focus:**
|
||||
- **Direct Connections**: Immediately obvious relationships between concepts
|
||||
- **Basic Categories**: Simple groupings and classifications
|
||||
- **Primary Functions**: Core purposes and basic applications
|
||||
- **Common Examples**: Familiar instances and straightforward implementations
|
||||
- **Essential Vocabulary**: Key terms and fundamental definitions
|
||||
|
||||
**Exploration Approach:**
|
||||
- Start with most familiar concepts and build outward
|
||||
- Use concrete examples before abstract relationships
|
||||
- Focus on "what" questions before "why" and "how"
|
||||
- Create simple visual structures with clear labels
|
||||
- Emphasize recognition over analysis
|
||||
|
||||
### Structural Level (Pattern and framework mapping)
|
||||
[Extended thinking: Identify underlying patterns, frameworks, and systematic relationships that organize concept domains. Focus on architecture and organizational principles.]
|
||||
|
||||
**Mapping Focus:**
|
||||
- **Pattern Recognition**: Recurring structures and organizational principles
|
||||
- **Framework Integration**: How concepts fit within larger systematic structures
|
||||
- **Design Principles**: Rules and guidelines that govern concept relationships
|
||||
- **Architectural Patterns**: Structural templates that organize complex domains
|
||||
- **System Boundaries**: Where concept domains begin and end
|
||||
|
||||
**Exploration Approach:**
|
||||
- Look for templates and repeating structures across different contexts
|
||||
- Identify principles that govern concept organization
|
||||
- Map concept dependencies and prerequisite relationships
|
||||
- Explore variations of common patterns
|
||||
- Connect structural understanding to practical applications
|
||||
|
||||
### Dynamic Level (Process and interaction flows)
|
||||
[Extended thinking: Understanding how concepts interact over time, including processes, feedback loops, and evolutionary patterns. Focus on change and adaptation.]
|
||||
|
||||
**Mapping Focus:**
|
||||
- **Process Flows**: How concepts transform and evolve over time
|
||||
- **Interaction Patterns**: Dynamic relationships and influence flows
|
||||
- **Feedback Systems**: How concept applications create learning and adaptation
|
||||
- **Evolution Pathways**: How concepts develop and change over time
|
||||
- **Emergence Phenomena**: How simple concepts combine to create complexity
|
||||
|
||||
**Exploration Approach:**
|
||||
- Trace concept evolution through time and context
|
||||
- Map cause-and-effect relationships and influence patterns
|
||||
- Identify feedback loops and self-reinforcing systems
|
||||
- Explore how concepts adapt to different contexts
|
||||
- Connect dynamic understanding to predictive capabilities
|
||||
|
||||
### Meta Level (Learning-about-learning maps)
|
||||
[Extended thinking: Understand how knowledge acquisition works, including learning patterns, knowledge transfer mechanisms, and meta-cognitive processes.]
|
||||
|
||||
**Mapping Focus:**
|
||||
- **Learning Patterns**: How understanding develops and transfers across domains
|
||||
- **Knowledge Structures**: How information organizes in cognitive systems
|
||||
- **Transfer Mechanisms**: How learning in one area affects understanding in another
|
||||
- **Meta-Cognitive Processes**: Awareness and control of learning and thinking
|
||||
- **Wisdom Development**: How knowledge transforms into applicable insight
|
||||
|
||||
**Exploration Approach:**
|
||||
- Map personal learning preferences and effective strategies
|
||||
- Identify knowledge transfer opportunities and bridges
|
||||
- Explore meta-cognitive awareness and self-regulation
|
||||
- Connect learning patterns to domain-specific understanding
|
||||
- Develop strategies for continuous learning optimization
|
||||
|
||||
## Bridge Identification Framework
|
||||
|
||||
### Cross-Domain Connection Recognition
|
||||
[Extended thinking: Identify opportunities to apply understanding from one domain to enhance learning in another domain.]
|
||||
|
||||
**Bridge Types:**
|
||||
- **Structural Analogies**: Similar organizational patterns across different domains
|
||||
- **Process Similarities**: Comparable workflows or methodologies in different contexts
|
||||
- **Principle Transfer**: Fundamental insights that apply across multiple domains
|
||||
- **Pattern Migration**: How successful approaches in one area can inform another
|
||||
- **Conceptual Metaphors**: How familiar concepts help understand unfamiliar ones
|
||||
|
||||
**Recognition Methodology:**
|
||||
1. **Pattern Abstraction**: Extract essential features from domain-specific concepts
|
||||
2. **Similarity Scanning**: Look for comparable patterns in other domains
|
||||
3. **Analogy Testing**: Verify whether similarities support meaningful transfer
|
||||
4. **Application Adaptation**: Modify transferred concepts for new context
|
||||
5. **Integration Validation**: Confirm successful knowledge integration
|
||||
|
||||
### Transfer Facilitation Protocol
|
||||
[Extended thinking: Support successful knowledge transfer between domains through structured bridge-building activities.]
|
||||
|
||||
**Transfer Strategies:**
|
||||
- **Metaphor Development**: Create powerful analogies that connect familiar to unfamiliar
|
||||
- **Example Mapping**: Show parallel applications across different contexts
|
||||
- **Principle Extraction**: Identify underlying rules that transcend specific domains
|
||||
- **Practice Bridging**: Apply transferred knowledge in new contexts with guided support
|
||||
- **Integration Reinforcement**: Strengthen cross-domain connections through repeated application
|
||||
|
||||
**Facilitation Process:**
|
||||
1. **Source Domain Mastery**: Ensure solid understanding of origin concepts
|
||||
2. **Target Domain Introduction**: Provide context for application area
|
||||
3. **Bridge Construction**: Create explicit connections between domains
|
||||
4. **Guided Application**: Support initial attempts at knowledge transfer
|
||||
5. **Independent Practice**: Encourage autonomous application with periodic support
|
||||
|
||||
## Execution Examples
|
||||
|
||||
### Example 1: Software Architecture Understanding
|
||||
```bash
|
||||
cognitive_map "microservices architecture patterns" --mapping-style=network --depth=structural --pathway=visual
|
||||
```
|
||||
|
||||
**Network-Style Structural Mapping:**
|
||||
|
||||
```
|
||||
Service Discovery ←→ Load Balancing ←→ Circuit Breakers
|
||||
↕ ↕ ↕
|
||||
API Gateway ←→ Service Mesh ←→ Observability ←→ Security Patterns
|
||||
↕ ↕ ↕
|
||||
Data Consistency ←→ Event Sourcing ←→ CQRS ←→ Saga Pattern
|
||||
↕ ↕ ↕
|
||||
Deployment ←→ Container Orchestration ←→ Infrastructure as Code
|
||||
```
|
||||
|
||||
**Structural Pattern Recognition:**
|
||||
- **Communication Patterns**: How services interact (sync/async, event-driven, request-response)
|
||||
- **Resilience Patterns**: Fault tolerance through circuit breakers, retries, timeouts
|
||||
- **Data Patterns**: Consistency management through eventual consistency, event sourcing
|
||||
- **Operational Patterns**: Deployment, monitoring, security across distributed systems
|
||||
- **Integration Patterns**: API gateways, service mesh, cross-cutting concerns
|
||||
|
||||
**Cross-Domain Bridge to Traditional Architecture:**
|
||||
- Microservices API Gateway ←→ Monolithic Application Controller Layer
|
||||
- Service-to-Service Communication ←→ Internal Method Calls
|
||||
- Distributed Data ←→ Shared Database with Transactions
|
||||
- Container Orchestration ←→ Application Server Management
|
||||
|
||||
### Example 2: Learning Strategy Development
|
||||
```bash
|
||||
cognitive_map "effective learning techniques" --mapping-style=journey --depth=meta --pathway=experiential
|
||||
```
|
||||
|
||||
**Journey-Style Meta-Level Mapping:**
|
||||
|
||||
```
|
||||
[Unconscious Incompetence] → [Conscious Incompetence] → [Conscious Competence] → [Unconscious Competence]
|
||||
↓ ↓ ↓ ↓
|
||||
[Awareness Building] → [Active Learning] → [Skill Practice] → [Mastery Integration]
|
||||
↓ ↓ ↓ ↓
|
||||
[Curiosity] → [Structured Study] → [Deliberate Practice] → [Teaching Others]
|
||||
↓ ↓ ↓ ↓
|
||||
[Reflection] → [Feedback Seeking] → [Pattern Recognition] → [Innovation]
|
||||
```
|
||||
|
||||
**Meta-Learning Bridge Identification:**
|
||||
- **Spaced Repetition** ←→ **Distributed Practice**: Both leverage memory consolidation timing
|
||||
- **Active Recall** ←→ **Self-Testing**: Both strengthen retrieval pathways
|
||||
- **Interleaving** ←→ **Cross-Training**: Both prevent over-specialization
|
||||
- **Elaborative Rehearsal** ←→ **Conceptual Mapping**: Both build rich knowledge networks
|
||||
|
||||
**Transfer Facilitation to Domain Learning:**
|
||||
- Technical skill development using deliberate practice principles
|
||||
- Language learning through spaced repetition and active recall
|
||||
- Creative skills through interleaving and cross-domain inspiration
|
||||
- Problem-solving through pattern recognition and analogical reasoning
|
||||
|
||||
### Example 3: Business Strategy Relationships
|
||||
```bash
|
||||
cognitive_map "competitive advantage frameworks" --mapping-style=matrix --depth=dynamic --pathway=analytical
|
||||
```
|
||||
|
||||
**Matrix-Style Dynamic Analysis:**
|
||||
|
||||
```
|
||||
| Sustainable | Competitive | Resource | Market
|
||||
| Advantage | Moats | Based | Position
|
||||
Porter's 5 Forces | Medium | High | Low | High
|
||||
Resource-Based View | High | Medium | High | Medium
|
||||
Blue Ocean Strategy | High | High | Medium | High
|
||||
Platform Strategy | High | High | Medium | Medium
|
||||
Dynamic Capabilities| High | Medium | High | Low
|
||||
```
|
||||
|
||||
**Dynamic Flow Integration:**
|
||||
```
|
||||
[Market Analysis] → [Resource Assessment] → [Strategic Choice] → [Implementation]
|
||||
↕ ↕ ↕ ↕
|
||||
[Competitive Intel] → [Capability Building] → [Positioning] → [Performance]
|
||||
↕ ↕ ↕ ↕
|
||||
[Environment Scan] → [Innovation Investment] → [Adaptation] → [Evolution]
|
||||
```
|
||||
|
||||
**Cross-Domain Strategy Bridges:**
|
||||
- **Military Strategy** ←→ **Business Competition**: Terrain analysis, resource allocation, tactical advantage
|
||||
- **Sports Team Strategy** ←→ **Organizational Capability**: Team coordination, skill development, performance optimization
|
||||
- **Ecosystem Biology** ←→ **Market Dynamics**: Niches, competition, symbiosis, adaptation
|
||||
|
||||
## Advanced Mapping Features
|
||||
|
||||
### Interactive Exploration Tools
|
||||
[Extended thinking: Provide dynamic ways to explore and manipulate cognitive maps for deeper understanding.]
|
||||
|
||||
**Exploration Methods:**
|
||||
- **Zoom Navigation**: Drill down from high-level overview to detailed implementation
|
||||
- **Filter Views**: Show/hide different types of relationships or concept categories
|
||||
- **Path Tracing**: Follow specific learning or application pathways through the map
|
||||
- **What-If Analysis**: Explore how changes to one concept affect related concepts
|
||||
- **Historical Evolution**: Show how concept relationships have changed over time
|
||||
|
||||
### Collaborative Mapping
|
||||
[Extended thinking: Enable multiple perspectives to contribute to comprehensive understanding through shared mapping activities.]
|
||||
|
||||
**Collaboration Approaches:**
|
||||
- **Multi-Perspective Integration**: Combine maps from different domain experts or stakeholders
|
||||
- **Consensus Building**: Resolve disagreements about concept relationships through discussion
|
||||
- **Knowledge Synthesis**: Merge individual understanding into collective comprehensive maps
|
||||
- **Peer Learning**: Use map creation as collaborative learning and teaching activity
|
||||
- **Community Validation**: Test map accuracy and usefulness with broader community input
|
||||
|
||||
## Success Indicators
|
||||
|
||||
### Mapping Quality Measures
|
||||
- **Comprehensiveness**: Coverage of relevant concepts and relationships within scope
|
||||
- **Accuracy**: Correct representation of actual concept relationships and dependencies
|
||||
- **Clarity**: Visual organization that supports understanding rather than creating confusion
|
||||
- **Insight Generation**: Maps reveal previously unrecognized patterns or connections
|
||||
- **Transfer Facilitation**: Effective support for knowledge application in new contexts
|
||||
|
||||
### Learning Enhancement
|
||||
- **Understanding Acceleration**: Faster comprehension through visual relationship representation
|
||||
- **Retention Improvement**: Better long-term memory through visual and conceptual organization
|
||||
- **Pattern Recognition**: Enhanced ability to identify similarities and differences across contexts
|
||||
- **Creative Connection**: Increased capacity for innovative thinking through cross-domain bridges
|
||||
- **Meta-Cognitive Development**: Greater awareness of own learning processes and knowledge organization
|
||||
|
||||
The cognitive_map command transforms abstract knowledge into concrete visual structures that reveal hidden relationships, support pattern recognition, and facilitate knowledge transfer across domains through systematic mapping and bridge identification.
|
||||
Reference in New Issue
Block a user