Run any Skill in Manus with one click

conversion-forms-checkout-polish

Stars54

Forks24

UpdatedJune 21, 2026 at 20:33

Design and polish website conversion flows. Use for CTAs, lead forms, booking forms, newsletter signup, checkout, pricing, contact pages, service inquiries, ecommerce purchase paths, error states, validation, trust signals, and conversion sections that must feel complete and credible.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

TheGoat395

TheGoat395/Codex-Skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

File Explorer

3 files

SKILL.md

readonly

name	conversion-forms-checkout-polish
description	Design and polish website conversion flows. Use for CTAs, lead forms, booking forms, newsletter signup, checkout, pricing, contact pages, service inquiries, ecommerce purchase paths, error states, validation, trust signals, and conversion sections that must feel complete and credible.

Conversion Forms Checkout Polish

Overview

Make action paths clear and trustworthy. A premium site still needs the user to act. Conversion design should feel calm, specific, and complete.

Website Nonnegotiables

Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands.
Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix.
Use existing project conventions first. Explain major new dependencies before adding them.
Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes.
Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again.
Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly.
Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

Workflow

Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability.
Inspect the project before editing when code exists.
Apply this skill's specific rules from references/conversion-forms-checkout-polish-guide.md.
Explain planned files before major changes unless the user has clearly said to proceed.
Build, inspect, polish, and verify before final delivery.

Reference

Read references/conversion-forms-checkout-polish-guide.md when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

More from this repository

same repository

design-motion-principles

TheGoat395/Codex-Skills

Motion and interaction design skill using interpretive lenses informed by publicly available work from Emil Kowalski, Jakub Krehel, and Jhey Tompkins. Two modes: build interactive components with purposeful motion, or audit existing animations to catch AI-generated motion anti-patterns. Use when creating, adding, animating, or reviewing UI motion: transitions, hover states, micro-interactions, enter/exit animations, or motion design work in React, Framer Motion, CSS, or HTML. This skill is not authored, reviewed, or endorsed by the referenced designers.

2026-07-0254

frontend-quality-auditor

TheGoat395/Codex-Skills

Audit frontend websites and apps before launch. Use for production-readiness reviews, visual polish checks, responsive QA, accessibility risks, performance and SEO basics, interaction states, forms, media, copy clarity, trust signals, and ship/no-ship recommendations for React, Next.js, static sites, dashboards, landing pages, portfolios, and product UI.

2026-07-0154

gsap-performance

TheGoat395/Codex-Skills

GSAP performance guidance — prefer transforms, avoid layout thrashing, use will-change selectively, and batch animation work. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.

2026-06-2554

accessibility-audit-websites

TheGoat395/Codex-Skills

Audit website accessibility. Use for semantic structure, headings, alt text, forms, focus states, keyboard navigation, color contrast, labels, ARIA misuse, reduced motion, captions, skip links, modals, menus, carousels, and final frontend QA aligned with WCAG-style accessibility expectations.

2026-06-2154

accessibility-performance-polish

TheGoat395/Codex-Skills

Improve website accessibility and performance polish. Use for semantic HTML, keyboard navigation, focus states, contrast, alt text, reduced motion, image/video loading, canvas fallbacks, bundle caution, animation performance, and final production readiness for polished websites.

2026-06-2154

animation-easing-language

TheGoat395/Codex-Skills

Define animation easing language for premium websites and apps. Use for motion timing systems, easing curves, spring feel, duration scales, stagger rhythm, delay strategy, entrance/exit timing, tactile controls, cinematic sections, and translating luxury, modern, fast, calm, or playful motion words into concrete values.

2026-06-2154

name	conversion-forms-checkout-polish
description	Design and polish website conversion flows. Use for CTAs, lead forms, booking forms, newsletter signup, checkout, pricing, contact pages, service inquiries, ecommerce purchase paths, error states, validation, trust signals, and conversion sections that must feel complete and credible.

Conversion Forms Checkout Polish

Overview

Make action paths clear and trustworthy. A premium site still needs the user to act. Conversion design should feel calm, specific, and complete.

Website Nonnegotiables

Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands.
Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix.
Use existing project conventions first. Explain major new dependencies before adding them.
Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes.
Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again.
Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly.
Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

Workflow

Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability.
Inspect the project before editing when code exists.
Apply this skill's specific rules from references/conversion-forms-checkout-polish-guide.md.
Explain planned files before major changes unless the user has clearly said to proceed.
Build, inspect, polish, and verify before final delivery.

Reference

Read references/conversion-forms-checkout-polish-guide.md when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.