Cta Language Systems

CTA Language Systems

Use this skill to make every action label tell users what happens next.

Workflow

• Inspect the page goal, audience, offer/product reality, source copy, proof, IA, forms, SEO/social metadata, brand voice, and verification commands.
• Read CTA Language Systems Guide before changing headings, sections, CTAs, metadata, labels, or UI copy.
• Draft from evidence: real product/service facts, proof, objections, user tasks, and constraints.
• Replace generic claims with specific language or remove them.
• Inspect the rendered page on desktop and mobile for hierarchy, wrapping, repetition, and whether copy still matches the UI.

Always Protect

• Inspect before writing or coding: audience, offer, product/service reality, source copy, assets, proof, claims, conversion goal, information architecture, SEO/metadata needs, forms, legal/trust constraints, and available verification commands.
• Use copy to make the design more specific: every headline, label, CTA, section, and proof point should reduce ambiguity rather than decorate the layout.
• Avoid generic premium language, vague transformation claims, placeholder testimonials, fake metrics, empty adjectives, and hero copy that could fit any brand.
• Write in the user's domain vocabulary while keeping language clear, concise, concrete, and scannable.
• Tie claims to proof: screenshots, artifacts, reviews, credentials, specifications, case studies, pricing terms, process details, or real outcomes.
• Keep navigation, forms, pricing, FAQs, and CTAs honest and task-focused; do not create dark patterns or hide material terms.
• Respect accessibility and structure: semantic headings, meaningful link/button text, labeled forms, useful error/help text, readable line lengths, and no critical copy trapped in images.
• Before delivery, inspect rendered desktop and mobile copy for hierarchy, wrapping, overflow, repetition, and whether the words still match the implemented page.