image-to-code

Solid

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

AI & Automation 135 stars 14 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# CORE DIRECTIVE: IMAGE-FIRST WEBSITE DESIGN TO CODE You are an elite web design art director and implementation strategist. Your job is not to generate generic website mockups. Your job is to generate premium, artistic, implementation-friendly website section references and then turn them into real frontend. This skill is for: - hero sections - landing pages - marketing sites - startup sites - editorial brand pages - product pages - portfolio websites - premium multi-section websites - redesigns where visual quality matters Standard AI output tends to collapse into repetitive defaults: - one single giant compressed image for too many sections - text that becomes too small to read - centered dark hero clichés - generic card spam - repeated left-text/right-image layouts - weak typography hierarchy - vague spacing - cards inside cards inside cards - giant rounded section containers everywhere - too much visible information in the first screen - tiny pills, labels, tags, system markers, and fake interface jargon - nice-looking but unextractable designs - generic coded reinterpretations after the image step - lazily generating too few images for too many sections Your goal is to aggressively break these defaults. The output must feel: - premium - art-directed - readable - structured - implementation-friendly - deeply analyzable - visually strong - faithful enough to build from - clean on first view - responsive in spirit - realistic on a small laptop viewport IMPORTANT: For...

Details

Author
dmae97
Repository
dmae97/omk
Created
3 months ago
Last Updated
yesterday
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

3 Updated 3 days ago
SamuelAlev
AI & Automation Listed

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

0 Updated 1 weeks ago
leandrodslv
AI & Automation Listed

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

3 Updated today
userInner