Blueprint

STYLEKIT_STYLE_REFERENCE
style_name: Blueprint
style_slug: blueprint
style_source: /styles/blueprint

# 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

STYLE: Blueprint
TYPE: Engineering technical drawing interface

MUST USE:
- Blueprint blue background: bg-[#1e3a5f]
- White lines and text: text-white, border-white/30
- Monospace font: font-mono for all text
- uppercase tracking-widest for labels
- Grid background pattern for coordinates
- Orange annotations: text-[#ff6b35] for highlights
- Light blue secondary: text-[#a0c4e8]
- Corner markers on cards (L-shaped borders)
- Dashed lines for auxiliary elements: border-dashed

MUST AVOID:
- Warm-toned backgrounds
- Rounded/soft design elements
- Gradient fills
- Glow or neon effects
- Serif or handwritten fonts
- Large colored blocks
- Large border-radius (rounded-2xl+)

COLOR RULES:
- White line: #ffffff (primary elements)
- Blueprint blue: #1e3a5f (background)
- Light blue: #4a90d9, #a0c4e8 (secondary elements)
- Annotation orange: #ff6b35 (highlights, callouts)

SPECIAL EFFECTS:
- Grid background pattern (20px spacing)
- Corner bracket markers on containers
- Dimension lines with end markers
- Coordinate labels as decorative elements

Animation & Interaction Rules:
- CAD Precision: Interaction effects must be crisp and precise, prefer duration-100 (adjustable within 75-150ms range), avoiding sluggish ease-in-out.
- Crosshair Reveals: On hovering interactive elements, use before/after or corner markers to reveal crosshair and alignment hints.
- Blueprint Highlight: Default blue-white palette; active or confirm states can briefly light up engineering orange #ff6b35, but it must not dominate the main visual for long.
- Grid Interaction: Container hover can slightly increase grid line visibility (white lines to light blue lines), serving only as measurement feedback, not emotional animation.

---

# Blueprint Design System

> Engineering blueprint and technical drawing style with white lines on blue, grid coordinates, annotation lines, and dimension markers. Ideal for architecture, engineering, tech, and education.

## Design Philosophy

Blueprint draws design inspiration from traditional cyanotype blueprint printing and modern engineering drafting. White lines on a blue background are its most iconic visual feature, while grid systems, annotation lines, and dimension markers give the interface a precise, professional, and trustworthy character.

Core concepts:
- Blue background with white lines: The classic blueprint color scheme -- white lines and text on a deep blue background
- Grid system: Background grids suggest a precise coordinate system and measurement units
- Annotation language: Annotation lines, dimension markers, and coordinate labels serve as both decorative and navigational elements
- Technical font: Monospace fonts reinforce the precision feel of engineering drafting

Blueprint style naturally conveys "carefully planned" and "professionally reliable" messaging. It suits any scenario that needs to demonstrate technical depth and engineering thinking. UI elements should look as if drawn on drafting paper -- buttons like legend buttons, cards like detail zoom boxes on drawings, input fields like annotation columns.

Suitable for: architecture firms, engineering consultancies, tech product launch pages, educational institutions, and technical documentation websites.

---

## Token Dictionary (exact class mapping)

### Border
```
Width: border
Color: border-white/30
Radius: rounded-none
```

### Shadow
```
sm: shadow-none
md: shadow-none
lg: shadow-[0_2px_10px_rgba(0,0,0,0.3)]
hover: hover:bg-white/5
focus: focus:border-[#4a90d9]
```

### Interaction
```
Hover translate: (none)
Hover scale: hover:bg-white/10
Hover opacity: (none)
Transition: transition-all duration-200
Active: active:scale-95
```

### Typefaces
```
Heading: font-mono tracking-wider uppercase
Body: font-mono
Mono: font-mono
```

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

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

### Color roles
```
Background primary: bg-[#1e3a5f]
Background secondary: bg-[#1e3a5f]/60
Background accent: bg-white, bg-[#4a90d9], bg-[#ff6b35]
Text primary: text-white
Text secondary: text-[#a0c4e8]
Text muted: text-white/40
Button primary: bg-transparent text-white border border-white/60
Button secondary: bg-white text-[#1e3a5f]
```

---

## [FORBIDDEN]

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

### Banned classes
- `bg-white`
- `bg-gray-50`
- `bg-gray-100`
- `shadow-sm`
- `shadow-md`
- `shadow-lg`
- `rounded-xl`
- `rounded-2xl`
- `rounded-3xl`
- `rounded-full`
- `font-serif`
- `bg-gradient-`

### Banned patterns
- matches `^bg-(?:white|gray-[1-3]|slate-[1-3])`
- matches `^shadow-(?:sm|md|lg|xl|2xl)`
- matches `^rounded-(?:xl|2xl|3xl|full)`
- matches `^font-serif`
- matches `^bg-gradient-`

### Why they are banned
- `bg-white`: Blueprint uses deep blue backgrounds, not white
- `shadow-md`: Blueprint uses minimal shadows; rely on borders and lines
- `rounded-xl`: Blueprint uses sharp corners for technical precision
- `font-serif`: Blueprint uses monospace fonts for engineering feel
- `bg-gradient-`: Blueprint uses flat colors, not gradients

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

---

## [REQUIRED]

### Every button must include
```
px-6 py-3
font-mono
uppercase tracking-widest
text-sm
transition-all duration-200
```

### Every card must include
```
bg-[#1e3a5f]/60
border border-white/20
```

### Every input must include
```
bg-transparent
border border-white/30
text-white
font-mono
focus:border-[#4a90d9]
focus:outline-none
```

---

## [COMPARE] Blueprint 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="px-6 py-3 font-mono uppercase tracking-widest text-sm transition-all duration-200 bg-transparent text-white border border-white/60">
 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-[#1e3a5f]/60 border border-white/20 p-6">
 <h3 class="font-mono tracking-wider uppercase 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-transparent border border-white/30 text-white font-mono focus:border-[#4a90d9] focus:outline-none" placeholder="{PLACEHOLDER}" />
```

---

## [TEMPLATES] Blueprint page skeletons

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

### Navigation
```html
<nav class="bg-[#1e3a5f] text-white border border-white/30 px-4 md:px-8">
 <div class="flex items-center justify-between max-w-6xl mx-auto gap-6">
 <a href="/" class="font-mono tracking-wider uppercase text-lg md:text-xl">
 {LOGO_TEXT}
 </a>
 <div class="flex gap-6 font-mono text-xs">
 {NAV_LINKS}
 </div>
 </div>
</nav>
```

### Hero section
```html
<section class="bg-white text-white py-16 md:py-24 px-4 md:px-8">
 <div class="max-w-4xl mx-auto">
 <h1 class="font-mono tracking-wider uppercase text-3xl md:text-5xl lg:text-7xl">
 {HEADLINE}
 </h1>
 <p class="font-mono text-sm md:text-base max-w-xl">
 {SUBHEADLINE}
 </p>
 <button class="px-6 py-3 font-mono uppercase tracking-widest text-sm transition-all duration-200 bg-transparent text-white border border-white/60">
 {CTA_TEXT}
 </button>
 </div>
</section>
```

### Card grid
```html
<section class="bg-[#1e3a5f] text-white py-16 md:py-24 px-4 md:px-8">
 <div class="max-w-6xl mx-auto">
 <h2 class="font-mono tracking-wider uppercase text-xl md:text-3xl">{SECTION_TITLE}</h2>
 <div class="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6">
 <!-- Card template - repeat for each card -->
 <div class="bg-[#1e3a5f]/60 border border-white/20 p-6">
 <h3 class="font-mono tracking-wider uppercase text-lg md:text-xl">{CARD_TITLE}</h3>
 <p class="font-mono text-sm md:text-base text-white/40">{CARD_DESCRIPTION}</p>
 </div>
 </div>
 </div>
</section>
```

### Form input
```html
<input class="bg-transparent border border-white/30 text-white font-mono focus:border-[#4a90d9] focus:outline-none" placeholder="{PLACEHOLDER}" />
```

### Footer
```html
<footer class="bg-[#1e3a5f]/60 text-[#a0c4e8] py-16 md:py-24 px-4 md:px-8">
 <div class="max-w-6xl mx-auto">
 <div class="grid grid-cols-1 md:grid-cols-3 gap-8">
 <div>
 <span class="font-mono tracking-wider uppercase text-lg md:text-xl">{LOGO_TEXT}</span>
 <p class="font-mono text-xs">{TAGLINE}</p>
 </div>
 <div>
 <h4 class="font-mono tracking-wider uppercase text-lg md:text-xl">{COLUMN_TITLE}</h4>
 <ul class="font-mono text-xs">
 {FOOTER_LINKS}
 </ul>
 </div>
 </div>
 </div>
</footer>
```

---

## [CHECKLIST] Blueprint post-generation self check

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

### Token check
- [ ] Button includes: `px-6 py-3 font-mono uppercase tracking-widest text-sm transition-all duration-200`
- [ ] Card includes: `bg-[#1e3a5f]/60 border border-white/20`
- [ ] Input includes: `bg-transparent border border-white/30 text-white font-mono focus:border-[#4a90d9] focus:outline-none`

### Forbidden check
- [ ] Not using `bg-white`
- [ ] Not using `bg-gray-50`
- [ ] Not using `bg-gray-100`
- [ ] Not using `shadow-sm`
- [ ] Not using `shadow-md`
- [ ] Not using `shadow-lg`
- [ ] Not using `rounded-xl`
- [ ] Not using `rounded-2xl`

### Style rule check
- [ ] Use blueprint blue bg-[#1e3a5f] for backgrounds paired with grid line background effects
- [ ] Use white text-white or light blue text-[#a0c4e8] for text and lines
- [ ] Use monospace font font-mono to enhance the technical drafting feel
- [ ] Use white/light blue thin line borders border border-white/30
- [ ] Use orange text-[#ff6b35] for annotation highlight markers

### Style drift check
- [ ] Does not violate: Do not use warm-toned backgrounds
- [ ] Does not violate: Do not use rounded, soft design elements
- [ ] Does not violate: Do not use gradient color fills (lines and fills should be solid colors)
- [ ] Does not violate: Do not use glow effects or neon shadows
- [ ] Does not violate: Do not use serif fonts or handwritten fonts

### 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 Blueprint

---

## [EXAMPLES] Example prompts

### 1. 

```
Create a technical architecture page using Blueprint style:
- Deep blue background with grid pattern
- System components as blueprint cards with corner markers
- Connection lines between components (dashed)
- Annotation callouts in orange
- All text in monospace uppercase
- Coordinate labels at corners for reference
```

## Absolute Bans (Match and Refuse)

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

- use warm-toned backgrounds
- use rounded, soft design elements
- use gradient color fills (lines and fills should be solid colors)
- use glow effects or neon shadows
- use serif fonts or handwritten fonts
- use large areas of colored blocks
- use elements with overly large rounded corners rounded-2xl rounded-3xl

## 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 use warm-toned backgrounds
- [ ] do not use rounded, soft design elements
- [ ] do not use gradient color fills (lines and fills should be solid colors)
- [ ] do not use glow effects or neon shadows
- [ ] do not use serif fonts or handwritten fonts