@musashishao/agent-kit 1.0.0 → 1.1.0

package/.agent/skills/problem-solving/collision-zone-thinking.md

@@ -0,0 +1,285 @@
+---
+name: collision-zone-thinking
+parent: problem-solving
+description: Force unrelated concepts together to discover emergent properties. "What if we treated X like Y?"
+---
+
+# Collision Zone Thinking
+
+> Creativity happens at the intersection of unrelated ideas.
+
+## When to Use
+
+- Incremental improvements aren't enough
+- You need a creative breakthrough
+- "We've tried everything" feeling
+- Looking for innovation, not optimization
+
+---
+
+## The 4-Step Process
+
+### Step 1: Define Your Problem Space
+
+```
+What are you trying to solve?
+
+Problem: Onboarding new developers takes 3 weeks
+Current domain: HR, Training, Documentation
+Current solutions: Docs, pair programming, bootcamp
+```
+
+### Step 2: Generate Random Domains
+
+Pick domains COMPLETELY unrelated to your problem:
+
+**Domain Generator (pick 3-5):**
+```
+Entertainment:     Video games, Theme parks, Movies, Music
+Food:             Restaurants, Cooking shows, Farming
+Travel:           Airports, Hotels, Tourism, Maps
+Health:           Hospitals, Gyms, Mental health
+Nature:           Ecosystems, Weather, Evolution
+Sports:           Team sports, Olympics, Training
+Military:         Strategy, Logistics, Training
+Retail:           Shopping malls, E-commerce, Fashion
+Education:        Schools, Universities, Tutoring
+Construction:     Architecture, Building, Infrastructure
+```
+
+**For this example:**
+- Video games
+- Restaurant kitchens
+- Airport security
+- Theme parks
+
+### Step 3: Force Collisions
+
+Take each random domain and FORCE a collision:
+
+---
+
+#### 🎮 "What if developer onboarding was like a VIDEO GAME?"
+
+| Game Element | Onboarding Translation |
+|--------------|----------------------|
+| Tutorial level | First-day guided walkthrough |
+| Quests | Small, clear tasks with completion |
+| XP and leveling | Progress tracking, badges |
+| Achievement unlocks | Access to new repos/systems |
+| NPCs and guides | Bots that answer questions |
+| Multiplayer | Collaborative challenges |
+| Save points | Checkpoints to resume |
+| Difficulty settings | Customize based on experience |
+| Leaderboard | Friendly competition |
+| Boss battles | Major milestone reviews |
+
+**Emergent idea:** "Developer Quest System"
+- Day 1: Complete 3 starting quests (setup, first commit, code review)
+- Week 1: Earn "Backend Badge" by completing module
+- Gamified progress visible to team
+
+---
+
+#### 🍳 "What if developer onboarding was like a RESTAURANT KITCHEN?"
+
+| Kitchen Element | Onboarding Translation |
+|-----------------|----------------------|
+| Station training | Master one area first |
+| Mise en place | Prep environment before "service" |
+| Line cooking | Work alongside experienced "chef" |
+| Restaurant rush | Simulate real workload |
+| Tasting | Code review like dish approval |
+| Recipe cards | Runbooks for common tasks |
+| Sous chef mentorship | Senior dev assigned |
+| Kitchen hierarchy | Clear escalation path |
+
+**Emergent idea:** "Station Mastery"
+- Each new hire masters ONE system first
+- Only move to next "station" when proficient
+- "Sous chef" (senior dev) signs off on each station
+
+---
+
+#### 🛫 "What if developer onboarding was like AIRPORT SECURITY?"
+
+| Airport Element | Onboarding Translation |
+|-----------------|----------------------|
+| Clear checkpoints | Must pass each step |
+| ID verification | Verify credentials/access |
+| Fast lane (PreCheck) | Skip steps if experienced |
+| Screening | Assess skills upfront |
+| Boarding zones | Graduate access by group |
+| Delays | Known blockers flagged early |
+| Information displays | Status visible to all |
+
+**Emergent idea:** "PreCheck for Experienced Hires"
+- Assessment at start to skip known skills
+- "Fast lane" for senior engineers
+- Clear checkpoint status visible
+
+---
+
+#### 🎢 "What if developer onboarding was like a THEME PARK?"
+
+| Theme Park Element | Onboarding Translation |
+|-------------------|----------------------|
+| Park map | Visual overview of journey |
+| Ride height requirements | Prerequisites clearly marked |
+| Fast pass | Priority access for critical paths |
+| Character meet & greet | Meet key team members |
+| Park sections | Themed learning areas |
+| Ride photos | Celebrate completions |
+| Closing time | Time-boxed onboarding |
+
+**Emergent idea:** "Onboarding Theme Park Map"
+- Visual journey map on day 1
+- "Lands" = different tech areas
+- "Rides" = learning experiences
+- "Fast pass" = skip if expert
+
+---
+
+### Step 4: Extract and Combine Best Ideas
+
+| Winning Idea | From Domain | Why It Works |
+|--------------|-------------|--------------|
+| Quest system | Video games | Clear goals, dopamine hits |
+| Station mastery | Kitchen | Deep before broad |
+| PreCheck skip | Airport | Respects prior experience |
+| Visual map | Theme park | Big picture orientation |
+
+**Final Solution: "Developer Quest Park"**
+1. Visual map of entire onboarding journey (theme park)
+2. Quest-based progression with badges (games)
+3. Station mastery: depth before breadth (kitchen)
+4. PreCheck assessment to skip known areas (airport)
+
+**Result:** 3 weeks → 1 week for most developers
+
+---
+
+## Collision Prompt Templates
+
+```
+"What if [YOUR PROBLEM] worked like [RANDOM DOMAIN]?"
+
+Examples:
+- What if code review worked like restaurant quality control?
+- What if deployment worked like a rocket launch?
+- What if debugging worked like medical diagnosis?
+- What if refactoring worked like home renovation?
+- What if meetings worked like improv comedy?
+- What if documentation worked like a museum tour?
+- What if testing worked like flight simulation?
+- What if hiring worked like sports drafting?
+```
+
+---
+
+## Domain Inspiration Cards
+
+Copy and randomly pick one:
+
+```
+🎰 RANDOM DOMAIN PICKER
+
+Roll a number 1-20:
+1.  Cooking competition
+2.  Emergency room
+3.  Orchestra performance
+4.  Space mission
+5.  Detective investigation
+6.  Gardening
+7.  Wedding planning
+8.  Movie production
+9.  Military operation
+10. Stand-up comedy
+11. Fashion runway
+12. Archaeology dig
+13. Video game speedrun
+14. Restaurant reservation
+15. Air traffic control
+16. Book publishing
+17. Music festival
+18. Court trial
+19. Nature documentary
+20. Magic show
+```
+
+---
+
+## Common Collision Discoveries
+
+| Your Problem | Good Collision Domains |
+|--------------|----------------------|
+| User engagement | Games, casinos, social media |
+| Speed/performance | Racing, fast food, emergency services |
+| Quality | Luxury brands, fine dining, craftsmanship |
+| Collaboration | Jazz bands, sports teams, improv |
+| Learning | Schools, games, driving lessons |
+| Scale | Logistics, supply chain, crowds |
+| Trust | Banking, medicine, marriage |
+
+---
+
+## Practice Exercise
+
+### Your Problem:
+> _______________________________________________
+
+### Random Domains (pick 3):
+1. _______________________________________________
+2. _______________________________________________
+3. _______________________________________________
+
+### Collision 1: "What if my problem worked like [Domain 1]?"
+| Domain Element | My Problem Translation |
+|----------------|----------------------|
+| | |
+| | |
+| | |
+
+**Emergent idea:** _______________________________________________
+
+### Collision 2: "What if my problem worked like [Domain 2]?"
+| Domain Element | My Problem Translation |
+|----------------|----------------------|
+| | |
+| | |
+| | |
+
+**Emergent idea:** _______________________________________________
+
+### Best Combined Idea:
+> _______________________________________________
+
+---
+
+## Quick Reference
+
+```
+COLLISION ZONE IN 60 SECONDS:
+
+1. What's my problem?
+   → "I'm trying to improve [X]"
+
+2. What's a random domain?
+   → *pick from list above*
+
+3. Force the collision:
+   → "What if [X] worked like [random domain]?"
+
+4. List elements of that domain:
+   → "In [domain], they have [A], [B], [C]..."
+
+5. Translate each:
+   → "In my problem, that would mean..."
+
+6. Find the gem:
+   → "The interesting idea here is..."
+```
+
+---
+
+> **Remember:** The more unrelated the domain, the more creative the collision. If it feels weird, you're doing it right. The magic happens when you force yourself to translate concepts that "shouldn't" fit.

