Updates plugin location for proper installation

.claude-plugin/marketplace.json

@@ -6,15 +6,60 @@
   },
   "metadata": {
     "description": "Comprehensive Claude Code skills marketplace: collaboration, testing, debugging, and more",
-    "version": "2.0.0"
+    "version": "2.1.0"
+  },
+  "packs": {
+    "universal": {
+      "name": "Universal Skills Pack",
+      "description": "Essential skills for all Claude Code users: collaboration, problem-solving, and research",
+      "roles": ["all", "non-technical", "manager", "researcher"],
+      "plugins": [
+        "collaboration-skills",
+        "problem-solving-skills",
+        "research-skills"
+      ],
+      "install_command": "/plugin install collaboration-skills@claude-power-user && /plugin install problem-solving-skills@claude-power-user && /plugin install research-skills@claude-power-user"
+    },
+    "developer": {
+      "name": "Developer Skills Pack",
+      "description": "Developer-focused skills: testing, debugging, and architecture patterns",
+      "roles": ["developer", "engineer", "tech-lead"],
+      "plugins": [
+        "testing-skills",
+        "debugging-skills",
+        "architecture-skills"
+      ],
+      "install_command": "/plugin install testing-skills@claude-power-user && /plugin install debugging-skills@claude-power-user && /plugin install architecture-skills@claude-power-user"
+    },
+    "power-user": {
+      "name": "Power User Pack",
+      "description": "Meta skills for customizing and extending Claude Code capabilities",
+      "roles": ["power-user", "admin", "customizer"],
+      "plugins": [
+        "meta-skills"
+      ],
+      "install_command": "/plugin install meta-skills@claude-power-user"
+    },
+    "complete": {
+      "name": "Complete Skills Pack",
+      "description": "All available skills - the complete claude-power-user experience",
+      "roles": ["all"],
+      "plugins": [
+        "collaboration-skills",
+        "testing-skills",
+        "debugging-skills",
+        "meta-skills",
+        "problem-solving-skills",
+        "research-skills",
+        "architecture-skills"
+      ],
+      "install_command": "/plugin install collaboration-skills@claude-power-user && /plugin install testing-skills@claude-power-user && /plugin install debugging-skills@claude-power-user && /plugin install meta-skills@claude-power-user && /plugin install problem-solving-skills@claude-power-user && /plugin install research-skills@claude-power-user && /plugin install architecture-skills@claude-power-user"
+    }
   },
   "plugins": [
     {
       "name": "collaboration-skills",
-      "source": {
-        "source": "local",
-        "path": "plugins/collaboration"
-      },
+      "source": "./plugins/collaboration",
       "description": "Collaboration skills: brainstorming, planning, code review, parallel agents, git workflows",
       "version": "1.0.0",
       "category": "productivity",
@@ -23,10 +68,7 @@
     },
     {
       "name": "testing-skills",
-      "source": {
-        "source": "local",
-        "path": "plugins/testing"
-      },
+      "source": "./plugins/testing",
       "description": "Testing skills: TDD, async patterns, testing anti-patterns",
       "version": "1.0.0",
       "category": "development",
@@ -35,10 +77,7 @@
     },
     {
       "name": "debugging-skills",
-      "source": {
-        "source": "local",
-        "path": "plugins/debugging"
-      },
+      "source": "./plugins/debugging",
       "description": "Debugging skills: systematic debugging, root cause tracing, verification, defense-in-depth",
       "version": "1.0.0",
       "category": "development",
@@ -47,10 +86,7 @@
     },
     {
       "name": "meta-skills",
-      "source": {
-        "source": "local",
-        "path": "plugins/meta"
-      },
+      "source": "./plugins/meta",
       "description": "Meta skills: writing skills, testing skills, sharing contributions, maintaining skill repositories",
       "version": "1.0.0",
       "category": "meta",
@@ -59,10 +95,7 @@
     },
     {
       "name": "problem-solving-skills",
-      "source": {
-        "source": "local",
-        "path": "plugins/problem-solving"
-      },
+      "source": "./plugins/problem-solving",
       "description": "Problem-solving skills: thinking techniques, simplification, pattern recognition, inversion exercises",
       "version": "1.0.0",
       "category": "productivity",
@@ -71,10 +104,7 @@
     },
     {
       "name": "research-skills",
-      "source": {
-        "source": "local",
-        "path": "plugins/research"
-      },
+      "source": "./plugins/research",
       "description": "Research skills: knowledge investigation, tracing lineages, information gathering",
       "version": "1.0.0",
       "category": "research",
@@ -83,10 +113,7 @@
     },
     {
       "name": "architecture-skills",
-      "source": {
-        "source": "local",
-        "path": "plugins/architecture"
-      },
+      "source": "./plugins/architecture",
       "description": "Architecture skills: design patterns, productive tensions, system thinking",
       "version": "1.0.0",
       "category": "architecture",

.claude-plugin/plugins/architecture/.claude-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "architecture-skills",
+  "description": "Architecture skills: design patterns, productive tensions, system thinking",
+  "version": "1.0.0",
+  "author": {
+    "name": "Matthew Caughman",
+    "email": "mcaughman@hackerone.com"
+  },
+  "license": "MIT",
+  "keywords": ["architecture", "design", "patterns", "system-design"]
+}

.claude-plugin/plugins/architecture/skills/ABOUT.md

@@ -0,0 +1,20 @@
+# Architecture Skills - Attribution
+
+This skill was derived from agent patterns in the [Amplifier](https://github.com/microsoft/amplifier) project.
+
+**Source Repository:**
+- Name: Amplifier
+- URL: https://github.com/microsoft/amplifier
+- Commit: 2adb63f858e7d760e188197c8e8d4c1ef721e2a6
+- Date: 2025-10-10
+
+## Skills Derived from Amplifier Agents
+
+**From ambiguity-guardian agent:**
+- preserving-productive-tensions - Recognizing when disagreements reveal valuable context, preserving multiple valid approaches instead of forcing premature resolution
+
+## What Was Adapted
+
+The ambiguity-guardian agent preserves productive contradictions and navigates uncertainty as valuable features of knowledge. This skill extracts the core pattern-recognition capability: distinguishing when tensions should be preserved (context-dependent trade-offs) vs resolved (clear technical superiority).
+
+Adapted as scannable guide with symptom-based triggers ("going back and forth", "keep changing mind") and practical preservation patterns (configuration, parallel implementations, documented trade-offs).

.claude-plugin/plugins/architecture/skills/preserving-productive-tensions/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: Preserving Productive Tensions
+description: Recognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution
+when_to_use: when oscillating between equally valid approaches that optimize for different legitimate priorities
+version: 1.1.0
+---
+
+# Preserving Productive Tensions
+
+## Overview
+
+Some tensions aren't problems to solve - they're valuable information to preserve. When multiple approaches are genuinely valid in different contexts, forcing a choice destroys flexibility.
+
+**Core principle:** Preserve tensions that reveal context-dependence. Force resolution only when necessary.
+
+## Recognizing Productive Tensions
+
+**A tension is productive when:**
+- Both approaches optimize for different valid priorities (cost vs latency, simplicity vs features)
+- The "better" choice depends on deployment context, not technical superiority
+- Different users/deployments would choose differently
+- The trade-off is real and won't disappear with clever engineering
+- Stakeholders have conflicting valid concerns
+
+**A tension needs resolution when:**
+- Implementation cost of preserving both is prohibitive
+- The approaches fundamentally conflict (can't coexist)
+- There's clear technical superiority for this specific use case
+- It's a one-way door (choice locks architecture)
+- Preserving both adds complexity without value
+
+## Preservation Patterns
+
+### Pattern 1: Configuration
+Make the choice configurable rather than baked into architecture:
+
+```python
+class Config:
+    mode: Literal["optimize_cost", "optimize_latency"]
+    # Each mode gets clean, simple implementation
+```
+
+**When to use:** Both approaches are architecturally compatible, switching is runtime decision
+
+### Pattern 2: Parallel Implementations
+Maintain both as separate clean modules with shared contract:
+
+```python
+# processor/batch.py - optimizes for cost
+# processor/stream.py - optimizes for latency
+# Both implement: def process(data) -> Result
+```
+
+**When to use:** Approaches diverge significantly, but share same interface
+
+### Pattern 3: Documented Trade-off
+Capture the tension explicitly in documentation/decision records:
+
+```markdown
+## Unresolved Tension: Authentication Strategy
+
+**Option A: JWT** - Stateless, scales easily, but token revocation is hard
+**Option B: Sessions** - Easy revocation, but requires shared state
+
+**Why unresolved:** Different deployments need different trade-offs
+**Decision deferred to:** Deployment configuration
+**Review trigger:** If 80% of deployments choose one option
+```
+
+**When to use:** Can't preserve both in code, but need to document the choice was deliberate
+
+## Red Flags - You're Forcing Resolution
+
+- Asking "which is best?" when both are valid
+- "We need to pick one" without explaining why
+- Choosing based on your preference vs user context
+- Resolving tensions to "make progress" when preserving them IS progress
+- Forcing consensus when diversity is valuable
+
+**All of these mean: STOP. Consider preserving the tension.**
+
+## When to Force Resolution
+
+**You SHOULD force resolution when:**
+
+1. **Implementation cost is prohibitive**
+   - Building/maintaining both would slow development significantly
+   - Team doesn't have bandwidth for parallel approaches
+
+2. **Fundamental conflict**
+   - Approaches make contradictory architectural assumptions
+   - Can't cleanly separate concerns
+
+3. **Clear technical superiority**
+   - One approach is objectively better for this specific context
+   - Not "I prefer X" but "X solves our constraints, Y doesn't"
+
+4. **One-way door**
+   - Choice locks us into an architecture
+   - Migration between options would be expensive
+
+5. **Simplicity requires choice**
+   - Preserving both genuinely adds complexity
+   - YAGNI: Don't build both if we only need one
+
+**Ask explicitly:** "Should I pick one, or preserve both as options?"
+
+## Documentation Format
+
+When preserving tensions, document clearly:
+
+```markdown
+## Tension: [Name]
+
+**Context:** [Why this tension exists]
+
+**Option A:** [Approach]
+- Optimizes for: [Priority]
+- Trade-off: [Cost]
+- Best when: [Context]
+
+**Option B:** [Approach]
+- Optimizes for: [Different priority]
+- Trade-off: [Different cost]
+- Best when: [Different context]
+
+**Preservation strategy:** [Configuration/Parallel/Documented]
+
+**Resolution trigger:** [Conditions that would force choosing one]
+```
+
+## Examples
+
+### Productive Tension (Preserve)
+"Should we optimize for cost or latency?"
+- **Answer:** Make it configurable - different deployments need different trade-offs
+
+### Technical Decision (Resolve)
+"Should we use SSE or WebSockets?"
+- **Answer:** SSE - we only need one-way communication, simpler implementation
+
+### Business Decision (Defer)
+"Should we support offline mode?"
+- **Answer:** Don't preserve both - ask stakeholder to decide based on user needs
+
+## Remember
+
+- Tensions between valid priorities are features, not bugs
+- Premature consensus destroys valuable flexibility
+- Configuration > forced choice (when reasonable)
+- Document trade-offs explicitly
+- Resolution is okay when justified

.claude-plugin/plugins/collaboration/.claude-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "collaboration-skills",
+  "description": "Collaboration skills: brainstorming, planning, code review, parallel agents, git workflows",
+  "version": "1.0.0",
+  "author": {
+    "name": "Matthew Caughman",
+    "email": "mcaughman@hackerone.com"
+  },
+  "license": "MIT",
+  "keywords": ["collaboration", "brainstorming", "planning", "code-review", "workflows"]
+}