Loading...
Loading...
Found 865 Skills
Skills for Upstash Vector features, TypeScript/JavaScript SDK usage, and integrations. Use when users ask how to work with Vector, its TS SDK, features, or supported frameworks.
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
Create custom Code Analyzer rules for Regex (pattern matching), PMD (XPath/AST for Apex and metadata XML), and ESLint (LWC/JavaScript/TypeScript). Use when users want to enforce coding standards, ban patterns, detect hardcoded values, govern metadata, or add rules not in the built-in set. TRIGGER when: user says 'create a rule', 'ban System.debug', 'enforce naming convention', 'detect hardcoded IDs', 'custom rule', 'xpath rule', 'regex rule', 'add a PMD rule', 'enforce a policy', 'create a check for', 'flag this pattern', 'make a rule that catches', 'metadata rule', 'check permissions', 'enforce API version', 'eslint rule', 'lwc rule', 'override rule threshold', 'customize complexity', or describes a pattern to enforce. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), configure engines (use dx-code-analyzer-configure), or explain existing rules (use dx-code-analyzer-run).
Workspace locales and translations for Factorial Code — i18n/<locale>.yaml locale files, the fcode.i18n(key, args) runtime helper in JavaScript and Python, fcode.i18n("key") tokens in form schemas, execution-locale selection (Fcode-Locale header, ?locale=, schedules), inheritance and primary-locale fallback, locale versioning, and the fcode i18n:* CLI commands. Use when adding a locale, translating or internationalizing existing process code or form text, calling fcode.i18n, testing with fcode run --locale, or syncing translations with i18n:push.
Add Polar billing to a TypeScript/JavaScript app using the @polar-sh/sdk package. Use this skill whenever the user wants to add a Checkout endpoint, a Customer Portal endpoint, or a Webhooks endpoint for Polar to any framework — Next.js, Express, Hono, Astro, SvelteKit, Remix, TanStack Start, Nuxt, Fastify, Elysia, Deno, Supabase Edge Functions, Cloudflare Workers, Bun, etc.
Use when turning a song into a kinetic-typography or motion-design music video, lyric video, visualizer or K-pop style MV with Scenario, landscape or vertical 9:16 for TikTok, Reels and Shorts: a generated subject sheet, style frames and footage, plus a deterministic JavaScript/three.js engine for lyric type, mattes and tracked graphics timed to sung onsets. Also for revising, recutting or cutting teasers from such a video.
Livewire 3 reactive components - wire:model, actions, events, Volt, Folio. Use when building reactive UI without JavaScript.
Shipwright build system for The Boring JavaScript Stack — Rsbuild-based asset pipeline replacing Grunt, with framework plugins for React/Vue/Svelte, Tailwind CSS, SSR support, and dev server with HMR. Use this skill when configuring builds, managing assets, or debugging the development server.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Generate Shopify Liquid theme code (sections, blocks, snippets) with correct schema JSON, LiquidDoc headers, translation keys, and CSS/JS patterns. Use when creating or editing .liquid files for Shopify themes, working with schema, doc, stylesheet, javascript tags, or Shopify Liquid objects/filters/tags.
Run Vitest tests and parse results into actionable output. Use WHEN user needs to run JavaScript/TypeScript tests in a Vitest-configured project, verify test suites pass, or get structured failure reports. Use for "run tests", "vitest", "check if tests pass", or "test results". Do NOT use for Jest/Mocha projects, installing dependencies, writing new tests, or auto-fixing failing assertions.
SafetyMails platform help — bulk email verification (up to 2M emails, 19-step algorithm), real-time API validation (JavaScript embed for forms), Email Finder (B2B corporate lookup), list cleaning, spamtrap/disposable/catch-all detection, integrations. Use when asking 'how do I do X in SafetyMails', verifying emails with SafetyMails, cleaning email lists in SafetyMails, setting up SafetyMails API/JavaScript embed, using SafetyMails Email Finder, or managing SafetyMails integrations. Do NOT use for general deliverability strategy across tools (use /sales-deliverability), general enrichment strategy (use /sales-enrich), building prospect lists (use /sales-prospect-list), or connecting tools generically (use /sales-integration).