F-Pattern Layout

STYLEKIT_STYLE_REFERENCE
style_name: F-Pattern Layout
style_slug: f-pattern-layout
style_source: /styles/f-pattern-layout

# Hard Prompt

## When To Use
Use this when you want AI to generate code with strict style consistency. It is the safest default for production UI.

## How To Use
- Copy the full prompt into ChatGPT, Claude, Cursor, or another coding assistant.
- Append the concrete product/page requirement after the prompt.
- After generation, check the forbidden rules and interaction states before accepting the output.

Strictly follow the style rules below and maintain consistency. No style drift allowed.

## Requirements

- Prioritize style consistency first, then creative extension.
- When conflicts arise, treat prohibitions as the highest priority.
- Self-check before output: verify colors, typography, spacing, and interactions still match this style.

## Style Rules

You are an F-Pattern Layout expert. All generated code must strictly follow these constraints:

## Layout Rules

- Place the most important information at the top of the page (logo, navigation, featured content)
- Place secondary information on the second row (categories, search)
- Place main content area on the left (article list)
- Place auxiliary content on the right (sidebar)
- All text left-aligned text-left

## Content Hierarchy

First layer (full-width top):
- Navigation bar
- Featured article/headline

Second layer (secondary horizontal area):
- Category tags
- Search bar

Third layer (left vertical list):
- Article list
- Content cards with thumbnails

Auxiliary area (right side):
- Trending recommendations
- Tag cloud
- Ad space

## Responsive

Desktop: Left main content + right sidebar
Tablet: Full-width main content + collapsed sidebar
Mobile: Single column stacked

## Self-Check

1. Most important content at top and top-left
2. Clear heading hierarchy
3. Text left-aligned
4. Content quickly scannable
5. Responsive adaptation complete

## Animation & Interaction Rules

- Eye-Tracking Guides: List item hover allows main title to slightly shift right (e.g., `translate-x-1`) or underline to appear, helping quickly lock on during scanning phase.
- Fast Feedback: News-type interactions recommend `duration-150` to `duration-200`, avoiding lengthy transitions that interrupt reading.
- Contrast Pop: Current hover item can be briefly separated from the information flow through slight shadow or border contrast enhancement.
- Image Focus: Thumbnail hover can increase contrast or brightness as clickable feedback, but the magnitude must be restrained.

---

# F-Pattern Layout Design System

> An F-pattern scanning layout based on eye-tracking research, where the user's gaze starts from the top-left, scans horizontally across the top, then moves downward, ideal for content-heavy pages, blog posts, and news listings.

## Design Philosophy

F-Pattern Layout is based on eye-tracking research by the Nielsen Norman Group, where users browse web pages with their gaze moving in an F-shape: first scanning horizontally across the top content, then moving down for a second (shorter) horizontal scan, and finally browsing vertically down the left side.

Core principles:
- Content priority: Most important content placed at the top and left
- Visual guidance: Guiding user reading path through hierarchy and weight
- Information density: Efficient arrangement for text-heavy content
- Scannability: Headlines, summaries, and body text form clear hierarchy

---

## Token Dictionary (exact class mapping)

### Border
```
Width: border
Color: border-gray-200
Radius: rounded-lg
```

### Shadow
```
sm: shadow-sm
md: shadow-sm
lg: shadow-md
hover: hover:shadow-md
focus: focus:shadow-sm
```

### Interaction
```
Hover translate: (none)
Hover scale: (none)
Hover opacity: hover:opacity-90
Transition: transition-colors duration-200
Active: active:scale-95
```

### Typefaces
```
Heading: font-semibold tracking-tight
Body: font-sans
Mono: font-mono
```

### Type scale
```
Hero: text-3xl md:text-4xl
H1: text-2xl md:text-3xl
H2: text-xl md:text-2xl
H3: text-lg md:text-xl
Body: text-sm md:text-base
Small: text-xs
```

### Spacing
```
Section: py-6 md:py-8 lg:py-12
Container: px-4 md:px-6
Card: p-4 md:p-6
Gap sm: gap-3 md:gap-4
Gap md: gap-4 md:gap-6
Gap lg: gap-6 md:gap-8
```

### Color roles
```
Background primary: bg-[#f8f9fa]
Background secondary: bg-white
Background accent: bg-[#e63946], bg-[#457b9d], bg-[#2a9d8f], bg-[#e9c46a]
Text primary: text-[#1a1a2e]
Text secondary: text-gray-600
Text muted: text-gray-400
Button primary: bg-[#e63946] text-white
Button secondary: bg-gray-100 text-gray-700
```

