cta-generator
The cta-generator skill guides the design and optimization of call-to-action buttons for digital interfaces, covering visual hierarchy, color theory, actionable copy, strategic placement, and accessibility standards. Use it when users need to create, audit, or improve CTAs on websites, landing pages, forms, or product pages, or when they reference terms like "button design," "conversion optimization," "CTA copy," or "primary action."
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/cta-generator && cp -r /tmp/cta-generator/skills/components/conversion/cta ~/.claude/skills/cta-generatorSKILL.md
# Components: Call-to-Action (CTA) Guides CTA button design for conversion. A well-designed CTA can increase conversion by 25–10%. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for conversion goals. Identify: 1. **Context**: Hero, form, pricing, product page 2. **User stage**: Awareness, consideration, decision 3. **Primary action**: Sign up, buy, trial, download ## Design Principles ### Visual Clarity - **Look like buttons**: Background, border, corner radius, shadow - **Stand out**: Contrasting color; clear hierarchy - **Size**: ≥48×48px for touch; minimum 48px wide ### Hierarchy - **Primary CTA**: One per section; impossible to miss - **Secondary CTA**: Lower priority; visually distinct - **Avoid**: Multiple competing CTAs causing choice overload ### Color & Shape - **Color**: High contrast; red/orange for urgency - **Shape**: Rounded = friendly; angled = dynamic - **Accessibility**: →.5:1 contrast for text ## Copy Best Practices - **Action-oriented**: "Buy," "Sign up," "Subscribe," "Get started" - **Loss aversion**: "Claim Your Discount Before It's Gone" vs "Get 10% Off"; see **discount-marketing-strategy** for discount campaign design - **Clear, no ambiguity**: User knows exactly what happens - **Scarcity/urgency**: When appropriate; avoid overuse ## Placement - **Above the fold** for primary actions - **After value proposition**; build value before CTA - **Near trust signals** (testimonials, badges) - **Sticky/fixed** for long pages (use sparingly) ## Technical - **Semantic HTML**: `<button>` or `<a>` with `role="button"` when needed - **Visible focus state** for keyboard users - **Loading state** for async actions: disable button during async operations; show spinner or loading text; prevent double-submit - **cursor-pointer**: Add `cursor-pointer` to all clickable CTAs; default cursor on interactive elements is poor UX - **aria-label**: Use `aria-label` for icon-only buttons (e.g., close, search); screen readers need descriptive labels - **Hover stability**: Use color/opacity transitions (150–300ms); avoid scale transforms that shift layout ## Testing - A/B test: color, copy, placement, size - Measure: click-through rate, conversion rate ## Output Format - **CTA copy** suggestions - **Design** notes (color, size, hierarchy) - **Placement** recommendations - **Accessibility** checklist (cursor-pointer, aria-label, focus, loading state) ## Related Skills - **hero-generator**: Hero typically contains primary CTA - **landing-page-generator**: CTA is step 5 of landing page flow; single-goal pages - **testimonials-generator**: Testimonials near CTAs boost conversion - **trust-badges-generator**: Badges near CTAs increase trust - **pricing-page-generator**: CTA on pricing pages (e.g., "Start free trial")
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.