@ngxtm/devkit 3.7.0 → 3.8.0

package/merged-commands/vector-database-engineer.md

@@ -0,0 +1,60 @@
+---
+name: vector-database-engineer
+description: "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar"
+---
+
+# Vector Database Engineer
+
+Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similarity search. Use PROACTIVELY for vector search implementation, embedding optimization, or semantic retrieval systems.
+
+## Do not use this skill when
+
+- The task is unrelated to vector database engineer
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Capabilities
+
+- Vector database selection and architecture
+- Embedding model selection and optimization
+- Index configuration (HNSW, IVF, PQ)
+- Hybrid search (vector + keyword) implementation
+- Chunking strategies for documents
+- Metadata filtering and pre/post-filtering
+- Performance tuning and scaling
+
+## Use this skill when
+
+- Building RAG (Retrieval Augmented Generation) systems
+- Implementing semantic search over documents
+- Creating recommendation engines
+- Building image/audio similarity search
+- Optimizing vector search latency and recall
+- Scaling vector operations to millions of vectors
+
+## Workflow
+
+1. Analyze data characteristics and query patterns
+2. Select appropriate embedding model
+3. Design chunking and preprocessing pipeline
+4. Choose vector database and index type
+5. Configure metadata schema for filtering
+6. Implement hybrid search if needed
+7. Optimize for latency/recall tradeoffs
+8. Set up monitoring and reindexing strategies
+
+## Best Practices
+
+- Choose embedding dimensions based on use case (384-1536)
+- Implement proper chunking with overlap
+- Use metadata filtering to reduce search space
+- Monitor embedding drift over time
+- Plan for index rebuilding
+- Cache frequent queries
+- Test recall vs latency tradeoffs

package/merged-commands/vector-index-tuning.md

@@ -0,0 +1,42 @@
+---
+name: vector-index-tuning
+description: Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.
+---
+
+# Vector Index Tuning
+
+Guide to optimizing vector indexes for production performance.
+
+## Use this skill when
+
+- Tuning HNSW parameters
+- Implementing quantization
+- Optimizing memory usage
+- Reducing search latency
+- Balancing recall vs speed
+- Scaling to billions of vectors
+
+## Do not use this skill when
+
+- You only need exact search on small datasets (use a flat index)
+- You lack workload metrics or ground truth to validate recall
+- You need end-to-end retrieval system design beyond index tuning
+
+## Instructions
+
+1. Gather workload targets (latency, recall, QPS), data size, and memory budget.
+2. Choose an index type and establish a baseline with default parameters.
+3. Benchmark parameter sweeps using real queries and track recall, latency, and memory.
+4. Validate changes on a staging dataset before rolling out to production.
+
+Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.
+
+## Safety
+
+- Avoid reindexing in production without a rollback plan.
+- Validate changes under realistic load before applying globally.
+- Track recall regressions and revert if quality drops.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.

package/merged-commands/vercel-deploy-claimable.md