---

## [FORBIDDEN]

These classes are banned in this style. Check for them before returning code:

### Banned classes
- `text-center`
- `rounded-none`
- `rounded-2xl`
- `rounded-3xl`
- `shadow-2xl`
- `font-black`

### Banned patterns
- matches `^rounded-(?:none|2xl|3xl)`
- matches `^shadow-2xl`

### Why they are banned
- `text-center`: F-Pattern Layout uses left-aligned text to follow natural scanning patterns
- `rounded-none`: F-Pattern Layout uses moderate rounding for professional appearance
- `shadow-2xl`: F-Pattern Layout uses subtle shadows for clean readability

> WARNING: if your code contains any of the above, replace it before shipping.

---

## [REQUIRED]

### Every button must include
```
rounded-lg
font-medium
transition-colors
```

### Every card must include
```
bg-white
rounded-lg
shadow-sm
text-left
```

### Every input must include
```
bg-gray-50
border border-gray-200
rounded-lg
focus:outline-none
focus:ring-2 focus:ring-[#457b9d]/20 focus:border-[#457b9d]
transition-all
```

---

## [COMPARE] F-Pattern Layout wrong vs right

The wrong examples below stand for generic library defaults that were never adapted to this style. Do not read them as visual suggestions.

### Button

[WRONG] **Wrong** (generic component library default, do not copy):
```html
<button class="{GENERIC_LIBRARY_BUTTON_DEFAULT}">
  Click me
</button>
```

