Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).

Generate spectrograms and feature-panel visualizations from audio with the songsee CLI.

iMessage/SMS CLI for listing chats, history, and sending messages via Messages.app.

Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).

Generate spectrograms and feature-panel visualizations from audio with the songsee CLI.

iMessage/SMS CLI for listing chats, history, and sending messages via Messages.app.

Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.

Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Configure Langfuse across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Langfuse configurations. Trigger with phrases like "langfuse environments", "langfuse staging", "langfuse dev prod", "langfuse environment setup", "langfuse config by env".

Conducts a comprehensive security review of a git repo. Use when asked about security issues, code quality concerns, or to evaluate the security posture of a codebase or library.

Configure Juicebox multi-environment. Trigger: "juicebox environments", "juicebox staging".

Deploy Juicebox integrations. Trigger: "deploy juicebox", "juicebox production deploy".

Execute Juicebox people search with power filters and ATS export. Trigger: "find candidates", "people search", "juicebox search".

Implement Instantly.ai webhook event handling with real API v2 event types. Use when setting up webhook endpoints, processing email events, or building CRM sync pipelines from Instantly notifications. Trigger with phrases like "instantly webhook", "instantly events", "instantly webhook handler", "handle instantly events", "instantly notifications".

Collect Instantly.ai debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or auditing campaign/account state. Trigger with phrases like "instantly debug", "instantly support ticket", "instantly diagnostic", "instantly audit", "collect instantly evidence".

Migrate between Ideogram API versions (V_1 to V_2 to V3) with breaking change detection. Use when upgrading from legacy to V3 endpoints, updating model versions, or handling deprecated API parameters. Trigger with phrases like "upgrade ideogram", "ideogram migration", "ideogram v2 to v3", "ideogram breaking changes", "migrate ideogram API".

Optimize Ideogram costs through model selection, caching, and usage monitoring. Use when analyzing Ideogram billing, reducing API costs, or implementing budget alerts and usage tracking. Trigger with phrases like "ideogram cost", "ideogram billing", "reduce ideogram costs", "ideogram pricing", "ideogram budget", "ideogram credits".

Automate the ClaimCenter FNOL→investigation→reserve→payment→settlement→close pipeline including the failure paths — duplicate FNOL from multi-source intake, reserve-must-precede-payment ordering, supervisor-authorization tiers, premature settlement, and reopen-vs-new-claim ambiguity. Use when building claim intake from caller portals, IVR, or partner systems; automating reserve-setting jobs; or integrating settlement events with finance. Trigger with "claimcenter automation", "FNOL", "claim reserve", "claim payment", "claim settlement", "claim reopen".

Build event-driven architectures with Groq streaming, batch processing, and async patterns. Use when setting up real-time SSE endpoints, batch processing pipelines, or event-driven LLM processing with Groq. Trigger with phrases like "groq streaming", "groq events", "groq SSE", "groq batch", "groq async", "groq event-driven".