@@ -0,0 +1,120 @@
+---
+name: vercel-deploy-claimable
+description: Deploy applications and websites to Vercel. Use when user requests deployment actions such as Deploy my app, Deploy this to production, Create a preview deployment. No authentication required - returns preview URL and claimable deployment link.
+source: "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable"
+risk: safe
+---
+
+# Vercel Deploy
+
+Deploy any project to Vercel instantly. No authentication required.
+
+## When to Use This Skill
+
+Use this skill when:
+- User requests deployment actions like "Deploy my app"
+- Deploying to production
+- Creating preview deployments
+- User asks for deployment links
+- Pushing projects live to Vercel
+
+## How It Works
+
+1. Packages your project into a tarball (excludes `node_modules` and `.git`)
+2. Auto-detects framework from `package.json`
+3. Uploads to deployment service
+4. Returns **Preview URL** (live site) and **Claim URL** (transfer to your Vercel account)
+
+## Usage
+
+```bash
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh [path]
+```
+
+**Arguments:**
+- `path` - Directory to deploy, or a `.tgz` file (defaults to current directory)
+
+**Examples:**
+
+```bash
+# Deploy current directory
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh
+
+# Deploy specific project
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project
+
+# Deploy existing tarball
+bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project.tgz
+```
+
+## Output
+
+```
+Preparing deployment...
+Detected framework: nextjs
+Creating deployment package...
+Deploying...
+✓ Deployment successful!
+
+Preview URL: https://skill-deploy-abc123.vercel.app
+Claim URL:   https://vercel.com/claim-deployment?code=...
+```
+
+The script also outputs JSON to stdout for programmatic use:
+
+```json
+{
+  "previewUrl": "https://skill-deploy-abc123.vercel.app",
+  "claimUrl": "https://vercel.com/claim-deployment?code=...",
+  "deploymentId": "dpl_...",
+  "projectId": "prj_..."
+}
+```
+
+## Framework Detection
+
+The script auto-detects frameworks from `package.json`. Supported frameworks include:
+
+- **React**: Next.js, Gatsby, Create React App, Remix, React Router
+- **Vue**: Nuxt, Vitepress, Vuepress, Gridsome
+- **Svelte**: SvelteKit, Svelte, Sapper
+- **Other Frontend**: Astro, Solid Start, Angular, Ember, Preact, Docusaurus
+- **Backend**: Express, Hono, Fastify, NestJS, Elysia, h3, Nitro
+- **Build Tools**: Vite, Parcel
+- **And more**: Blitz, Hydrogen, RedwoodJS, Storybook, Sanity, etc.
+
+For static HTML projects (no `package.json`), framework is set to `null`.
+
+## Static HTML Projects
+
+For projects without a `package.json`:
+- If there's a single `.html` file not named `index.html`, it gets renamed automatically
+- This ensures the page is served at the root URL (`/`)
+
+## Present Results to User
+
+Always show both URLs:
+
+```
+✓ Deployment successful!
+
+Preview URL: https://skill-deploy-abc123.vercel.app
+Claim URL:   https://vercel.com/claim-deployment?code=...
+
+View your site at the Preview URL.
+To transfer this deployment to your Vercel account, visit the Claim URL.
+```
+
+## Troubleshooting
+
+### Network Egress Error
+
+If deployment fails due to network restrictions (common on claude.ai), tell the user:
+
+```
+Deployment failed due to network restrictions. To fix this:
+
+1. Go to https://claude.ai/settings/capabilities
+2. Add *.vercel.com to the allowed domains
+3. Try deploying again
+```

package/merged-commands/vercel-deploy.md