[CORRECT] **Right** (uses this style's tokens):
```html
<button class="rounded-lg font-medium transition-colors bg-[#e63946] text-white">
  Click me
</button>
```

### Card

[WRONG] **Wrong** (generic card, not adapted to this style):
```html
<div class="{GENERIC_LIBRARY_CARD_DEFAULT}">
  <h3>{TITLE}</h3>
</div>
```

[CORRECT] **Right** (uses this style's card tokens):
```html
<div class="bg-white rounded-lg shadow-sm text-left p-4 md:p-6">
  <h3 class="font-semibold tracking-tight text-lg md:text-xl">{TITLE}</h3>
</div>
```

### Input

[WRONG] **Wrong** (generic input, not adapted to this style):
```html
<input class="{GENERIC_LIBRARY_INPUT_DEFAULT}" />
```

[CORRECT] **Right** (uses this style's input tokens):
```html
<input class="bg-gray-50 border border-gray-200 rounded-lg focus:outline-none focus:ring-2 focus:ring-[#457b9d]/20 focus:border-[#457b9d] transition-all" placeholder="{PLACEHOLDER}" />
```

---

## [TEMPLATES] F-Pattern Layout page skeletons

These skeletons use this style's tokens only. Replace `{PLACEHOLDER}` values, but keep every token in place:

### Navigation
```html
<nav class="bg-[#f8f9fa] text-[#1a1a2e] border border-gray-200 px-4 md:px-6">
  <div class="flex items-center justify-between max-w-6xl mx-auto gap-4 md:gap-6">
    <a href="/" class="font-semibold tracking-tight text-lg md:text-xl">
      {LOGO_TEXT}
    </a>
    <div class="flex gap-4 md:gap-6 font-sans text-xs">
      {NAV_LINKS}
    </div>
  </div>
</nav>
```

### Hero section
```html
<section class="bg-[#e63946] text-[#1a1a2e] py-6 md:py-8 lg:py-12 px-4 md:px-6">
  <div class="max-w-4xl mx-auto">
    <h1 class="font-semibold tracking-tight text-3xl md:text-4xl">
      {HEADLINE}
    </h1>
    <p class="font-sans text-sm md:text-base max-w-xl">
      {SUBHEADLINE}
    </p>
    <button class="rounded-lg font-medium transition-colors bg-[#e63946] text-white">
      {CTA_TEXT}
    </button>
  </div>
</section>
```

### Card grid
```html
<section class="bg-[#f8f9fa] text-[#1a1a2e] py-6 md:py-8 lg:py-12 px-4 md:px-6">
  <div class="max-w-6xl mx-auto">
    <h2 class="font-semibold tracking-tight text-xl md:text-2xl">{SECTION_TITLE}</h2>
    <div class="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-4 md:gap-6">
      <!-- Card template - repeat for each card -->
      <div class="bg-white rounded-lg shadow-sm text-left p-4 md:p-6">
        <h3 class="font-semibold tracking-tight text-lg md:text-xl">{CARD_TITLE}</h3>
        <p class="font-sans text-sm md:text-base text-gray-400">{CARD_DESCRIPTION}</p>
      </div>
    </div>
  </div>
</section>
```

### Form input
```html
<input class="bg-gray-50 border border-gray-200 rounded-lg focus:outline-none focus:ring-2 focus:ring-[#457b9d]/20 focus:border-[#457b9d] transition-all" placeholder="{PLACEHOLDER}" />
```

### Footer
```html
<footer class="bg-white text-gray-600 py-6 md:py-8 lg:py-12 px-4 md:px-6">
  <div class="max-w-6xl mx-auto">
    <div class="grid grid-cols-1 md:grid-cols-3 gap-6 md:gap-8">
      <div>
        <span class="font-semibold tracking-tight text-lg md:text-xl">{LOGO_TEXT}</span>
        <p class="font-sans text-xs">{TAGLINE}</p>
      </div>
      <div>
        <h4 class="font-semibold tracking-tight text-lg md:text-xl">{COLUMN_TITLE}</h4>
        <ul class="font-sans text-xs">
          {FOOTER_LINKS}
        </ul>
      </div>
    </div>
  </div>
</footer>
```

---

## [CHECKLIST] F-Pattern Layout post-generation self check

**Before returning code, verify every token and rule below. Fix any violation before delivering:**

### Token check
- [ ] Button includes: `rounded-lg font-medium transition-colors`
- [ ] Card includes: `bg-white rounded-lg shadow-sm text-left`
- [ ] Input includes: `bg-gray-50 border border-gray-200 rounded-lg focus:outline-none focus:ring-2 focus:ring-[#457b9d]/20 focus:border-[#457b9d] transition-all`

### Forbidden check
- [ ] Not using `text-center`
- [ ] Not using `rounded-none`
- [ ] Not using `rounded-2xl`
- [ ] Not using `rounded-3xl`
- [ ] Not using `shadow-2xl`
- [ ] Not using `font-black`

### Style rule check
- [ ] Place the most important content at the top of the page (first horizontal line)
- [ ] Place navigation or key information on the left side (vertical line)
- [ ] Use clear heading hierarchy h1 > h2 > h3
- [ ] Use lists and sections to increase scannability
- [ ] Maintain left alignment text-left to match reading habits

### Style drift check
- [ ] Does not violate: Do NOT place important content in the bottom-right corner
- [ ] Does not violate: Do NOT center-align large blocks of text
- [ ] Does not violate: Do NOT ignore content priority ordering
- [ ] Does not violate: Do NOT use excessively long unsegmented text
- [ ] Does not violate: Do NOT leave too much whitespace on the left side

### Delivery check
- [ ] Responsive layout holds on phone, tablet and desktop with no horizontal overflow
- [ ] Every interactive element has a visible focus state, an accessible name and a reduced-motion path
- [ ] Text contrast meets WCAG AA and colour alone never carries state
- [ ] The result is still recognizable at a glance as F-Pattern Layout

## Absolute Bans (Match and Refuse)

If any of the following patterns appear, it is a style violation — rewrite without exception.

- place important content in the bottom-right corner
- center-align large blocks of text
- ignore content priority ordering
- use excessively long unsegmented text
- leave too much whitespace on the left side

## Self-Check (Verify Before Shipping)

If any item fails, the style has drifted — fix before shipping.

- [ ] No purple-to-blue gradients
- [ ] No overused fonts (Inter, Roboto, Geist, Fraunces, Plus Jakarta Sans)
- [ ] No nested cards (cards inside cards)
- [ ] No gray text on colored backgrounds
- [ ] Body text contrast meets WCAG AA (>= 4.5:1)
- [ ] No bounce or elastic easing curves
- [ ] Animations have a prefers-reduced-motion fallback
- [ ] Body text line length capped at 65-75 characters
- [ ] No side-stripe accent borders (border-left/right > 1px)
- [ ] No gradient text (background-clip: text)
- [ ] No glassmorphism used as the default surface treatment
- [ ] No tiny uppercase tracked eyebrow labels above every section heading
- [ ] do NOT place important content in the bottom-right corner
- [ ] do NOT center-align large blocks of text
- [ ] do NOT ignore content priority ordering
- [ ] do NOT use excessively long unsegmented text
- [ ] do NOT leave too much whitespace on the left side