Skip to content

Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages

Update frontend image skill prompt

Leonxlnx7f1eb201552d
diff --git a/skills/images-taste-skill/SKILL.md b/skills/images-taste-skill/SKILL.md
index 1405dd6..21b3719 100644
--- a/skills/images-taste-skill/SKILL.md
+++ b/skills/images-taste-skill/SKILL.md
@@ -1,171 +1,323 @@
---
name: image-taste-frontend
-description: Elite frontend image-direction skill for generating premium, artistic, implementation-friendly website design references. Uses combinatorial variation to avoid repetitive AI aesthetics, enforces cinematic hero minimalism, strong hierarchy, generous spacing, image-led composition, and anti-slop visual discipline. For visual frontend tasks, this skill must first generate the design image(s) itself, deeply analyze them, then implement the frontend to match them as closely as possible.
+description: 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 not compress many sections into one tiny unreadable board. It should prefer many large, readable, section-specific images and create extra detail images whenever needed for clean extraction of text, typography, spacing, buttons, colors, and component structure.
---
-# CORE DIRECTIVE: AWWWARDS-LEVEL IMAGE ART DIRECTION
-You are an elite frontend image art director.
+# 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 AI art.
-Your job is to generate highly creative, premium, frontend design reference images that feel like real high-end website concepts.
+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.
-Standard image generation tends to collapse into repetitive defaults:
-- centered dark hero
-- purple/blue AI glow
-- floating meaningless blobs
-- generic dashboard card spam
+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
-- cloned sections
-- “luxury” that is just beige serif text
-- “creative” that is actually messy and unreadable
-- text-heavy layouts with not enough imagery
-- overly dense sections with no breathing room
+- vague spacing
+- 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:
-- art-directed
- premium
-- visually memorable
-- structured
+- art-directed
- readable
+- structured
- implementation-friendly
-- clearly usable as a frontend reference
-
-Do not generate random mood art unless explicitly asked.
-Default to website design comps.
+- deeply analyzable
+- visually strong
+- faithful enough to build from
IMPORTANT:
-For visual frontend tasks, you must first generate the design image or image set yourself.
-Then you must deeply analyze the generated image(s) before implementation.
-Do not begin with implementation first.
-Do not skip the image-generation step when image generation is available.
-The generated image is the primary visual source of truth.
-Only after generating and deeply inspecting the image(s) should you implement the frontend.
+For visual website tasks, you must first generate the design image(s) yourself.
+Then you must deeply analyze the generated image(s).
+Only after that should you implement the frontend.
+
+Do not skip image generation when image generation is available.
+Do not begin with freeform coding first.
+The generated image(s) are the primary visual source of truth.
+
+The required workflow is:
+
+image generation first
+deep image analysis second
+implementation third
+
+If the task is mainly visual, this order is mandatory.
---
## 1. ACTIVE BASELINE CONFIGURATION
- DESIGN_VARIANCE: 8
- `(1 = rigid / symmetrical, 10 = artsy / asymmetric)`
+ `(1 = rigid / conventional, 10 = highly art-directed / asymmetric)`
- VISUAL_DENSITY: 4
- `(1 = airy / gallery-like, 10 = packed / intense)`
+ `(1 = airy / calm, 10 = dense / packed)`
- ART_DIRECTION: 8
`(1 = safe commercial, 10 = bold creative statement)`
- IMPLEMENTATION_CLARITY: 9
- `(1 = loose moodboard, 10 = very codeable UI reference)`
+ `(1 = loose moodboard, 10 = highly buildable UI reference)`
- IMAGE_USAGE_PRIORITY: 9
- `(1 = mostly typographic, 10 = strongly image-led)`
+ `(1 = mostly typographic, 10 = strongly image-led when appropriate)`
- SPACING_GENEROSITY: 8
- `(1 = compact / tight, 10 = very spacious / breathable)`
+ `(1 = compact / tight, 10 = spacious / breathable)`
+- ANALYSIS_PRECISION: 10
+ `(1 = broad vibe only, 10 = deep extraction of design details)`
+- IMAGE_GENERATION_EAGERNESS: 10
+ `(1 = minimal image count, 10 = generate as many images as needed for excellent extraction)`
AI Instruction:
-Use these as global defaults unless the user clearly asks for something else.
-Do not ask the user to edit this file.
-Adapt these values dynamically from the prompt.
+Use these as defaults unless the user clearly wants something else.
+Adapt them to the prompt.
Interpretation:
- If the user says “clean”, reduce density and increase clarity.
- If the user says “crazy creative”, increase variance and art direction.
- If the user says “premium SaaS”, keep clarity high and art direction controlled.
- If the user says “editorial”, allow stronger type and more asymmetry.
-- Bias toward stronger visual concepts, not safe layouts.
-- Use imagery as a core design material, not as decoration.
-- Keep sections breathable. Do not over-pack the page.
-- Prefer slightly more whitespace between sections than default.
+- Keep sections breathable.
+- Prefer readability over squeezing too much into one image.
+- In Codex, bias strongly toward larger, more analyzable section images.
+- If more images would improve extraction quality, generate more images.
+- Do not be lazy with image count.
---
## 2. MANDATORY IMAGE-FIRST RULE
-For frontend design requests where visual quality matters, image generation is mandatory first.
+For website design requests where visual quality matters, image generation is mandatory first.
This means:
-1. generate the design image or multi-image reference set yourself first
+1. generate the design image or image set yourself first
2. deeply inspect and analyze the generated image(s)
-3. extract the visible system from them
+3. extract the design system from them
4. implement the frontend only after that
Do not:
- start with freeform coding
- skip straight to implementation
-- describe a design without first generating it when generation is available
-- rely on memory of “what good frontend looks like” instead of producing the visual reference
+- describe a website without first generating the visual reference when generation is available
+- rely on memory of “good frontend taste” instead of producing the actual reference
-The required workflow is:
+The image is the design source.
+The code is the translation layer.
-image generation first
-deep image analysis second
-implementation third
+---
+
+## 3. GENERATE ENOUGH IMAGES RULE
+
+Generate enough images to make the design truly readable and extractable.
+
+Do not be lazy with image count.
+
+If more images would improve:
+- text readability
+- typography extraction
+- spacing analysis
+- button analysis
+- card analysis
+- color extraction
+- component inspection
+- implementation fidelity
+
+then generate more images.
+
+Strong rule:
+- it is better to generate too many clear images than too few compressed images
+- it is better to generate one clear image per section than one unreadable board for the whole site
+- it is better to create an extra close-up image than to guess details later
+
+Never reduce image count just for convenience if that harms quality.
+
+---
+
+## 4. CODEX-SPECIFIC SECTION IMAGE RULE
+
+Inside Codex, do not compress too many website sections into one single image if that would make the text, spacing, buttons, or layout details too small to analyze properly.
+
+In Codex, prefer separate large images per section.
+
+Default rule inside Codex:
+- 1 section requested → generate 1 image
+- 2 sections requested → generate 2 images
+- 3 sections requested → generate 3 images
+- 4 sections requested → generate 4 images
+- 5 sections requested → generate 5 images
+- 6 sections requested → generate 6 images
+- 7 sections requested → generate 7 images
+- 8 sections requested → generate 8 images
+- 9 sections requested → generate 9 images
+- 10 sections requested → generate 10 images
+- and so on when reasonable
+
+This is preferred because:
+- text stays readable
+- typography becomes analyzable
+- spacing stays visible
+- button details stay visible
+- card styling stays visible
+- extraction quality becomes much better
+- implementation becomes more faithful
+
+Do not default to:
+- one giant multi-column collage
+- one long compressed board with tiny unreadable text
+- one image containing many sections if that reduces extraction quality
+
+If necessary, generate more images rather than shrinking everything.
+
+Outside Codex, this skill may still allow more compact multi-section composition when appropriate.
+Inside Codex, prioritise section clarity and extraction accuracy.
+
+---
+
+## 5. OPTIONAL DETAIL / EXTRACTION IMAGE RULE
+
+If a section image still does not expose the necessary detail clearly enough, generate an additional detail image for that same section.
+
+Examples of useful secondary images:
+- a closer hero crop to read headline, subheadline, CTA, and typography
+- a detail image for pricing cards
+- a closer crop for testimonials
+- a closer crop for navbar / header treatment
+- a closer crop for feature cards or UI panels
+- a closer crop for footer or CTA section
+- a refined variation of the first generated image that makes the section more extractable
+- a cleaner re-generation of the same section with larger text for extraction
+- an image focused mainly on typography and spacing instead of the full composition
+
+These additional images exist to improve analysis and extraction quality.
-If the task is primarily visual, this order is not optional.
+Use them when needed for:
+- readable text
+- clearer button states
+- tighter spacing analysis
+- card and component inspection
+- clearer color extraction
+- better typography observation
+- more precise implementation
+
+Do not hesitate to create a second or third extraction-oriented image for a section if the first image is too broad.
---
-## 3. DEEP IMAGE ANALYSIS REQUIREMENT
+## 6. CLEAN ANALYSIS STANDARD
+
+Analyze cleanly and systematically.
+
+Do not do vague vibe-only analysis.
+Do not jump too fast from image to code.
+
+For every generated section image, inspect cleanly:
+- what the section is
+- what the visual priority is
+- what text is readable
+- what typography relationships are visible
+- what spacing relationships are visible
+- what buttons and controls are visible
+- what card or block logic is visible
+- what colors dominate
+- what structural rhythm is visible
+- what details are still unclear
+
+If something is unclear, generate another image before coding.
+
+The analysis should feel:
+- calm
+- structured
+- exact
+- faithful
+- design-aware
+- implementation-aware
+
+---
+
+## 7. DEEP IMAGE ANALYSIS REQUIREMENT
Before implementing anything, deeply analyze the generated image(s).
Do not just glance at them.
Treat them like a design specification.
-Carefully inspect:
-- page structure
-- hero composition
-- section ordering
-- headline scale
-- subheadline scale
-- spacing system
-- section-to-section rhythm
-- image usage
-- component shapes
-- card logic
-- border radius logic
-- CTA styling
+Carefully inspect and extract:
+- exact visible text where readable
+- hero headline wording
+- subheadline wording
+- CTA wording
+- section titles
+- typography character
+- type scale relationships
+- font mood
+- line count
+- line wrapping behavior
- alignment logic
-- grid behavior
-- color relationships
-- visual density
-- balance between text and media
-- framing and cropping
-- repeated patterns that define the design language
+- section spacing
+- internal spacing
+- padding and gutters
+- card dimensions and rhythm
+- border radius logic
+- stroke / divider usage
+- button shapes
+- button hierarchy
+- button padding
+- hover-implied styling if visually suggested
+- color palette
+- accent colors
+- background treatment
+- image treatment
+- icon treatment
+- shadows / depth logic
+- grid logic
+- layout structure
+- section ordering
+- section density
+- visual rhythm
+- repeated motifs that define the design language
-Your goal is to understand exactly why the generated design looks strong.
+Your goal is to understand exactly why the generated website looks strong.
Only after this deep analysis should you implement the frontend.
---
-## 4. IMAGE-FIRST CODEX WORKFLOW
+## 8. IMAGE-FIRST CODEX WEBSITE WORKFLOW
-When this skill is used inside Codex or any environment that supports image generation plus implementation, default to an image-first workflow for frontend design tasks.
+When this skill is used inside Codex or any environment that supports image generation plus implementation, default to an image-first workflow for website design tasks.
Preferred execution order:
-1. generate the design image or multi-image reference set first
-2. deeply inspect the generated image(s)
-3. extract the layout, spacing, hierarchy, typography character, section rhythm, and component language
-4. implement the frontend to match the generated design as closely as reasonably possible
-5. only invent missing details when the image leaves something ambiguous
-
-For frontend-heavy requests, do not begin by freely designing in code.
-Begin by creating a strong visual reference first whenever image generation is available.
-
-The image is the primary art-direction source.
+1. infer the section count
+2. generate section reference images first
+3. generate extra detail/extraction images where needed
+4. deeply inspect all generated images
+5. extract text, typography, spacing, colors, layout, buttons, and component logic
+6. implement the website to match the generated design as closely as reasonably possible
+7. only invent missing details when the images leave something ambiguous
+
+For visually important frontend tasks, do not begin by freely designing in code.
+Begin by creating the visual references first whenever image generation is available.
+
+The images are the primary art-direction source.
The code is the implementation layer.
-This workflow is especially preferred for:
-- hero sections
-- landing pages
-- marketing sites
-- visually ambitious product pages
-- editorial brand pages
-- redesign requests
-- “make this look premium” tasks
-
---
-## 5. WHEN TO TRIGGER IMAGE GENERATION FIRST
+## 9. WHEN TO TRIGGER IMAGE GENERATION FIRST
If image generation is available, strongly prefer generating image references first when the request is mainly about visual frontend quality.
@@ -174,91 +326,84 @@ Trigger image-first workflow when the user asks for:
- a premium landing page
- a creative website
- a redesign
-- a more modern / more aesthetic / more polished interface
-- a marketing page
+- a more modern website
+- a more aesthetic interface
+- a polished marketing page
- a portfolio site
- a startup site where visual taste matters heavily
- a multi-section website concept
-- anything described primarily in visual terms
-
-Do not default to direct coding first if the main challenge is taste, layout quality, or art direction.
+- anything described mainly in visual terms
-Direct-code first is more acceptable when:
-- the request is mostly technical
+Direct-code first is more acceptable only when:
+- the task is mostly technical
- the user wants a bug fix
- the user already provides a precise design system
-- the task is primarily structural rather than visual
+- the task is mainly structural rather than visual
---
-## 6. THE COMBINATORIAL VARIATION ENGINE
+## 10. THE COMBINATORIAL VARIATION ENGINE
-To avoid repetitive AI-looking output, internally choose one option from each category based on the prompt and commit to it consistently.
+To avoid repetitive AI-looking output, internally choose a strong combination and commit to it consistently.
-Do not mash everything together into chaos.
-Pick a strong combination and execute it clearly.
+Do not mash everything into chaos.
+Pick a coherent visual direction and execute it clearly.
### Theme Paradigm
Choose 1:
-1. Pristine Light Mode
- Off-white / cream / paper tones, sharp dark text, editorial confidence.
-2. Deep Dark Mode
- Charcoal / graphite / zinc, elegant glow only when justified.
-3. Bold Studio Solid
- Strong controlled color fields like oxblood, royal blue, forest, vermilion, or emerald with crisp contrasting UI.
-4. Quiet Premium Neutral
- Bone, sand, taupe, stone, smoke, muted contrast, restrained luxury.
+1. Pristine Light Mode
+2. Deep Dark Mode
+3. Bold Studio Solid
+4. Quiet Premium Neutral
### Background Character
Choose 1:
-1. Subtle technical grid / dotted field
-2. Pure solid field with soft ambient gradient depth
-3. Full-bleed cinematic imagery with proper contrast control
-4. Quiet textured paper / material / tactile surface feel
+1. subtle technical grid / dotted field
+2. pure solid field with soft ambient gradient depth
+3. full-bleed cinematic imagery
+4. tactile textured surface feel
### Typography Character
Choose 1:
-1. Satoshi-like clean grotesk
-2. Neue-Montreal-like refined grotesk
-3. Cabinet / Clash-like expressive display
-4. Monument-like compressed statement typography
-5. Elegant editorial serif + sans pairing
-6. Swiss rational sans with very strong hierarchy
-
-Never drift into boring default web typography energy.
+1. clean grotesk
+2. refined grotesk
+3. expressive display
+4. compressed statement typography
+5. editorial serif + sans
+6. Swiss rational hierarchy
### Hero Architecture
Choose 1:
-1. Cinematic Centered Minimalist
-2. Asymmetric Split Hero
-3. Floating Polaroid Scatter
-4. Inline Typography Behemoth
-5. Editorial Offset Composition
-6. Massive Image-First Hero with restrained text
+1. cinematic centered minimalist
+2. asymmetric split hero
+3. floating polaroid scatter
+4. inline typography behemoth
+5. editorial offset composition
+6. massive image-first hero with restrained text
### Section System
-Choose 1 dominant structure:
-1. Strict modular bento rhythm
-2. Alternating editorial blocks
-3. Poster-like stacked storytelling
-4. Gallery-led visual cadence
+Choose 1:
+1. modular bento rhythm
+2. alternating editorial blocks
+3. poster-like stacked storytelling
+4. gallery-led cadence
5. Swiss grid discipline
-6. Asymmetric premium marketing flow
+6. asymmetric premium marketing flow
### Signature Component Set
Choose exactly 4 unique components:
-- Diagonal Staggered Square Masonry
-- 3D Cascading Card Deck
-- Hover-Accordion Slice Layout
-- Pristine Gapless Bento Grid
-- Infinite Brand Marquee Strip
-- Turning Polaroid Arc
-- Vertical Rhythm Lines
-- Off-Grid Editorial Layout
-- Product UI Panel Stack
-- Split Testimonial Quote Wall
-- Oversized Metrics Strip
-- Layered Image Crop Frames
+- diagonal staggered square masonry
+- 3D cascading card deck
+- hover-accordion slice layout
+- pristine gapless bento grid
+- infinite brand marquee strip
+- turning polaroid arc
+- vertical rhythm lines
+- off-grid editorial layout
+- product UI panel stack
+- split testimonial quote wall
+- oversized metrics strip
+- layered image crop frames
### Motion-Implied Language
Choose exactly 2:
@@ -269,32 +414,31 @@ Choose exactly 2:
- smooth accordion expansion energy
- cinematic fade-through energy
-Important:
These are not coding instructions.
-They are visual-direction cues the generated design should imply.
+They are visual-direction cues the design should imply.
---
-## 7. FRONTEND REFERENCE RULE
+## 11. WEBSITE REFERENCE RULE
-Every generated image must clearly communicate:
+Every generated website section image must clearly communicate:
- layout
-- section hierarchy
+- hierarchy
- spacing
- typography scale
-- visual rhythm
- CTA priority
- component styling
- image treatment
- overall design system
-A developer or coding model should be able to look at the image and understand how to build it.
+A developer or coding model should be able to look at the image(s) and understand how to build the website.
Do not produce vague abstract artwork when the request is for frontend.
+Default to real section comps.
---
-## 8. HERO MINIMALISM RULES
+## 12. HERO MINIMALISM RULES
The hero must feel cinematic, clear, and intentional.
@@ -321,15 +465,12 @@ Do:
- make the first screen feel polished and deliberate
Do not:
-- clutter the hero with too many elements
-- let multiple competing focal points fight each other
-- overfill the hero with cards, labels, or micro-details
-- make the hero feel noisy or busy
+- clutter the hero
+- create multiple competing focal points
+- overfill the hero with cards or micro-details
+- make the hero noisy or busy
### Headline Rule
-The H1 should visually read like a premium statement.
-Do not let it feel long, weak, or overly wrapped.
-
Strong preference:
- 1 line if possible
- 2 lines very good
@@ -340,154 +481,36 @@ Avoid:
- paragraph-like hero copy
- weak headline-to-subheadline contrast
-### Typography Execution
-Prefer:
-- medium / normal / light elegance
-- tight tracking
-- controlled line count
-- strong scale contrast
-
-Avoid:
-- random extra-bold shouting everywhere
-- gradient text as a lazy premium effect
-- 6-line startup headings
-- text treatment that looks generated
-
-### Graphic Restraint
-Do not default to:
-- giant meaningless outline numbers
-- cheap SVG-looking filler graphics
-- generic AI blobs
-- random orb clutter
-
-Use:
-- typography
-- image crops
-- real layout tension
-- premium materials
-- strong framing
-instead.
-
----
-
-## 9. IMAGE COUNT & PAGE SLICING
-
-When the user asks for a frontend design, decide image count based on section count.
-
-### Single-section requests
-If the user asks for one section only:
-- generate exactly 1 image
-
-### Multi-section requests
-Use this rule:
-- 1–2 sections → 1 image
-- 3–4 sections → 1 tall vertical image
-- 5–8 sections → 2 tall vertical images
-- 9–12 sections → 3 tall vertical images
-- 13–16 sections → 4 tall vertical images
-
-### Continuity Rule
-If multiple images are used:
-- treat them as one single website
-- same palette
-- same typography logic
-- same button style
-- same card language
-- same border radius logic
-- same image treatment
-- same overall brand world
-
-Each image must feel like the continuation of the previous one.
-
-### Portrait Preference
-For multi-section outputs:
-- prefer vertical compositions
-- make each image feel like a realistic page slice
-- do not hide layout structure in ultra-wide compositions
-
---
-## 10. CREATIVITY ESCALATION RULE
-
-The design must show real creative ambition.
-
-Do not settle for the first obvious layout solution.
-Push the work beyond generic SaaS patterns.
+## 13. SECTION IMAGE GENERATION RULE
-Actively increase at least 3 of these:
-- stronger composition
-- more distinctive typography
-- more confident scale contrast
-- more memorable hero concept
-- more interesting image treatment
-- more expressive section rhythm
-- more original framing / cropping
-- more art-directed visual tension
-- more surprising but clear layout structure
+Inside Codex, treat each section as its own analyzable unit.
-Creativity must feel intentional, not chaotic.
+If the user asks for:
+- a hero only → generate 1 hero image
+- 4 sections → generate 4 section images
+- 8 sections → generate 8 section images
+- 12 sections → generate 12 section images when reasonable, or a very close equivalent with extra detail images if some can be paired without shrinking text
-Do:
-- make bold but controlled design decisions
-- use asymmetry when it improves the page
-- create visual moments that feel premium and memorable
-- make the page feel designed, not auto-generated
+General preference:
+- one section = one primary image
+- one complex section = one primary image + one or more optional detail images
-Do not:
-- default to safe template layouts
-- repeat the same block structure too often
-- confuse creativity with clutter
-- make the page overly dense
+This section-first generation rule exists to prevent:
+- tiny unreadable text
+- tiny buttons
+- unclear spacing
+- weak extraction quality
+- lossy design-to-code translation
---
-## 11. IMAGE-FIRST ART DIRECTION
-
-This skill must actively use images.
-
-Images are not optional decoration.
-Images are a core part of the frontend design language.
-
-Strongly prefer:
-- art-directed photography
-- product imagery
-- editorial imagery
-- image crops
-- framed image panels
-- layered image compositions
-- image-led hero sections
-- image-supported storytelling blocks
-- multiple purposeful images across the website when appropriate
-
-Use images to:
-- create visual hierarchy
-- break up text-heavy layouts
-- build mood and brand character
-- support section transitions
-- make the design easier to interpret and implement
-- make the site feel visually rich rather than text-only
-
-Important:
-- the design should not become text-only or card-only unless the user explicitly wants that
-- if a page has multiple sections, several sections should meaningfully include imagery
-- if a hero exists, it should usually contain a strong visual image, product visual, or art-directed media element
-- imagery should feel premium and intentional, not like stock filler
-- if the website concept benefits from multiple images, generate and use multiple images within the website design itself, not just one isolated visual
-- different sections may use different image assets, but they must still belong to one coherent design world
-
-Avoid:
-- tiny useless thumbnails
-- random decorative images with no structural role
-- one single image and then a completely text-heavy rest of page
-- overusing fake UI panels instead of real visual variety
-
----
+## 14. WEBSITE IMAGE SYSTEM RULE
-## 12. WEBSITE IMAGE SYSTEM RULE
+When generating a website design, think not only about the overall site but also about the internal image system used inside the website itself.
-When generating a website design, think not only about the full-page reference image, but also about the internal image system used inside the website itself.
-
-This means the website design may contain:
+This may include:
- hero media
- section images
- editorial crops
@@ -497,26 +520,20 @@ This means the website design may contain:
- gallery-like blocks
- supporting visual panels
-If the site structure benefits from multiple images, include multiple images across the website composition.
-
-Examples:
-- hero with one large visual + feature section with 2–4 supporting image panels
-- editorial landing page with repeated large image moments between text sections
-- product page with hero render, detail crops, lifestyle panels, and supporting showcase blocks
-- multi-section marketing site with different section visuals that still share one art direction
+If the site benefits from multiple images, include multiple image moments across the website.
Rules:
-- images inside the website should feel deliberate and curated
+- image usage must feel deliberate
- image count should match the complexity of the site
-- do not rely on a single hero image for the whole website if multiple sections clearly need visual support
+- do not rely on one single hero image if many sections need visual support
- keep image usage balanced and clean
-- multiple images must still feel cohesive in color, mood, treatment, and composition
+- all image moments must still feel like one coherent design world
---
-## 13. FIXED MEDIA FRAME RULE
+## 15. FIXED MEDIA FRAME RULE
-Images used inside the website should usually sit inside clear, controlled, implementation-friendly frames.
+Images inside the website should usually sit inside clear, controlled, implementation-friendly frames.
Prefer:
- fixed-aspect media blocks
@@ -525,149 +542,233 @@ Prefer:
- consistent corner radius logic
- stable visual proportions across similar sections
-Examples of preferred image frame behavior:
+Examples:
- hero image in a clearly bounded large frame
- editorial crops using repeatable portrait or landscape ratios
- card images with consistent proportions
- gallery blocks with controlled aspect ratios
-- product images placed in stable, intentional containers
+- product images placed in stable intentional containers
Avoid:
- random image sizes with no system
- inconsistent proportions across similar modules
-- messy image scaling that weakens implementation clarity
+- messy scaling
- uncontrolled collage chaos unless explicitly requested
The goal is:
- visually strong images
-- but inside a system that a frontend model can realistically rebuild
+- inside a system a frontend model can realistically rebuild
---
-## 14. DESIGN-TO-CODE COPY DISCIPLINE
+## 16. TEXT EXTRACTION RULE
-After generating the reference image(s), implement the design in a copy-oriented way.
+When text is readable in the generated section image, extract it and use it.
-This means:
-- follow the reference closely
-- preserve the layout logic
-- preserve spacing rhythm
-- preserve section ordering
-- preserve image/text balance
-- preserve the typography mood
-- preserve the component style
-- preserve the overall visual tension and cleanliness
+Especially inspect and extract:
+- hero headline
+- hero subheadline
+- CTA labels
+- section headings
+- pricing labels
+- feature names
+- testimonial names and roles if clearly shown
+- navbar labels
+- footer labels if relevant
-Do not drift into a different design direction during implementation.
-Do not “improve” the design by replacing it with a generic coded layout.
-Do not collapse the composition into standard AI-coded patterns.
+If the text is too small to extract reliably:
+- generate a closer extraction image
+- or generate a second clearer version of that section
-The goal is not:
-- “inspired by the image”
+Do not ignore text extraction.
+The visible text is part of the design system and should influence implementation.
-The goal is:
-- “visually faithful to the image, translated into real frontend”
+---
+
+## 17. TYPOGRAPHY EXTRACTION RULE
+
+Do not only notice that typography “looks nice”.
+Analyze it properly.
+
+Extract and observe:
+- size relationships
+- weight relationships
+- line count
+- line height feel
+- tracking feel
+- serif vs sans behavior
+- display vs body contrast
+- section heading rhythm
+- CTA text scale
+- whether the design uses calm or aggressive type
-If some details are ambiguous, resolve them in the same design language rather than inventing a new one.
+Use these findings during implementation.
+Do not flatten typography into a generic coded hierarchy.
---
-## 15. IMAGE ANALYSIS BEFORE IMPLEMENTATION
+## 18. SPACING EXTRACTION RULE
-Before implementing from generated images, analyze them carefully.
+Analyze spacing deliberately.
-Extract and preserve:
-- overall page structure
-- hero composition
-- section sequence
-- dominant alignment logic
-- approximate spacing system
-- typography scale relationships
-- card and panel shapes
-- border radius logic
-- imagery placement
-- visual density
-- CTA treatment
-- color palette and contrast logic
-- decorative motifs only when they are structurally important
+Inspect:
+- distance between headline and subheadline
+- distance between text and buttons
+- distance between cards
+- section top and bottom spacing
+- side gutters
+- card padding
+- image-to-text distance
+- navbar spacing
+- CTA block spacing
+- overall cadence across sections
+
+The goal is not exact pixel OCR.
+The goal is faithful spacing logic.
+
+Do not collapse the implementation into generic tight spacing if the generated design is more generous.
+
+---
+
+## 19. BUTTON / COMPONENT EXTRACTION RULE
+
+Buttons and components must be analyzed, not guessed.
+
+Inspect:
+- button size
+- button shape
+- button radius
+- fill vs outline behavior
+- icon usage
+- hover-implied mood
+- primary vs secondary hierarchy
+- card structure
+- badge usage
+- dividers
+- shadows
+- borders
+- pill logic
+- input styling if present
+
+If button or card detail is too small, generate a closer image.
+
+---
+
+## 20. COLOR EXTRACTION RULE
+
+Actively analyze and extract colors from the generated image(s).
+
+Inspect:
+- background color
+- panel colors
+- accent colors
+- button fills
+- text color hierarchy
+- border color logic
+- shadow color mood
+- image tint / grade
+- gradient restraint or intensity
+
+The implemented website should preserve the original color logic as closely as reasonably possible.
+
+Do not replace a carefully designed palette with generic default web colors.
+
+---
+
+## 21. DESIGN-TO-CODE COPY DISCIPLINE
+
+After generating and analyzing the reference image(s), implement the website in a copy-oriented way.
+
+This means:
+- follow the references closely
+- preserve layout logic
+- preserve spacing rhythm
+- preserve section ordering
+- preserve text/image balance
+- preserve typography mood
+- preserve component style
+- preserve overall visual cleanliness
-Treat the generated image as a design specification, not just inspiration.
+Do not drift into a different design direction during implementation.
+Do not “improve” the design by replacing it with a generic coded layout.
-If multiple images are provided, treat them as one continuous site and maintain consistency across the full implementation.
+The goal is not:
+- inspired by the image
+
+The goal is:
+- visually faithful to the image, translated into real frontend
---
-## 16. ANTI-DRIFT IMPLEMENTATION RULE
+## 22. ANTI-DRIFT IMPLEMENTATION RULE
A common failure mode is design drift:
-the generated image looks strong, but the coded result becomes generic.
+the generated images look strong, but the coded result becomes generic.
Strictly avoid that.
During implementation:
-- do not simplify the layout into a default template
-- do not replace image-led sections with generic card rows
-- do not compress generous spacing into a dense layout
-- do not replace distinctive typography with plain default hierarchy
-- do not turn asymmetric sections into repetitive left-text/right-image blocks
+- do not simplify into default templates
+- do not replace distinctive sections with generic rows
+- do not compress generous spacing into dense layout
+- do not replace strong typography with plain hierarchy
- do not remove the page’s visual identity for convenience
+- do not merge section logic into repetitive patterns that were not present in the source images
-The final coded result should still feel like the same design world as the generated image.
+The final coded result should still feel like the same website as the generated references.
---
-## 17. MISSING DETAIL RESOLUTION
-
-When implementing from an image, some details may be unclear.
+## 23. MISSING DETAIL RESOLUTION
-Resolve missing details by following this priority:
+When implementing from images, some details may still be unclear.
+Resolve ambiguity by following this order:
1. preserve the visible design language
-2. preserve the spacing and hierarchy logic
-3. preserve the component family
-4. preserve the same mood and level of polish
-5. choose the most implementation-friendly version that still feels visually faithful
+2. preserve layout and spacing logic
+3. preserve component family
+4. preserve mood and polish level
+5. generate an extra detail image if needed
+6. only then choose the most implementation-friendly faithful version
-Do not fill ambiguity with generic defaults.
-Fill ambiguity with system-consistent decisions.
+Do not fill ambiguity with generic defaults too quickly.
---
-## 18. ANTI-AI-SLOP RULES
+## 24. ANTI-AI-SLOP RULES
Strictly avoid these patterns unless explicitly requested.
### Layout slop
+- one giant unreadable collage
- endless centered sections
- identical card rows repeated section after section
- cloned left-text/right-image blocks
-- perfect but lifeless symmetry everywhere
- fake complexity without hierarchy
-- empty decorative space with no purpose
+- decorative empty space with no purpose
### Visual slop
- default purple/blue AI gradients
- too many glowing edges
-- floating spheres / blobs everywhere
+- floating blobs everywhere
- glassmorphism stacked without reason
- random futuristic details with no structure
- over-rendered noise that hides the layout
### Typography slop
- giant heading + weak tiny subcopy
-- too many font moods in one page
+- too many font moods
- awkward line breaks
- lazy all-caps everywhere
-- gradient headline as shortcut for “premium”
+- generic gradient headline tricks
### Content slop
-Ban generic copy vibes like:
+Avoid generic filler vibes like:
- unleash
- elevate
- revolutionize
- next-gen
- seamless
-- powerful solution
- transformative platform
Avoid fake brand slop:
@@ -676,30 +777,26 @@ Avoid fake brand slop:
- Flowbit
- Quantumly
- NovaCore
-- obvious nonsense wordmarks
-
-Use short, believable, design-friendly copy.
### Density slop
-- no over-packed sections
-- no card overload in every block
-- no tiny spacing between major sections
-- no trying to fill every empty area
-- no visually exhausting wall-of-content layouts
+- over-packed sections
+- card overload
+- tiny spacing between major sections
+- visually exhausting walls of content
---
-## 19. TYPOGRAPHY-FIRST DISCIPLINE
+## 25. TYPOGRAPHY-FIRST DISCIPLINE
-Typography is not filler.
Typography is a primary design material.
Always ensure:
- clear size contrast
- obvious reading order
- strong display moments
-- supporting text that is readable and brief
-- labels, captions, and section headings that reinforce structure
+- readable body text
+- concise copy
+- section headings that reinforce structure
For editorial directions:
- let typography shape composition
@@ -709,9 +806,9 @@ For tech/product directions:
---
-## 20. SECTION RHYTHM RULE
+## 26. SECTION RHYTHM RULE
-A high-end site does not feel like repeated boxes.
+A high-end site does not feel like the same block repeated forever.
Vary section rhythm across the page by changing:
- density
@@ -723,72 +820,29 @@ Vary section rhythm across the page by changing:
- background intensity
- visual tempo
-Do not let every section feel generated from the same template.
-
-Important:
-- rhythm variation should not break overall cleanliness
-- keep the page visually balanced from top to bottom
-- section heights may vary, but the spacing between sections should feel controlled and fairly even
-- avoid abrupt jumps between very small and very large sections without enough breathing room
-- the full page should feel curated, smooth, and consistent
-
----
-
-## 21. COMPONENT EXECUTION GUIDELINES
-
-### Diagonal Staggered Square Masonry
-Use square image or content blocks with strong staggered vertical rhythm.
-Should feel curated and graphic, not messy.
-
-### 3D Cascading Card Deck
-Cards layered as a physical stack with depth logic.
-Should feel premium and tactile, not gimmicky.
-
-### Hover-Accordion Slice Layout
-A row of compressed visual slices that feel expandable.
-In static images, imply interaction clearly through proportions and emphasis.
-
-### Pristine Gapless Bento Grid
-Mathematically clean grid.
-No accidental gaps.
-Mix large visual blocks with smaller dense information panels.
-
-### Turning Polaroid Arc
-Clustered, rotated imagery with elegant composition.
-Should feel styled and intentional, not scrapbook-random.
-
-### Off-Grid Editorial Layout
-Use asymmetry and tension with control.
-Must remain readable and clearly structured.
-
-### Product UI Panel Stack
-Layer UI screens or interface crops to imply a product story.
-Avoid generic fake dashboards.
-
-### Vertical Rhythm Lines
-Use fine lines and spacing systems to reinforce order and elegance.
-Never let them become decorative clutter.
+But:
+- keep the page coherent
+- keep spacing controlled
+- avoid random jumps
+- keep each section clean enough to analyze well
---
-## 22. DENSITY & SPACING DISCIPLINE
+## 27. DENSITY & SPACING DISCIPLINE
-Do not make everything too dense.
+Do not make the website too dense.
The page should breathe.
-Leave slightly more blank space between sections than a default AI-generated design would.
Rules:
-- use more even vertical spacing between major sections
-- keep section-to-section spacing consistent unless there is a strong design reason not to
-- avoid one section feeling very cramped while the next feels too empty
-- prefer a clean, balanced cadence across the page
-- allow negative space to create rhythm and emphasis
-- separate denser sections with calmer sections
-- avoid stacking too many cards, labels, and content blocks too tightly
-- smaller sections should still receive enough surrounding space so the page feels polished and intentional
-
-A premium page should feel:
+- use even section spacing
+- keep major section gaps controlled and intentional
+- allow negative space to create calmness
+- avoid one section feeling cramped while the next feels empty
+- smaller sections should still have enough surrounding space
+- prefer analyzable generous spacing over compressed compositions
+
+A premium website should feel:
- open
- composed
- balanced
@@ -800,66 +854,11 @@ Not:
- noisy
- uneven
- overfilled
-- visually exhausted
-
-Section rhythm should alternate with control:
-- some sections can be more content-rich
-- some sections can be smaller and calmer
-- but the overall spacing cadence should still feel even, clean, and deliberate
-
-Whitespace is a design tool.
-Use it deliberately.
-Do not let spacing become random.
+- visually exhausting
---
-## 23. COLOR & MATERIAL RULES
-
-### Palette Discipline
-Use one controlled palette with one or two accents at most.
-
-### Strong guidance
-- avoid rainbow randomness
-- avoid over-neon unless requested
-- avoid generic startup gradient dependence
-- keep contrast intentional
-- match accent colors to the chosen theme paradigm
-
-### Materiality
-Where appropriate, add:
-- paper feel
-- glass feel
-- brushed metal feel
-- soft blur depth
-- tactile matte surfaces
-- editorial photo treatment
-
-But always keep the frontend structure readable.
-
----
-
-## 24. IMAGE / MEDIA DIRECTION
-
-If imagery is present, it must support the layout.
-
-Allowed:
-- art-directed product visuals
-- refined editorial photography
-- UI crops
-- abstract forms with structural purpose
-- framed objects
-- premium texture use
-- campaign-style visuals
-
-Avoid:
-- irrelevant scenery
-- stock-photo clichés
-- decorative junk
-- visuals that overpower the page hierarchy
-
----
-
-## 25. DEFAULT SITE PACKS
+## 28. DEFAULT SECTION PACKS
### 4-section pack
1. Hero
@@ -891,144 +890,142 @@ Avoid:
11. FAQ
12. CTA + footer
+In Codex, these should usually become section-by-section images, not one compressed sheet.
+
---
-## 26. MULTI-IMAGE CONSISTENCY RULE
+## 29. MULTI-IMAGE CONSISTENCY RULE
-For multi-image sites, enforce:
+For multi-image websites, enforce:
- same brand world
- same type scale logic
- same spacing discipline
- same CTA styling
-- same icon or illustration mood
+- same icon mood
- same image treatment
- same tonal language
+- same component family
-Image 2 and 3 must not drift into a different site.
+Image 2, 3, or 8 must not drift into a different website.
---
-## 27. CLARITY CHECK
+## 30. CLARITY CHECK
Before finalizing, verify internally:
-1. Is the hierarchy obvious?
-2. Is the hero clean enough?
-3. Is the design visually distinctive?
-4. Is it free of obvious AI tells?
-5. Is it premium rather than template-like?
-6. Can someone code from this?
-7. If multiple images exist, do they clearly belong together?
-8. Is imagery used strongly enough?
-9. Does the page breathe, or is it too dense?
-10. Is there enough spacing between sections?
-11. Does the creativity feel intentional and premium?
-12. Is the spacing between sections even and controlled?
-13. Do smaller sections still have enough surrounding space to feel clean?
-14. Has the generated image been deeply analyzed before implementation?
-15. Are the website’s internal image moments strong enough and system-consistent?
+1. Has the design been generated first?
+2. Have all generated images been deeply analyzed?
+3. Is the text readable enough?
+4. If not, were extra detail images created?
+5. Were enough images generated, or was the image count too lazy?
+6. Is the hierarchy obvious?
+7. Is the hero clean enough?
+8. Is typography analyzed properly?
+9. Are spacing relationships understood properly?
+10. Are buttons and components extracted properly?
+11. Are colors analyzed properly?
+12. Is the design visually distinctive?
+13. Is it free of obvious AI tells?
+14. Can someone code from this faithfully?
+15. If multiple images exist, do they clearly belong together?
+16. Has Codex avoided compressing too many sections into one tiny image?
+17. Was the analysis clean, structured, and specific?
If not, refine internally before output.
---
-## 28. RESPONSE BEHAVIOR
+## 31. RESPONSE BEHAVIOR
-When the user asks for a frontend design:
+When the user asks for a website design in an image-to-code workflow:
1. infer site type
2. infer number of sections
-3. decide whether image-first workflow should be used
-4. if image generation is available and visual quality is central, generate the design image(s) first
-5. choose image count
-6. choose a strong visual combination
-7. choose 4 signature components
-8. choose 2 motion-implied cues
-9. enforce hero minimalism and keep the hero headline within a clean line count
-10. enforce strong image usage
-11. if the site benefits from it, include multiple images across the website itself
-12. use controlled, fixed-feeling media frames and repeatable image proportions
-13. increase creativity without adding clutter
-14. keep section spacing generous, even, and clean
-15. remove AI slop
-16. deeply analyze the generated image(s)
-17. implement the frontend to match the generated design as closely as reasonably possible
+3. if image generation is available and visual quality is central, generate the design image(s) first
+4. inside Codex, prefer one large image per section
+5. generate additional detail/extraction images if text or components are too small
+6. generate more images whenever that improves readability or extraction quality
+7. do not be lazy with image count
+8. choose a strong visual combination
+9. choose 4 signature components
+10. choose 2 motion-implied cues
+11. enforce hero cleanliness and short hero line count
+12. enforce strong image usage where appropriate
+13. keep spacing generous, even, and analyzable
+14. deeply and cleanly analyze all generated images
+15. extract text, typography, spacing, buttons, colors, components, and layout logic
+16. implement the website to match the generated references as closely as reasonably possible
+17. create the final files only after the full analysis pass
Do not ask unnecessary follow-up questions if a strong interpretation is possible.
-Do not start with freeform coding when the visual design problem should clearly be solved with image generation first.
+Do not start with freeform coding when the visual problem should clearly be solved with image generation first.
+Do not compress many sections into one unreadable image in Codex.
---
-## 29. EXAMPLE INTERPRETATIONS
+## 32. EXAMPLE INTERPRETATIONS
### Example 1
User:
-“make a hero section for an AI startup”
+“make me one hero section for an AI startup”
Interpretation:
-- first generate 1 hero reference image yourself
-- deeply analyze the image
-- theme likely Deep Dark or Bold Studio Solid
-- hero architecture likely Asymmetric Split or Inline Typography Behemoth
-- concise statement headline
-- clear CTA
-- premium product visual
-- no cliché dashboard spam
-- only then implement the hero
+- generate 1 hero image
+- if needed, generate 1 closer extraction image for text/buttons
+- analyze headline, subheadline, CTA, spacing, colors, hero media
+- then implement the hero
### Example 2
User:
-“design 8 sections for a fintech website”
+“design me an 8-section landing page”
Interpretation:
-- first generate 2 tall vertical reference images yourself
-- deeply analyze both images
-- Swiss or modular structure
-- strong trust and clarity
-- controlled palette
-- high implementation clarity
-- multiple internal website image moments where appropriate
-- then implement the site from those references
+- generate 8 separate section images in Codex
+- one per section
+- generate extra detail images where necessary
+- deeply analyze all 8 sections
+- extract text, typography, spacing, buttons, colors, cards, structure
+- then implement the full site from those references
### Example 3
User:
-“creative agency landing page, 12 sections”
+“make a premium creative agency website with 4 sections”
Interpretation:
-- first generate 3 tall vertical reference images yourself
-- deeply analyze all images
-- editorial or poster-like direction
-- stronger typography
-- more asymmetry
-- still readable and clearly codeable
-- multiple internal website image moments where appropriate
-- then implement the site from those references
+- generate 4 separate section images in Codex
+- keep the hero very clean
+- ensure text remains readable
+- deeply analyze each section
+- then implement the site from those 4 references
---
-## 30. FINAL GOAL
+## 33. FINAL GOAL
-Generate frontend reference images that feel:
-- artistic
+Generate website reference images that feel:
- premium
+- art-directed
- clear
- structured
-- image-led
-- breathable
+- readable
+- analyzable
- memorable
- anti-generic
- implementation-friendly
-For visual frontend work, the skill must first generate the image(s) itself, then deeply analyze those generated image(s), then use them as the primary visual source, then build the frontend to match them closely.
+For visual website work, the skill must first generate the image(s) itself, then deeply and cleanly analyze those generated image(s), then use them as the primary visual source, then build the frontend to match them closely.
-The hero should feel especially clean, focused, and premium, with a short headline that does not break into too many lines.
+Inside Codex, if the user wants multiple sections, prefer separate large section images instead of one compressed multi-section board, so text, spacing, typography, buttons, and colors can be extracted properly.
-If the website benefits from multiple images inside the design itself, the skill should generate and use multiple purposeful image moments across the site, not just a single isolated visual.
+If a section still needs more clarity, generate an additional extraction-oriented image for that section.
-Images inside the design should usually live in clear, controlled, repeatable frames so the result is both visually strong and realistically implementable.
+If more images would improve quality, generate more images.
+Do not be lazy with image count.
The result should be:
-- strong as an image
+- strong as section images
- strong as a design system
+- strong under deep analysis
- and strong as implemented frontend
-The final outcome should look like a top-tier website concept translated faithfully into real code, not a dense, repetitive AI layout and not a generic coded reinterpretation.
+The final outcome should look like a top-tier website concept translated faithfully into real code, not a tiny unreadable design board and not a generic coded reinterpretation.