@@ -0,0 +1,22 @@
+---
+name: vercel-deploy
+description: Deploy applications to Vercel with edge functions, serverless, and ISR.
+author: vercel
+category: development
+tags: [nextjs, node, typescript]
+---
+
+# Vercel Deploy
+
+Deploy applications to Vercel with edge functions, serverless, and ISR.
+
+## When to Use
+
+- Deploying Next.js applications
+- Setting up edge functions
+- Configuring ISR (Incremental Static Regeneration)
+- Serverless deployments
+
+## Source
+
+This skill references patterns from [Vercel's agent-skills](https://github.com/vercel-labs/agent-skills).

package/merged-commands/vercel-deployment.md

@@ -0,0 +1,79 @@
+---
+name: vercel-deployment
+description: "Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production."
+source: vibeship-spawner-skills (Apache 2.0)
+risk: safe
+---
+
+# Vercel Deployment
+
+You are a Vercel deployment expert. You understand the platform's
+capabilities, limitations, and best practices for deploying Next.js
+applications at scale.
+
+## When to Use This Skill
+
+Use this skill when:
+- Deploying to Vercel
+- Working with Vercel deployment
+- Hosting applications on Vercel
+- Deploying to production on Vercel
+- Configuring Vercel for Next.js applications
+
+Your core principles:
+1. Environment variables - different for dev/preview/production
+2. Edge vs Serverless - choose the right runtime
+3. Build optimization - minimize cold starts and bundle size
+4. Preview deployments - use for testing before production
+5. Monitoring - set up analytics and error tracking
+
+## Capabilities
+
+- vercel
+- deployment
+- edge-functions
+- serverless
+- environment-variables
+
+## Requirements
+
+- nextjs-app-router
+
+## Patterns
+
+### Environment Variables Setup
+
+Properly configure environment variables for all environments
+
+### Edge vs Serverless Functions
+
+Choose the right runtime for your API routes
+
+### Build Optimization
+
+Optimize build for faster deployments and smaller bundles
+
+## Anti-Patterns
+
+### ❌ Secrets in NEXT_PUBLIC_
+
+### ❌ Same Database for Preview
+
+### ❌ No Build Cache
+
+## ⚠️ Sharp Edges
+
+| Issue | Severity | Solution |
+|-------|----------|----------|
+| NEXT_PUBLIC_ exposes secrets to the browser | critical | Only use NEXT_PUBLIC_ for truly public values: |
+| Preview deployments using production database | high | Set up separate databases for each environment: |
+| Serverless function too large, slow cold starts | high | Reduce function size: |
+| Edge runtime missing Node.js APIs | high | Check API compatibility before using edge: |
+| Function timeout causes incomplete operations | medium | Handle long operations properly: |
+| Environment variable missing at runtime but present at build | medium | Understand when env vars are read: |
+| CORS errors calling API routes from different domain | medium | Add CORS headers to API routes: |
+| Page shows stale data after deployment | medium | Control caching behavior: |
+
+## Related Skills
+
+Works well with: `nextjs-app-router`, `supabase-backend`

package/merged-commands/verification-before-completion.md

@@ -0,0 +1,139 @@
+---
+name: verification-before-completion
+description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
+---
+
+# Verification Before Completion
+
+## Overview
+
+Claiming work is complete without verification is dishonesty, not efficiency.
+
+**Core principle:** Evidence before claims, always.
+
+**Violating the letter of this rule is violating the spirit of this rule.**
+
+## The Iron Law
+
+```
+NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
+```
+
+If you haven't run the verification command in this message, you cannot claim it passes.
+
+## The Gate Function
+
+```
+BEFORE claiming any status or expressing satisfaction:
+
+1. IDENTIFY: What command proves this claim?
+2. RUN: Execute the FULL command (fresh, complete)
+3. READ: Full output, check exit code, count failures
+4. VERIFY: Does output confirm the claim?
+   - If NO: State actual status with evidence
+   - If YES: State claim WITH evidence
+5. ONLY THEN: Make the claim
+
+Skip any step = lying, not verifying
+```
+
+## Common Failures
+
+| Claim | Requires | Not Sufficient |
+|-------|----------|----------------|
+| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
+| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
+| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
+| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
+| Regression test works | Red-green cycle verified | Test passes once |
+| Agent completed | VCS diff shows changes | Agent reports "success" |
+| Requirements met | Line-by-line checklist | Tests passing |
+
+## Red Flags - STOP
+
+- Using "should", "probably", "seems to"
+- Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.)
+- About to commit/push/PR without verification
+- Trusting agent success reports
+- Relying on partial verification
+- Thinking "just this once"
+- Tired and wanting work over
+- **ANY wording implying success without having run verification**
+
+## Rationalization Prevention
+
+| Excuse | Reality |
+|--------|---------|
+| "Should work now" | RUN the verification |
+| "I'm confident" | Confidence ≠ evidence |
+| "Just this once" | No exceptions |
+| "Linter passed" | Linter ≠ compiler |
+| "Agent said success" | Verify independently |
+| "I'm tired" | Exhaustion ≠ excuse |
+| "Partial check is enough" | Partial proves nothing |
+| "Different words so rule doesn't apply" | Spirit over letter |
+
+## Key Patterns
+
+**Tests:**
+```
+✅ [Run test command] [See: 34/34 pass] "All tests pass"
+❌ "Should pass now" / "Looks correct"
+```
+
+**Regression tests (TDD Red-Green):**
+```
+✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
+❌ "I've written a regression test" (without red-green verification)
+```
+
+**Build:**
+```
+✅ [Run build] [See: exit 0] "Build passes"
+❌ "Linter passed" (linter doesn't check compilation)
+```
+
+**Requirements:**
+```
+✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
+❌ "Tests pass, phase complete"
+```
+
+**Agent delegation:**
+```
+✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
+❌ Trust agent report
+```
+
+## Why This Matters
+
+From 24 failure memories:
+- your human partner said "I don't believe you" - trust broken
+- Undefined functions shipped - would crash
+- Missing requirements shipped - incomplete features
+- Time wasted on false completion → redirect → rework
+- Violates: "Honesty is a core value. If you lie, you'll be replaced."
+
+## When To Apply
+
+**ALWAYS before:**
+- ANY variation of success/completion claims
+- ANY expression of satisfaction
+- ANY positive statement about work state
+- Committing, PR creation, task completion
+- Moving to next task
+- Delegating to agents
+
+**Rule applies to:**
+- Exact phrases
+- Paraphrases and synonyms
+- Implications of success
+- ANY communication suggesting completion/correctness
+
+## The Bottom Line
+
+**No shortcuts for verification.**
+
+Run the command. Read the output. THEN claim the result.
+
+This is non-negotiable.

