conversion-forms-checkout-polish

Files (3)

• SKILL.md
• openai.yaml · agents/
• conversion-forms-checkout-polish-guide.md · references/

SKILL.md (first lines)

# 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.

## Scoped execution

Apply the [shared web contract](../website-operating-rules/references/scoped-web-contract.md) once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

## Workflow

1. Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability.
2. Inspect the project before editing when code exists.
3. Apply this skill's specific rules from `references/conversion-forms-checkout-polish-guide.md`.
4. State material planned changes and proceed within existing authorization.
5. For implementation, build and inspect affected states, fix material defects and verify. For analysis or artifact-only requests, deliver that result with its evidence limits.

## Reference

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

## Scope and evidence

Separate visual/state polish from integration certification. Record the authorized test environment and trigger/input/success/failure evidence. A real send, purchase or charge requires its actual authorization; prefer test submissions within the agreed boundary.

From TheGoat395/Codex-Skills, MIT.

More from TheGoat395/Codex-Skills