package/.agent/skills/problem-solving/inversion-exercise.md

@@ -0,0 +1,205 @@
+---
+name: inversion-exercise
+parent: problem-solving
+description: Flip core assumptions to reveal hidden constraints and alternative approaches. "What if the opposite were true?"
+---
+
+# Inversion Exercise
+
+> Challenge every assumption by exploring its opposite.
+
+## When to Use
+
+- You feel stuck because of "the way things are"
+- Conventional approaches have failed
+- You suspect hidden assumptions are blocking you
+- Need a fresh perspective on an old problem
+
+---
+
+## The 4-Step Process
+
+### Step 1: State the Problem Clearly
+
+```
+Write your problem as a simple statement:
+
+"Users are not completing checkout"
+"Our API is too slow"
+"Developers don't write tests"
+"Customers are churning"
+```
+
+### Step 2: List Your Assumptions
+
+Everything you believe to be true about the problem:
+
+```
+Problem: "Users are not completing checkout"
+
+Assumptions:
+1. Users WANT to complete checkout
+2. The checkout flow is too LONG
+3. Users need MORE payment options
+4. PRICE is the main barrier
+5. Users TRUST our site
+6. Mobile experience is GOOD ENOUGH
+7. Users FOUND the right product
+```
+
+### Step 3: Invert Each Assumption
+
+| Original | Inverted | Exploration |
+|----------|----------|-------------|
+| Users want to complete | Users DON'T want to complete | Maybe cart = wishlist, not intent |
+| Checkout is too long | Checkout is too SHORT | Missing trust signals? No confirmation? |
+| Need more options | Need FEWER options | Decision paralysis? |
+| Price is barrier | Price is NOT barrier | Shipping? Trust? Uncertainty? |
+| Users trust us | Users DON'T trust us | New visitors? No reviews shown? |
+| Mobile is good enough | Mobile is TERRIBLE | Test on real devices! |
+| Found right product | Found WRONG product | Are they buying to try? |
+
+### Step 4: Explore the Most Promising
+
+Pick 2-3 inversions that resonate:
+
+```
+Most promising: "Cart = wishlist, not purchase intent"
+
+Evidence:
+- Average cart age is 3 days
+- Users add 5 items, buy 1
+- No "save for later" option
+
+New approach:
+- Add "Save for Later" prominently  
+- Only push checkout when behavior shows intent
+- Send reminders for wishlisted items
+- Reframe cart as "Your Collection"
+```
+
+---
+
+## Inversion Templates
+
+### For Product Problems
+
+| Assumption | Inversion Question |
+|------------|-------------------|
+| Users need this feature | What if this feature makes things worse? |
+| More features = more value | What if fewer features = more value? |
+| Users want control | What if users want automation? |
+| Fast is better | What if slow is better? |
+| Users know what they want | What if users don't know? |
+
+### For Technical Problems
+
+| Assumption | Inversion Question |
+|------------|-------------------|
+| This is a performance problem | What if it's a UX problem? |
+| We need more servers | What if we need fewer requests? |
+| The algorithm is wrong | What if the input is wrong? |
+| We need real-time | What if eventual is fine? |
+| This is a database issue | What if it's a caching issue? |
+
+### For Process Problems
+
+| Assumption | Inversion Question |
+|------------|-------------------|
+| We need more meetings | What if we need fewer meetings? |
+| We need better documentation | What if we need less documentation? |
+| We need more planning | What if we need less planning? |
+| We need more people | What if we need fewer people? |
+| We need to move faster | What if we need to slow down? |
+
+---
+
+## Example: API Performance
+
+### Original Problem
+"Our API is too slow (500ms average response time)"
+
+### Assumptions
+1. 500ms is too slow
+2. Users notice the latency
+3. The bottleneck is in our code
+4. We need to optimize the database
+5. Caching will help
+
+### Inversions
+
+| Assumption | Inversion | Insight |
+|------------|-----------|---------|
+| 500ms is too slow | 500ms is acceptable | Check: Do users actually complain? |
+| Users notice | Users DON'T notice | Perception ≠ reality; test with users |
+| Bottleneck is our code | Bottleneck is ELSEWHERE | Network latency? Client rendering? |
+| Need DB optimization | DB is fine | Profile first; maybe it's JSON serialization |
+| Caching will help | Caching will NOT help | What if requests are unique? |
+
+### Discovery
+After profiling: 400ms was JSON serialization, not database!
+Solution: Switch serializer, 50ms response time.
+The "database optimization" assumption would have wasted weeks.
+
+---
+
+## Warning Signs You Need Inversion
+
+- "Everyone knows that..."
+- "We've always done it this way"
+- "That's just how it works"
+- "Users expect..."
+- "Best practice says..."
+- You've been stuck for > 1 hour
+
+---
+
+## Practice Exercise
+
+### Your Problem
+Write it here:
+> _______________________________________________
+
+### Your Assumptions (list 5)
+1. _______________________________________________
+2. _______________________________________________
+3. _______________________________________________
+4. _______________________________________________
+5. _______________________________________________
+
+### Inversions
+| # | Inversion | Worth exploring? |
+|---|-----------|-----------------|
+| 1 | What if... | |
+| 2 | What if... | |
+| 3 | What if... | |
+| 4 | What if... | |
+| 5 | What if... | |
+
+### Most Promising
+Pick one and explore deeply:
+> _______________________________________________
+
+---
+
+## Quick Reference
+
+```
+INVERSION IN 30 SECONDS:
+
+1. What do I believe is true?
+   → "${assumption}"
+
+2. What if the opposite is true?
+   → "What if ${NOT assumption}?"
+
+3. What would that change?
+   → "If that's true, then..."
+
+4. Is there evidence for the inversion?
+   → "Let me check..."
+```
+
+---
+
+> **Remember:** Inversion doesn't mean the opposite is true. It means the opposite is worth exploring. Some inversions will be dead ends; that's okay. One breakthrough inversion pays for all the dead ends.