Email composition and templates
biopython
by ovachiever
"Primary Python toolkit for molecular biology. Preferred for Python-based PubMed/NCBI queries (Bio.Entrez), sequence manipulation, file parsing (FASTA, GenBank, FASTQ, PDB), advanced BLAST workflows, structures, phylogenetics. For quick BLAST, use gget. For direct REST API, use pubmed-database."
architecture-patterns
by ovachiever
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
billing-automation
by ovachiever
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
formisch-usage
by open-circle
Form handling with Formisch, the type-safe form library for modern frameworks. Use when the user needs to create forms, handle form state, validate form inputs, or work with Formisch.
Ruby OOP Patterns
by Kaakati
Comprehensive guide to Object-Oriented Programming in Ruby and Rails covering classes, modules, design patterns, SOLID principles, and modern Ruby 3.x features
Testing Patterns
by Kaakati
"Unit, widget, integration, and golden test patterns with mocking strategies"
error-handling-patterns
by Kaakati
"Expert error handling decisions for iOS/tvOS: when to use throws vs Result, error type design trade-offs, recovery strategy selection, and user-facing error presentation patterns. Use when designing error hierarchies, implementing retry logic, or deciding how to surface errors to users. Trigger keywords: Error, throws, Result, LocalizedError, retry, recovery, error presentation, do-catch, try, error handling, failure"
GetX State Management Patterns
by Kaakati
"GetX controllers, reactive state, dependency injection, bindings, navigation, and best practices"
Exploring Alternatives
by obra
Try 2-3 different approaches before implementing - don't settle for first design you think of
Formily Ant Design Components
by whinc
This skill should be used when the user asks to "use formily with ant design", "formily antd components", "formily ant design integration", "formily form layout", "formily form.item", "formily antd forms", or "integrate formily with ant design".
SwiftUI Programming Skill
by fal3
Expertise in SwiftUI for building declarative user interfaces, including SF Symbols integration and best practices.
Formily Migration Guide
by whinc
This skill should be used when the user asks to "convert to formily", "formily migration", "migrate forms to formily", "convert react forms to formily", "formily vs other form libraries", or "replace existing forms with formily".
email-notify
by caopulan
Send SMTP email notifications after Codex completes a task. Use when one Codex or Claude run is finished, or when you need to notify on task completion with device name, project name, status, and summary via email.
rails-ai:mailers
by zerobearing2
Use when sending emails - ActionMailer with async delivery via SolidQueue, templates, previews, and testing
typescript-type-safety
by marcioaltoe
TypeScript type safety including type guards and advanced type system features. ALWAYS use when writing ANY TypeScript code (frontend AND backend) to ensure strict type safety, avoid any types, and leverage the type system. Examples - "create function", "implement class", "define interface", "type guard", "discriminated union", "type narrowing", "conditional types", "handle unknown types".
naming-conventions
by marcioaltoe
Expert in naming conventions for files, directories, classes, functions, and variables. ALWAYS use when creating ANY files, folders, classes, functions, or variables, OR when renaming any code elements. Use proactively to ensure consistent, readable naming across the codebase. Examples - "create new component", "create file", "create folder", "name this function", "rename function", "rename file", "rename class", "refactor variable names", "review naming conventions".
clean-architecture
by marcioaltoe
Clean Architecture principles for Modular Monolith with bounded contexts and minimal shared kernel. ALWAYS use when working on backend code, ESPECIALLY when creating files, deciding file locations, or organizing contexts (auth, tax, bi, production). Use proactively to ensure context isolation and prevent "Core Obesity Syndrome". Examples - "create entity", "add repository", "where should this file go", "modular monolith", "bounded context", "shared kernel", "context isolation", "file location", "layer organization".
better-auth
by oakoss
Self-hosted TypeScript auth framework with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Supports Drizzle/Prisma/Kysely adapters. Self-hosted alternative to Clerk/Auth.js. Use when: configuring auth, adding plugins, social OAuth, multi-tenant SaaS, organizations with teams and RBAC, two-factor authentication (TOTP/OTP/backup codes), email verification, password reset flows, session management, rate limiting, CSRF and cookie security, Expo/mobile, D1 adapter errors, TanStack Start integration, additionalFields bugs, admin plugin, migrating from NextAuth, migrating from Clerk, migrating from Supabase Auth, or troubleshooting auth issues.
backend-engineer
by marcioaltoe
Backend engineering with Modular Monolith, bounded contexts, and Hono. ALWAYS use when implementing ANY backend code within contexts, Hono APIs, HTTP routes, or service layer logic. Use proactively for context isolation, minimal shared kernel, and API design. Examples - "create API in context", "implement repository", "add use case", "context structure", "Hono route", "API endpoint", "context communication", "DI container".
error-handling-patterns
by marcioaltoe
Error handling patterns including exceptions, Result pattern, validation strategies, retry logic, and circuit breakers. ALWAYS use when implementing error handling in backend code, APIs, use cases, or validation logic. Use proactively for robust error handling, recovery mechanisms, and failure scenarios. Examples - "handle errors", "Result pattern", "throw exception", "validate input", "error recovery", "retry logic", "circuit breaker", "exception hierarchy".
outreach-and-prospecting
by JK-0001
Run cold and warm outreach campaigns to find and engage potential customers or partners. Use when building a prospecting pipeline, writing cold emails or LinkedIn messages, identifying and qualifying leads, planning an outreach strategy, or scaling lead generation as a solopreneur. Covers lead identification, qualification frameworks, cold email writing, LinkedIn outreach, multi-touch sequences, and tracking. Trigger on "cold outreach", "prospecting", "find customers", "cold email", "LinkedIn outreach", "lead generation", "outreach strategy", "build a pipeline", "find clients".
email-marketing
by dmend3z
This skill transforms Claude into a world-class email marketing specialist following Andre Chaperon's Soap Opera Sequence methodology and Frank Kern's Behavioral Dynamic Response framework. Use it for story-driven email campaigns, automated sequences, behavioral triggers, list building, segmentation, and deliverability optimization. Covers Open Loops, Seinfeld Emails, and intent-based sequencing.
affiliate-onboarding
by dmend3z
This skill guides users in setting up a robust affiliate onboarding system. It covers welcome sequences, swipe file creation, training curriculum, compliance guidelines, resource library setup, first promotion guidance, and communication templates to transform new affiliates into high-performing partners.
marketing-automation
by dmend3z
This skill transforms Claude into a marketing automation specialist, capable of designing, implementing, and optimizing automated marketing campaigns. It should be used when a user needs to create a welcome series for new subscribers, recover abandoned carts, nurture leads through the sales funnel, or engage customers post-purchase. Activate this skill when users mention terms like "marketing automation," "email drip campaign," "lead scoring," "customer journey," or "automated workflows."