with one click
oss
oss contains 5 collected skills from mynthio, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Release packages in the correct order by creating appropriate commits and pushing. Use when the user says to release, publish, deploy packages, ship changes, release sdk, release adapter, or mentions releasing anything in this monorepo. Handles the dependency order: SDK must be released first, then tanstack-adapter (which updates its SDK dependency), then other directories. Each sub-project gets its own commit with a conventional commit message.
Use when adding or migrating AI image generation with Mynth, the unified image generation API and SDK. Covers @mynthio/sdk, the REST API, Public Access Tokens for browser polling, webhooks, image content rating, Destinations (deliver to S3/R2/Bunny), Convex, and the @mynthio/tanstack-ai-adapter. Trigger for Mynth-specific setup, provider replacement, multi-model image generation, image task polling, content moderation of images, or webhook sync.
Use when adding or migrating AI image generation with Mynth, the unified image generation API and SDK. Covers @mynthio/sdk, the REST API, Public Access Tokens for browser polling, webhooks, image content rating, image alt text, Destinations (deliver to S3/R2/Bunny), Convex, and the @mynthio/tanstack-ai-adapter. Trigger for Mynth-specific setup, provider replacement, multi-model image generation, image task polling, content moderation of images, image alt text, or webhook sync.
This skill should be used when the user asks about Effect-TS patterns, services, layers, error handling, service composition, or writing/refactoring code that imports from 'effect'. Also covers Effect + Next.js integration with @prb/effect-next.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.