aigent-landing-page-polish
Skill4 starsChanged 3 months agoMITView on GitHub
Improve landing pages with AIgent conversion, copy, layout, button, pricing, mobile, and premium visual polish. Use when a page needs sharper hero text, better CTA hierarchy, less jargon, stronger FOMO, cleaner pricing, reduced repetition, responsive fixes, GSAP text reveal, or higher-end visual taste without breaking the existing design.
In this repository26 other files it gives its agents.
- aigentSkill
- aigent-3d-scroll-systemSkill
- aigent-asset-gallery-systemSkill
- aigent-business-sitesSkill
- aigent-designSkill
- asset-provenance-auditSkill
- cinematic-asset-gallerySkill
- cinematic-site-qaSkill
- cinematic-studioSkill
- cinematic-web-directorSkill
- creative-asset-directorSkill
- design-forensicsSkill
- design-resolverSkill
- gsap-scroll-choreographySkill
- hyperframes-videoSkill
- inspiration-originality-auditSkill
- modular-scroll-pageSkill
- publish-siteSkill
- reference-synthesisSkill
- remotion-web-assetsSkill
- spline-web-sceneSkill
- threejs-web-sceneSkill
- video-asset-pipelineSkill
- video-scrub-deckSkill
- visual-design-criticSkill
- web-3d-asset-pipelineSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 14 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
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
- Distinctive: line 8
Use this skill when a landing page already exists but needs to convert better and feel more premium.
- Distinctive: line 23
Put the outcome in the headline.
- Distinctive: line 24
Put mechanism in the subhead.
- Distinctive: line 25
Avoid jargon in the first viewport unless the audience already uses it.
- Distinctive: line 26
Do not say the same thing in subtext and cards.
- Distinctive: line 27
Use FOMO carefully: founder price, limited run, first access, before it gets crowded.
- Distinctive: line 32
Keep button dimensions stable when prices are added.
- Distinctive: line 33
Avoid cheap 3D effects.
- Distinctive: line 34
Add hover motion: subtle lift, glint, border light.
- Distinctive: line 35
Place guarantee/subscription clarity near the CTA.
- Distinctive: line 39
Use fewer visual tricks, better executed.
- Distinctive: line 40
Do not use gradient blobs or decorative filler.
- Very specific: line 41
Use real media, generated media, Spline, Three.js, or frame sequences for hero depth.
- Distinctive: line 55
If the page feels impressive but unclear, simplify the copy.
- Distinctive: line 56
If the page is clear but dull, improve the scene, type, and motion.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
AIgent Landing Page Polish
Use this skill when a landing page already exists but needs to convert better and feel more premium.
First Pass
Check:
- What is the page selling?
- Who already understands the terms?
- What pain does the hero name?
- What is the proof?
- What action should the visitor take?
Copy Rules
- Shorter is usually better.
- Put the outcome in the headline.
- Put mechanism in the subhead.
- Avoid jargon in the first viewport unless the audience already uses it.
- Do not say the same thing in subtext and cards.
- Use FOMO carefully: founder price, limited run, first access, before it gets crowded.
CTA Rules
- Button label should name the product or action.
- Keep button dimensions stable when prices are added.
- Avoid cheap 3D effects.
- Add hover motion: subtle lift, glint, border light.
- Place guarantee/subscription clarity near the CTA.
Premium Visual Rules
- Use fewer visual tricks, better executed.
- Do not use gradient blobs or decorative filler.
- Use real media, generated media, Spline, Three.js, or frame sequences for hero depth.
- Cards should have stable dimensions and enough breathing room.
- Text must never touch or overlap.
Mobile Rules
- H1 must fit.
- CTA must be reachable without hunting.
- Sticky elements must not cover content.
- Font sizes must remain readable.
- Screenshots decide, not assumptions.
Final Check
If the page feels impressive but unclear, simplify the copy. If the page is clear but dull, improve the scene, type, and motion.
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
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.

