Guideline / Visual Design System

Visual UI System

The complete visible representation of AIPOCH components. Every rule is demonstrated strictly via live HTML components.

0. Global Rules

Mockups
  • Mockups must be present in every template that defines a device visual.
  • Mockups must keep the original aspect ratio at all times.
  • Mockups must never be stretched, squashed, or distorted.
Typography
  • Titles must use one emphasis only.
  • Emphasis must use Tinos Italic.
  • Approved brand accent colors may apply to the italic keyword only when the template defines that treatment.
Layout
  • Extra frames, nested outlines, and duplicate containers are not allowed.
  • Placeholder text and debug text must not appear in output.
  • Templates must use only the approved structure defined in the system.
Consistency
  • The left preview must match the right-side specification exactly.
  • Every rendered element must be defined by the written rule set.
  • Elements not defined in the specification must not appear in the preview.

2. Typography

H1 Hero
text-5xl lg:text-7xl font-normal tracking-tight Inter

Structured interfaces create research confidence.

H2 Section
text-4xl font-light tracking-tight Inter

Technical modules must feel calm, precise, and legible.

Panel Title
text-xl font-medium Inter

Technical Panel Title

Social Headline Accent
one italic keyword / titles only Tinos Italic

Portfolio Signals

Use italic for one keyword only inside website hero titles and social media headlines.

Italic emphasis must use Tinos Italic and must not rely on browser-generated italic.

Approved brand accent colors may apply to the italic keyword only when the template defines that treatment. Portfolio Signals, Accelerate Insight, and Product Focus follow the same rule.

Social Brand Marker
top-corner brand / handle Inter SemiBold
AIPOCH @AIPOCH

Use small uppercase Inter markers for social brand identifiers placed in the top corners of templates.

Brand markers must stay compact and secondary to the main headline. This style is for brand and handle metadata only.

Body Text
text-sm leading-[1.65] text-gray-600 Inter

Use muted body copy for helper text, operational notes, and panel descriptions. Keep sentences short, factual, and low-drama.

