feat: Complete fleet — 94 skills across 10+ domains

Pulled ALL skills from 15 source repositories:
- anthropics/skills: 16 (docs, design, MCP, testing)
- obra/superpowers: 14 (TDD, debugging, agents, planning)
- coreyhaines31/marketingskills: 25 (marketing, CRO, SEO, growth)
- better-auth/skills: 5 (auth patterns)
- vercel-labs/agent-skills: 5 (React, design, Vercel)
- antfu/skills: 16 (Vue, Vite, Vitest, pnpm, Turborepo)
- Plus 13 individual skills from various repos

Mosaic Stack is not limited to coding — the Orchestrator and
subagents serve coding, business, design, marketing, writing,
logistics, analysis, and more.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

skills/pnpm/references/features-catalogs.md

@@ -0,0 +1,159 @@
+---
+name: pnpm-catalogs
+description: Centralized dependency version management for workspaces
+---
+
+# pnpm Catalogs
+
+Catalogs provide a centralized way to manage dependency versions across a workspace. Define versions once, use everywhere.
+
+## Basic Usage
+
+Define a catalog in `pnpm-workspace.yaml`:
+
+```yaml
+packages:
+  - 'packages/*'
+
+catalog:
+  react: ^18.2.0
+  react-dom: ^18.2.0
+  typescript: ~5.3.0
+  vite: ^5.0.0
+```
+
+Reference in `package.json` with `catalog:`:
+
+```json
+{
+  "dependencies": {
+    "react": "catalog:",
+    "react-dom": "catalog:"
+  },
+  "devDependencies": {
+    "typescript": "catalog:",
+    "vite": "catalog:"
+  }
+}
+```
+
+## Named Catalogs
+
+Create multiple catalogs for different scenarios:
+
+```yaml
+packages:
+  - 'packages/*'
+
+# Default catalog
+catalog:
+  lodash: ^4.17.21
+
+# Named catalogs
+catalogs:
+  react17:
+    react: ^17.0.2
+    react-dom: ^17.0.2
+  
+  react18:
+    react: ^18.2.0
+    react-dom: ^18.2.0
+  
+  testing:
+    vitest: ^1.0.0
+    "@testing-library/react": ^14.0.0
+```
+
+Reference named catalogs:
+
+```json
+{
+  "dependencies": {
+    "react": "catalog:react18",
+    "react-dom": "catalog:react18"
+  },
+  "devDependencies": {
+    "vitest": "catalog:testing"
+  }
+}
+```
+
+## Benefits
+
+1. **Single source of truth**: Update version in one place
+2. **Consistency**: All packages use the same version
+3. **Easy upgrades**: Change version once, affects entire workspace
+4. **Type-safe**: TypeScript support in pnpm-workspace.yaml
+
+## Catalog vs Overrides
+
+| Feature | Catalogs | Overrides |
+|---------|----------|-----------|
+| Purpose | Define versions for direct dependencies | Force versions for any dependency |
+| Scope | Direct dependencies only | All dependencies (including transitive) |
+| Usage | `"pkg": "catalog:"` | Applied automatically |
+| Opt-in | Explicit per package.json | Global to workspace |
+
+## Publishing with Catalogs
+
+When publishing, `catalog:` references are replaced with actual versions:
+
+```json
+// Before publish (source)
+{
+  "dependencies": {
+    "react": "catalog:"
+  }
+}
+
+// After publish (published package)
+{
+  "dependencies": {
+    "react": "^18.2.0"
+  }
+}
+```
+
+## Migration from Overrides
+
+If you're using overrides for version consistency:
+
+```yaml
+# Before (using overrides)
+overrides:
+  react: ^18.2.0
+  react-dom: ^18.2.0
+```
+
+Migrate to catalogs for cleaner dependency management:
+
+```yaml
+# After (using catalogs)
+catalog:
+  react: ^18.2.0
+  react-dom: ^18.2.0
+```
+
+Then update package.json files to use `catalog:`.
+
+## Best Practices
+
+1. **Use default catalog** for commonly shared dependencies
+2. **Use named catalogs** for version variants (e.g., different React versions)
+3. **Keep catalog minimal** - only include shared dependencies
+4. **Combine with workspace protocol** for internal packages
+
+```yaml
+catalog:
+  # External shared dependencies
+  lodash: ^4.17.21
+  zod: ^3.22.0
+
+# Internal packages use workspace: protocol instead
+# "dependencies": { "@myorg/utils": "workspace:^" }
+```
+
+<!-- 
+Source references:
+- https://pnpm.io/catalogs
+-->