agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/conversion-forms-checkout-polish/SKILL.md

conversion-forms-checkout-polish

Skill136 starsChanged 5 months agoMITView on GitHub

Polish conversion journeys and visible states.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability.

    line 18
  2. Very specific:

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

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.