Caption / System Label
text-[10px] font-mono uppercase tracking-[0.18em] Roboto Mono
System Label / Ready
Inline Code
text-[10px] font-mono inline-flex border border-[#E7E5DE] bg-[#F7F7F4] Roboto Mono
Use inline code for flags and paths such as --preview /workspace/skills

3. Color System

Figma Color Scheme (Source of Truth)

This module is synced from AIPOCH UI Component Library → Foundations → Color Scheme. Each swatch keeps the Figma token name, step, and hex value for direct comparison.

Step Token HEX

Primary Scale (color/primary/*)

Primary / Highlight: Restrained warm yellow scale used for emphasis, guided attention, and a single focal CTA per view.

050
color/primary/050
#FFF9DE
100
color/primary/100
#FFF4B8
200
color/primary/200
#FFEC8C
300
color/primary/300
#FBDD67
400
color/primary/400
#F6CC46
500
color/primary/500
#EDB732
600
color/primary/600
#D08D23
700
color/primary/700
#A66B1C
800
color/primary/800
#7A4D16
900
color/primary/900
#52320F

Neutral Scale (color/neutral/*)

Neutral: Canvas, structure, reading, and border roles across the interface.

050
color/neutral/050
#FCFCFA
100
color/neutral/100
#F7F7F4
200
color/neutral/200
#E7E5DE
300
color/neutral/300
#D9D7D0
400
color/neutral/400
#B4B4AE
500
color/neutral/500
#8E8E87
600
color/neutral/600
#6B6B66
700
color/neutral/700
#4E4E49
800
color/neutral/800
#2A2A28
900
color/neutral/900
#111111

Semantic Success

Positive workflow outcomes, confirmation states, and safe operational feedback.

100 · color/semantic/success/100
#E0EBE7
300 · color/semantic/success/300
#9FBFB4
500 · color/semantic/success/500
#5A8876
700 · color/semantic/success/700
#3E6B5A
900 · color/semantic/success/900
#2C5348

Semantic Warning

Attention states, validation prompts, and controlled caution surfaces.

100 · color/semantic/warning/100
#F6EEDC
300 · color/semantic/warning/300
#D8B96D
500 · color/semantic/warning/500
#C18E2A
700 · color/semantic/warning/700
#8F6118
900 · color/semantic/warning/900
#5B3C0E

Semantic Error

Blocking failures, destructive states, and critical system feedback.

100 · color/semantic/error/100
#F5E3E1
300 · color/semantic/error/300
#D69A94
500 · color/semantic/error/500
#B85E57
700 · color/semantic/error/700
#8D4A44
900 · color/semantic/error/900
#603733

Single Tokens

500
color/accent/orange
#EA580C

Accent Orange: High-contrast brand callout used for approved keyword emphasis and standout CTA accents.

500
color/state/info
#4B6778

Info: Context, system guidance, research notes, and neutral status communication.

4. Icon System

Lucide Core

24x24 frame, 2px stroke, outline only.

5. Buttons & UI Components

Button Styles

Primary Ink
Secondary Outline
Split Directional

Utility Elements

Neutral Tag Active Tag System Label
Inline code tokens: --dry-run /workspace/config
Copy Action
Copied State

Interaction States & Motion

Hover
Accent the touched surface

Use highlight to indicate intent while preserving structure and text contrast.

Active / Focus
1px outline / 2px offset

Clarify borders and focus rings before adding heavier fills or shadows.

Copied / Success
Copied

Swap to a short confirmation label, then reset automatically after a brief delay.

Motion Timing
300ms direct response 1000ms ambient settle

Reserve slower motion for color settling and utility feedback, not for structural shifts.

6. Spacing & Grid Definition

Panel Padding
32px

Use `32px` as the default internal spacing for technical panels and divided modules.

Major Gap
Block A
Block B

Use `48px` between primary columns or major content groups inside one technical module.

Section Rhythm
24px
24px

Use `24px` to separate stacked content groups inside a single column.

Micro Spacing
12px
12px
Notes 4px

Use `12px` for compact stacks and `4px` for tightly related metadata or note lines.

12-Column Desktop Grid max-w-6xl

Indexed support rail / col-span-5

7. Social Media

Overview

Social media is a rule-based output system, not a single fixed template. Each asset must use approved brand elements, approved background language, and one clear layout logic.

System Rules

Layout Variation

Social graphics must use one approved layout variation per asset. Layout types must not be mixed.

Brand Presence

Every asset must demonstrate core brand elements and approved background usage.

Element Constraint

Use only elements already defined in the system, or reasonable combinations of those elements.

Visual Discipline

Do not introduce new visual elements or new gradients. Keep output aligned with the existing brand language.

Brand Elements

Social graphics must use the same elemental vocabulary already established in the system: circular marks, framed structure, line grids, and decisive highlight blocks.

Lens / Orbit

Use as focal anchors, cadence markers, or end points inside a composition.

Grid Origin
Grid origin source structure

Use this source structure to set grid origin, alignment logic, and framing boundaries across all background compositions.

Concentric Pattern
Node and ring array brand element

Use this concentric pattern as a core brand element to establish focal hierarchy, radial balance, and visual continuity across the system.

Background Styles
Light structural background
Dark radial background

Use the approved light and dark background systems as reusable structural modes inside social compositions.

Background

Allowed Structures

Build backgrounds from line grids, orbit rings, bracket corners, node fields, flat surfaces, and simple black or neutral planes.

Usage Rule

Backgrounds must support the main message and must not overpower it. Use opacity only within the approved palette. Decorative treatments outside the system are not allowed.

Hard Limits

Do not introduce new visual effects. No extra gradients unless already defined in the system. No blur, noise, glow, or atmospheric texture.

Light structural background
Dark radial background

AIPOCH Background Compositions

Collected from the Figma `Elements / AIPOCH Background Compositions` source. This preview includes all approved background directions inside the `Background` section and gives each one a direct SVG download.

12 downloadable PNG backgrounds

Layout Options

Use one layout logic per graphic. Multiple layout types must not appear in the same composition.

Hero

One dominant visual, minimal text, clear focal point.

single focus
Concentric pattern
Hero concentric pattern
One field. One signal.

Split

Separate message and visual structure.

dual rail
Text rail
Keep proof separate from message.

Let one side hold structure and the other hold content.

Approved split visual
approved visual

Frame

Structured margins and strong alignment.

margin-led
Grid origin Concentric pattern
Frame

Structure must carry the read.

Use approved elements only

Composition Rules

Focal Point

Every graphic must have one thing that reads first: a headline, a lens form, or one color block.

Alignment

Use visible left, center, or grid alignment. Avoid scattered or floating placements.

Negative Space

Leave quiet zones around the focal content so the composition feels deliberate and readable.

Hierarchy

Use scale and contrast before adding more parts. Structure must do more work than decoration.

Correction Logic

If Weak

Simplify. Remove secondary elements and strengthen one anchor.

If Crowded

Delete elements. Keep the strongest line, block, and message only.

If Empty

Add structure, not decoration. Use a frame, grid, ring, or color plane that already belongs to the system.

Content Examples

Use abstract content examples to show how approved elements combine inside real social outputs without introducing platform-specific styling.

Editorial Hero / 4:5
Concentric pattern
Signal core element

Evidence needs a clear signal.

One focus only
Structured Split / 1:1
Copy

Keep insight and structure distinct.

Approved structured split visual
approved visual
Framed Statement / 9:16
Grid origin Concentric pattern
Frame

Structure must carry the read.

Use approved elements only

Template System

Treat each template as a fixed system pattern. The previews below use approved brand elements and layout rules only; the notes define how to rebuild the same composition logic with new content.

3 reusable social templates
Template 1
Dark Background / Portfolio Intro

Use only for portfolio, category-intro, or opening social slides. Text leads; the device mockup supports.

no frame / background-driven
AIPOCH
@AIPOCH
Portfolio Signals
www.aipoch.com
Composition Structure

Use a pure black field with top-left brand, top-right handle, center-left headline, supporting URL below, and a device mockup anchored at the bottom.

Elements Breakdown

Use branding, handle, one-keyword italic headline with `#FBDD67`, supporting URL, laptop mockup, pure black background, and radial/grid overlays built from approved brand elements.

Layout Rules

Headline must be the primary read. The title block must stay left-weighted. The mockup must stay lower and wider than the text block. Support text must sit between headline and device.

Constraints
  • Background must be pure black.
  • Background pattern must render correctly with no artifacts or broken visuals.
  • Title must use one italic keyword only.
  • The italic keyword must use `#FBDD67`.
  • Random symbols and debug elements must not appear.
  • Mockup must not be distorted.
Template 2
Framed Device Showcase

Use only for headline-led product showcase slides. The headline pulls focus; the device sits inside one clear, single frame.

single hard frame
AIPOCH
@AIPOCH
Accelerate Insight
Composition Structure

Use a light field with top-corner brand markers, centered headline, framed device showcase in the center, and one restrained brand graphic behind.

Elements Breakdown

Use branding, handle, one-keyword italic headline where Insight uses `#EA580C`, laptop mockup, one hard frame boundary, and one approved grid/radial background element.

Layout Rules

Composition must stay vertically centered. The headline must stay above the mockup. A single, unbroken frame must wrap the device area.

Constraints
  • Mockup is required and must always be visible.
  • Only one frame is allowed. Duplicate and nested frames are not allowed.
  • Mockup must keep the original aspect ratio with no distortion.
  • Title must use one italic keyword only.
  • The italic keyword must use `#EA580C`.
  • Extra text and placeholder text must not appear.
Template 3
Soft UI / Product Promotion

Use only for softer, product-led promotion where the mockup sits inside a rounded container block and the CTA acts as the interaction layer.

soft container / no visible border
AIPOCH
@AIPOCH
Product  Focus
View Mockups
Composition Structure

Use a light neutral field with grid overlay, top-corner brand markers, left-aligned headline, large rounded mockup container, centered CTA below, and a yellow highlight with `#FBDD67` behind Focus only.

Elements Breakdown

Use branding, handle, one-keyword italic headline, product mockup inside a rounded container, CTA button, grid origin structure, approved radial background pattern, and one `#FBDD67` highlight block behind Focus.

Layout Rules

The headline must stay in the upper-left read zone. The mockup container must be the primary visual focus and must use the same scale and proportion logic as the Framed Device Showcase. The CTA must sit below as a separate interaction band.

Constraints
  • Mockup is required and must be the primary visual focus.
  • Mockup scale must match Framed Device Showcase ratio.
  • `#FBDD67` highlight applies only to the word Focus.
  • Yellow block must have no border radius.
  • Only one highlight element is allowed.
  • Extra text and placeholder content must not appear.

Copy Tone Application

Headline Tone

Run structured checks with clear visual hierarchy.

Calm & Factual

Unlock the most powerful workflow ever built!

Hyped & Desperate

Module Microcopy
Run Check View Details Copy Copied

Use short operational verbs and compact confirmations. The interface must sound exact, not promotional.

Preferred labels copy / copied / tip / ready

Use direct nouns and verbs: `Run`, `View`, `Copy`, `Ready`, `Unavailable`.

Prefer one sentence of helper text over multi-step persuasion.

Avoid playful verbs such as `Grab`, `Explore Now`, or `Magic` in technical UI.

Rule Summary

Keep it operational

Microcopy must support the action in front of the user and must not narrate the entire workflow.

Keep it short

Labels must stay at one to three words. Helper text must usually fit in one sentence.

Keep it factual

Success and warning states must read as factual system feedback rather than marketing language.