@tech-leads-club/skills-catalog 0.1.0

package/package.json

@@ -0,0 +1,15 @@
+{
+  "name": "@tech-leads-club/skills-catalog",
+  "version": "0.1.0",
+  "description": "Skills catalog registry for agent-skills CLI (CDN distribution)",
+  "author": "Tech Leads Club",
+  "license": "MIT",
+  "type": "module",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/tech-leads-club/agent-skills.git",
+    "directory": "packages/skills-catalog"
+  },
+  "publishConfig": { "access": "public" },
+  "files": ["skills-registry.json", "skills/"]
+}

package/skills/(architecture)/component-common-domain-detection/QUICK-REFERENCE.md

@@ -0,0 +1,169 @@
+# Common Domain Component Detection - Quick Reference
+
+## Domain vs Infrastructure
+
+| Type               | Description                              | Examples                        | Consolidate?               |
+| ------------------ | ---------------------------------------- | ------------------------------- | -------------------------- |
+| **Domain**         | Business logic, common to some processes | Notification, audit, validation | ✅ Yes                     |
+| **Infrastructure** | Technical concerns, common to all        | Logging, metrics, security      | ❌ No (handled separately) |
+
+## Detection Strategies
+
+### 1. Namespace Pattern Detection
+
+Find components with common leaf node names:
+
+```
+services/customer/notification  ← Common pattern
+services/ticket/notification     ← Common pattern
+services/survey/notification     ← Common pattern
+```
+
+**Common Patterns**:
+
+- `*.notification`, `*.notify`, `*.email`
+- `*.audit`, `*.auditing`, `*.log`
+- `*.validation`, `*.validate`, `*.validator`
+- `*.format`, `*.formatter`, `*.formatting`
+
+### 2. Shared Class Detection
+
+Find classes used across multiple components:
+
+```
+SMTPConnection → Used by 5 components
+AuditLogger → Used by 8 components
+DataFormatter → Used by 3 components
+```
+
+### 3. Functionality Analysis
+
+Examine code to verify similarity:
+
+- Read source code of each component
+- Identify similarities and differences
+- Assess if differences can be abstracted
+
+## Coupling Analysis
+
+### Before Consolidation
+
+```
+Component A: CA = 2 (used by 2 components)
+Component B: CA = 2 (used by 2 components)
+Component C: CA = 1 (used by 1 component)
+Total CA: 5
+```
+
+### After Consolidation
+
+```
+Consolidated Component: CA = 5 (used by 5 components)
+Total CA: 5 (same!)
+```
+
+**Verdict**: ✅ Safe to consolidate (no coupling increase)
+
+### Warning Signs
+
+```
+After Consolidation: CA = 15 (was 5)
+Verdict: ⚠️ High coupling increase - reconsider
+```
+
+## Consolidation Approaches
+
+### Shared Service
+
+**Use when**:
+
+- Functionality changes frequently
+- Complex operations
+- Needs independent scaling
+
+**Example**: Notification service called by multiple components
+
+### Shared Library
+
+**Use when**:
+
+- Stable functionality
+- Simple utilities
+- Compile-time dependency acceptable
+
+**Example**: Validation utilities packaged as npm package
+
+### Component Merge
+
+**Use when**:
+
+- Highly related functionality
+- Low coupling impact
+- Same deployment unit acceptable
+
+**Example**: Merge 3 notification components into 1
+
+## Quick Analysis Steps
+
+1. **Scan** → Find common namespace patterns
+2. **Detect** → Identify shared classes
+3. **Analyze** → Verify functionality similarity
+4. **Assess** → Calculate coupling impact
+5. **Recommend** → Suggest consolidation approach
+
+## Output Template
+
+```markdown
+## Common Domain Components Found
+
+### [Functionality Name]
+
+**Components**:
+
+- component1 (X% - Y statements)
+- component2 (X% - Y statements)
+
+**Functionality Analysis**:
+
+- Similarities: [what's the same]
+- Differences: [what's different]
+- Consolidation Feasibility: ✅ High / ⚠️ Medium / ❌ Low
+
+**Coupling Analysis**:
+
+- Before: CA = X
+- After: CA = Y
+- Verdict: ✅ Safe / ⚠️ Monitor / ❌ Too risky
+
+**Recommendation**: [consolidation approach]
+```
+
+## Decision Tree
+
+```
+Found common pattern?
+├─ YES → Analyze functionality
+│   ├─ Similar enough?
+│   │   ├─ YES → Assess coupling
+│   │   │   ├─ CA increase acceptable?
+│   │   │   │   ├─ YES → ✅ Consolidate
+│   │   │   │   └─ NO → ⚠️ Reconsider or use shared library
+│   │   └─ NO → ❌ Don't consolidate
+│   └─ NO → ❌ Don't consolidate
+└─ NO → No consolidation needed
+```
+
+## Common Patterns
+
+### High Consolidation Candidates ✅
+
+- Notification components
+- Audit components
+- Validation components
+- Formatting components
+
+### Low Consolidation Candidates ❌
+
+- Infrastructure utilities
+- Different business contexts
+- High coupling risk scenarios