Email composition and templates
ruby
by miles990
Ruby programming patterns and idioms
junior-developer
by dangeles
Use when implementing well-scoped Python tasks with clear requirements, writing unit tests, and producing documented code for senior-developer review.
communication-tracker
by legacybridge-tech
Track and integrate external communications (emails, chat messages, screenshots) into project context with timeline management. Use when user mentions "email", "message", "communication", "screenshot", "track", "import", "sync", or wants to import external information sources into the project timeline.
popup-cro
by almeidamarcell
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
email-sequence
by almeidamarcell
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
service-integration
by mgd34msu
"Load PROACTIVELY when task involves connecting external services or third-party APIs. Use when user says \"add email sending\", \"integrate a CMS\", \"set up file uploads\", \"add analytics\", or \"connect to S3\". Covers email services (Resend, SendGrid), CMS platforms (Sanity, Contentful, Payload), file upload solutions (UploadThing, Cloudinary, S3), analytics integration, webhook handling, error recovery, and credential management."
todo-complete
by legacybridge-tech
Mark a todo as complete and archive it
onboarding-cro
by almeidamarcell
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
copywriting
by almeidamarcell
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
dry-principle
by joabgonzalez
"Eliminate knowledge duplication via abstraction. Trigger: When same logic appears 3+ times or changing one place requires updating others."
clean-architecture
by joabgonzalez
"Layer-based architecture with inward dependency rule. Trigger: When separating business logic from frameworks, databases, and external services."
form-cro
by almeidamarcell
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
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".
dbt
by jpoutrin
dbt (data build tool) patterns for data transformation and analytics engineering. Use when building data models, implementing data quality tests, or managing data transformation pipelines.
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".
content_strategist
by vuralserhat86
Creates high-quality, SEO-optimized content that ranks in search engines. Applies on-page SEO best practices, keyword optimization, and content structure for maximum visibility and engagement.
better_auth
by vuralserhat86
The ultimate authentication and authorization skill. Implement login, signin, signup, registration, OAuth, 2FA, MFA, passkeys, and user session management. Secure your application with RBAC and access control.
email_composer
by vuralserhat86
Profesyonel e-posta yazma, business communication ve template oluşturma rehberi.
cold_email
by vuralserhat86
Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead generation emails.
Convex Agents Tools
by Sstobo
"Enables agents to call external functions, APIs, and database operations through tool definitions. Use this when agents need to fetch data, perform actions, or integrate with external services while maintaining clean separation."
rails-ai:mailers
by zerobearing2
Use when sending emails - ActionMailer with async delivery via SolidQueue, templates, previews, and testing