package/merged-commands/vexor.md

@@ -0,0 +1,22 @@
+---
+name: vexor
+description: "Vector-powered CLI for semantic file search with a Claude/Codex skill"
+source: "https://github.com/scarletkc/vexor"
+risk: safe
+---
+
+# Vexor
+
+## Overview
+
+Vector-powered CLI for semantic file search with a Claude/Codex skill
+
+## When to Use This Skill
+
+Use this skill when you need to work with vector-powered cli for semantic file search with a claude/codex skill.
+
+## Instructions
+
+This skill provides guidance and patterns for vector-powered cli for semantic file search with a claude/codex skill.
+
+For more information, see the [source repository](https://github.com/scarletkc/vexor).

package/merged-commands/video-downloader.md

@@ -0,0 +1,106 @@
+---
+name: video-downloader
+description: Downloads videos from YouTube and other platforms for offline viewing, editing, or archival. Handles various formats and quality options.
+---
+
+# Video Downloader
+
+This skill downloads videos from YouTube and other platforms directly to your computer.
+
+## When to Use This Skill
+
+- Downloading YouTube videos for offline viewing
+- Saving educational content for reference
+- Archiving important videos
+- Getting video files for editing or repurposing
+- Downloading your own content from platforms
+- Saving conference talks or webinars
+
+## What This Skill Does
+
+1. **Downloads Videos**: Fetches videos from YouTube and other platforms
+2. **Quality Selection**: Lets you choose resolution (480p, 720p, 1080p, 4K)
+3. **Format Options**: Downloads in various formats (MP4, WebM, audio-only)
+4. **Batch Downloads**: Can download multiple videos or playlists
+5. **Metadata Preservation**: Saves title, description, and thumbnail
+
+## How to Use
+
+### Basic Download
+
+```
+Download this YouTube video: https://youtube.com/watch?v=...
+```
+
+```
+Download this video in 1080p quality
+```
+
+### Audio Only
+
+```
+Download the audio from this YouTube video as MP3
+```
+
+### Playlist Download
+
+```
+Download all videos from this YouTube playlist: [URL]
+```
+
+### Batch Download
+
+```
+Download these 5 YouTube videos:
+1. [URL]
+2. [URL]
+...
+```
+
+## Example
+
+**User**: "Download this YouTube video: https://youtube.com/watch?v=abc123"
+
+**Output**:
+```
+Downloading from YouTube...
+
+Video: "How to Build Products Users Love"
+Channel: Lenny's Podcast
+Duration: 45:32
+Quality: 1080p
+
+Progress: ████████████████████ 100%
+
+✓ Downloaded: how-to-build-products-users-love.mp4
+✓ Saved thumbnail: how-to-build-products-users-love.jpg
+✓ Size: 342 MB
+
+Saved to: ~/Downloads/
+```
+
+**Inspired by:** Lenny's workflow from his newsletter
+
+## Important Notes
+
+⚠️ **Copyright & Fair Use**
+- Only download videos you have permission to download
+- Respect copyright laws and platform terms of service
+- Use for personal, educational, or fair use purposes
+- Don't redistribute copyrighted content
+
+## Tips
+
+- Specify quality if you need lower file size (720p vs 1080p)
+- Use audio-only for podcasts or music to save space
+- Download to a dedicated folder to stay organized
+- Check file size before downloading on slow connections
+
+## Common Use Cases
+
+- **Education**: Save tutorials and courses for offline learning
+- **Research**: Archive videos for reference
+- **Content Creation**: Download your own content from platforms
+- **Backup**: Save important videos before they're removed
+- **Offline Viewing**: Watch videos without internet access
+