vitest-feature-protector
Generate Vitest unit tests for new features/components to prevent regressions
Discover Business skills, compare source repositories and read the instructions for each workflow.
Generate Vitest unit tests for new features/components to prevent regressions
Systematic debugging of code to find root causes, fix bugs, and prevent regressions. Use whenever an error, bug, or unexpected behavior appears.
Critical guardrail for Supabase database operations ensuring multi-tenant isolation with publication_id filtering, proper use of supabaseAdmin, avoiding SELECT *, error handling patterns, and secure server-side...
Next.js 15 API route patterns, NextRequest, NextResponse, error handling, maxDuration configuration, authentication, request validation, server-side operations, route handlers, and API endpoint best practices....
AI content generation with OpenAI and Claude, callAIWithPrompt usage, prompt storage in app_settings, structured outputs, response format validation, multi-criteria scoring, rate limiting, JSON schema, and AI A...
Guide for working with newsletter campaigns, RSS processing workflows, article generation, MailerLite integration, multi-tenant isolation, campaign status management, Vercel workflows, advertorial rotation, and...
File AnyPod GitHub issues (bug or feature) with the official templates and publish them through the gh CLI.
Generates comprehensive pre-PR test checklist for dotfiles TUI. Use before merging feature branches to main, when running tests, creating test plans, or doing QA. Includes manual tests, automatic tests, securit...
RemoteViewer.Client design system with spacing, colors, typography, and components. Use when building UI, styling components, or working with Avalonia XAML.
Guide for using MVVM Community Toolkit with Avalonia in RemoteViewer.Client. Use when working with ViewModels, data binding, commands, or Avalonia UI patterns.
Neon PostgreSQL patterns for Pitchey. Raw SQL only, no ORM. Uses Hyperdrive for connection pooling. Activates for database queries, migrations, or schema work.
Edge function development patterns for Cloudflare Workers. Use when creating API endpoints, handling requests, or working with bindings.
Debugging patterns for Cloudflare Workers. Activates when troubleshooting errors, checking logs, or investigating production issues.
Cloudflare Wrangler deployment patterns for Pitchey. Activates when deploying, publishing, or releasing to Cloudflare Pages or Workers.
Tools for searching, reading, and adding to the user's personal notes (Obsidian vault).
Sub skill for pbt-workflow-guide. Apply Aletheia to generate and sync PBT templates/tests for any non-aletheia MoonBit repo.
Sub skill for pbt-workflow-guide. Self-dogfooding workflow for the f4ah6o/aletheia.mbt repo, covering PBT generation, template updates, and validation.
Create a new version tag with release message and push to trigger GoReleaser. Use when user wants to release, tag, bump version, or publish a new version.
Implements a proactive confirmation and continuous loop mechanism for all agent interactions. Use this skill when engaging in any task (consultation, development, debugging) to ensure step-by-step user approval...
Annotation and documentation protocol for rapid-iteration projects (“vibe coding”). Enforces Google Docstring Style plus comment-as-contract: consistency with signatures/types, explicit pre/post-conditions, uni...
External (non-workspace) research protocol. Use network search only to locate canonical repos/docs, then verify by reading source (github_repo) or official docs (Context7/DeepWiki). Enforce fact-driven answers...
Fact-driven retrieval for local codebases. Use codebase-wide search first, English long-form queries, then read complete files (optionally in parallel) and use CLI grep/ripgrep for keyword pinpointing when help...
Isaac Lab project-specific conventions. Environment activation, standalone AppLauncher pattern.
Planning workflow for breaking down tasks into actionable steps. Defines the standard plan structure (milestones/tasks/dependencies/risks) and execution tracking via manage_todo_list.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.