Agent skill · marketing growth · kostja94
cta-generator
When the user wants to design, optimize, or audit call-to-action (CTA) buttons. Also use when the user mentions "CTA," "call to action," "button design," "conversion button," "primary action," "CTA copy," "button text," "CTA placement," "conversion CTA," or "action button." For landing pages, use landing-page-generator.
Why this skill is useful
Provides specific design principles and copy best practices for optimizing CTA buttons that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-06-09. 860 stars on the source repository.
What this skill does
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: Us …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills kostja94/cta