taste:
id: neon-canopy
name: Neon Canopy
summary: >-
A light, comfortable corporate UI combining professional structure with vivid, high-energy
accents.
app_type: WEB_APP
project_types:
- saas
styles:
- corporate
- bold
industry: software
aesthetics:
- corporate
- bold
tags:
- corporate
- bold
theme:
default_mode: LIGHT_MODE
palette_note: >-
Only the 500 anchor is provided per palette; the full 17-step ramp (100-900) is derived from
it by the system's heuristic shade tool.
palettes:
neutral:
'500': '#808080'
description: Balanced, neutral grey ramp anchored on the core secondary text value.
brand:
'500': '#00718F'
description: Deep, professional teal serving as the primary brand identifier.
danger:
'500': '#D9383A'
warning:
'500': '#F59E0B'
success:
'500': '#62D84E'
info:
'500': '#00718F'
accent:
'500': '#62D84E'
colors:
background:
light: '#FFFFFF'
dark: neutral/900
foreground:
light: '#0A0A0A'
dark: neutral/100
card:
light: '#FFFFFF'
dark: neutral/800
card-foreground:
light: neutral/900
dark: neutral/100
popover:
light: '#FFFFFF'
dark: neutral/800
popover-foreground:
light: neutral/900
dark: neutral/100
primary:
light: accent/500
dark: accent/500
primary-foreground:
light: neutral/900
dark: neutral/900
secondary:
light: neutral/100
dark: neutral/800
secondary-foreground:
light: neutral/900
dark: neutral/100
muted:
light: neutral/100
dark: neutral/800
muted-foreground:
light: neutral/700
dark: neutral/400
accent:
light: brand/100
dark: brand/800
accent-foreground:
light: brand/700
dark: brand/300
destructive:
light: danger/600
dark: danger/600
destructive-foreground:
light: neutral/100
dark: neutral/100
border:
light: neutral/200
dark: neutral/700
input:
light: neutral/200
dark: neutral/700
ring:
light: brand/500
dark: brand/500
chart-1:
light: brand/500
dark: brand/400
chart-2:
light: accent/500
dark: accent/400
chart-3:
light: brand/700
dark: brand/300
chart-4:
light: neutral/500
dark: neutral/400
chart-5:
light: danger/500
dark: danger/400
sidebar:
light: neutral/100
dark: neutral/800
sidebar-foreground:
light: neutral/900
dark: neutral/100
sidebar-primary:
light: brand/600
dark: brand/500
sidebar-primary-foreground:
light: neutral/100
dark: neutral/900
sidebar-accent:
light: neutral/200
dark: neutral/700
sidebar-accent-foreground:
light: neutral/900
dark: neutral/100
sidebar-border:
light: neutral/200
dark: neutral/700
sidebar-ring:
light: brand/500
dark: brand/500
radius:
base:
value: 0.625rem
description: Base radius allowing md to render at exactly 8px.
shadows:
xs:
value: 0 1px 2px rgba(0,0,0,0.05)
sm:
value: 0px 0px 0px 1px rgb(132, 132, 132)
md:
value: 0 4px 6px -1px rgba(0,0,0,0.08), 0 2px 4px -1px rgba(0,0,0,0.04)
lg:
value: 0 10px 15px -3px rgba(0,0,0,0.08), 0 4px 6px -2px rgba(0,0,0,0.04)
xl:
value: 0 20px 25px -5px rgba(0,0,0,0.08), 0 10px 10px -5px rgba(0,0,0,0.02)
gradients:
brand_wash:
value: 'linear-gradient(135deg, #00718F 0%, #62D84E 100%)'
fonts:
sans:
family: Source Serif 4
description: Clean modern serif for legible body and running text.
display:
family: Inter
description: High-contrast headings and primary titles.
mono:
family: JetBrains Mono
description: Precise monospace for tabular data and system metrics.
typography:
hero:
font: display
size_px: 36
line_height_px: 42
weight: 700
letter_spacing_em: 0
transform: none
title:
font: display
size_px: 24
line_height_px: 26
weight: 700
letter_spacing_em: 0
transform: none
heading:
font: display
size_px: 22
line_height_px: 24
weight: 700
letter_spacing_em: -0.015
transform: none
body:
font: sans
size_px: 14
line_height_px: 21
weight: 400
letter_spacing_em: -0.015
transform: none
caption:
font: sans
size_px: 12
line_height_px: 16
weight: 400
letter_spacing_em: 0
transform: none
label:
font: sans
size_px: 16
line_height_px: 24
weight: 700
letter_spacing_em: 0
transform: none
overline:
font: sans
size_px: 12
line_height_px: 16
weight: 600
letter_spacing_em: 0.08
transform: uppercase
style_guidelines:
visual_direction:
title: Visual Direction
recommendations:
- >-
Combine structured corporate layout structures with high-energy neon green interactive
elements to drive workflow engagement.
- Establish clean boundaries with subtle keyline borders instead of heavy color blocks.
hierarchy:
title: Hierarchy
recommendations:
- >-
Position critical status indicators in high-contrast neon green to draw immediate user
attention.
- Use prominent bold labels to clearly partition deep data arrays.
components:
title: Components
recommendations:
- >-
Render primary action buttons with a fully rounded pill format for a soft yet actionable
feel.
- >-
Define text inputs with crisp thin borders and explicit focus rings for clear visual state
changes.
typography:
title: Typography
recommendations:
- >-
Use monospace fonts exclusively for metrics and tabular digits to align multi-column data
neatly.
- >-
Apply refined line heights on Inter labels to ensure maximum scanability in tight data
lists.
color_and_effects:
title: Color & Effects
recommendations:
- >-
Incorporate low-opacity grey keyline shadows to lift active modules without cluttering the
screen.
- Restrict neon green accents to positive states and CTAs to avoid sensory fatigue.
quality_bar:
title: Quality Bar
checks:
- id: contrast-compliance
label: Contrast Compliance
recommendation: Ensure high-contrast text ratios on both light and dark backgrounds.
- id: pill-button-geometry
label: Pill Button Geometry
recommendation: >-
Verify that primary buttons maintain their exact 500px border radius and 36px height
profile.
- id: thin-border-restraint
label: Thin Border Restraint
recommendation: Confirm that structural dividers and borders use the precise 1px thin specification.
- id: status-color-discipline
label: Status Color Discipline
recommendation: >-
Check that the vivid neon green is reserved exclusively for primary actions and positive
status signals.
active_remix:
mode: light
brand: '#00718F'
display_font: Inter
shape: system
depth: system
spacing: system
spacing_value: null
craft: >
# Craft (universal core + conditional craft)
How to apply this design system well. These rules contain no brand look of their own — all
per-system character comes from the tokens and taste notes above; this section only governs
how they are composed. **Precedence:** the design system above is the authority on how things
look — where its own notes conflict with a rule here, the design system wins. And the user's
request is the authority on what the screen IS — notes above that describe the source
product's screens (workspaces, dashboards, panels) are its aesthetic heritage, not an
instruction to build that kind of screen.
## Universal — applies to every screen (screen-agnostic craft)
- **Surface definition.** Every container is visually separable from what it sits on — at least
one
honest edge cue: a hairline border, a ≥4% tonal step from its parent, or a real shadow. Never a card
whose fill matches its section with no border; never nested surfaces that dissolve together.
- **Accent discipline.** The brand/primary color is a scalpel, not paint: spend it on the primary
action, the active/selected/focused state, and at most **one** brand or data highlight per screen.
Everything else rides neutral background / card / muted / border tokens. A screen flooded with brand
color reads unfinished, not bold.
- **Restraint ledger.** Beauty is also what you don't do: at most one glow and two gradient
directions
screen-wide; decoration only where content doesn't reach; no ornament between a heading and its own
action. Every decorative element must answer "what does this make clearer or more felt?" — if the
answer is "nothing," remove it.
- **Type with intent.** The measured faces/scale are fixed; character comes from *usage*, and the
move
must fit the surface — a marketing page earns a dramatic display move; a working screen earns a
crisp, tight, legible hierarchy at UI scale (display-hero type on a dense tool is a smell). Chrome
and wayfinding are never display type; data numerals are tabular (mono or sans), never the
decorative face. Headings stay roman — italics live as emphasis inside running text, not as
display styling (unless the system's own type says otherwise).
- **Anti-default.** If the screen could pass for a generic template with the colors swapped, it is
not
done. Make the brand unmistakable through the accent's *use*, the type, the radius + density, and
**one** signature detail — never by importing another surface's clichés.
- **Honest content.** Never invent proof — no made-up adoption counts, growth percentages,
testimonials, client logos, or awards. Use the user's real content, a neutral placeholder, or
leave the element out and let the layout carry it. Never hand-draw fake browser bars, phone
frames, or editor chrome around content — show the content itself, or nothing.
- **Interaction integrity.** Buttons, links, tabs, and nav labels never wrap to two lines; display
headlines wrap cleanly, never clipping mid-word; nothing overflows horizontally at any width;
keyboard focus gets an instant, clearly visible ring.
- **Token fidelity.** Every design value comes from a token: colors, radii, shadows, and fonts
from
the system's variables — never a literal hex, a hand-picked shadow, or a substitute font. For a
translucent or composited value (a scrim, a glow, a hairline over a fill), derive it from a token
(an opacity modifier or color-mix), never a literal rgba. If the system specifies square corners and
a hard shadow, the screen shows square corners and that hard shadow — not a rounded, soft substitute.
## Conditional — apply ONLY the layer that matches the screen the user asked for
**First name the screen honestly from the user's prompt.** Then apply the matching guidance. Do
not
cross layers, and **do not add elements from a layer the screen doesn't call for** — a screen that
is
not a data view must not sprout KPI tiles, charts, filter bars, or data tables to satisfy a
template.
- **If it's a data / dashboard / admin / table view:** density done well (comfortable rows, tight
control clusters, one spacing rhythm); a populated working state (real rows/cards, not empty feature
boxes); tables with aligned tabular numerals, status as badges, row hover, one visible selected row,
and control states that agree with the data shown. KPI tiles, *if the screen has them*, are
value + label + delta. **At most one** chart, of a real metric for this domain, token-colored and
axis-labeled — never a decorative sine wave or filler sparkline. Exactly one unambiguous primary
action.
- **If it's a focused task / tool / player / capture / monitor / form / wizard (not a data
view):**
the screen's real job dominates the frame; chrome recedes. Honor the screen's own nature — a player
looks like a player, a monitor like a monitor, a form like a form — with the design system's color,
type, radius, and depth applied to *those* elements. **No dashboard furniture**: no KPI tiles, no
charts, no data tables, no filter chrome unless the task itself is about that data. Real-time or
safety-critical readouts get calm, unambiguous, high-legibility treatment over decoration.
- **If it's a marketing / landing surface:** editorial art direction belongs here — section rhythm
(modulate surface temperature, density, and scale; one oversized moment; at least one full-bleed
band) and considered visual treatments. Never put this on a working app screen.
- **Mobile:** follow the platform's native idioms for the screen's type (e.g. an app screen:
compact
top bar, one focused column, a bottom tab bar, ≥44px targets, safe areas) — the same conditional
rules above still decide what content belongs.
## Imagery (universal)
- **Imagery is content, not decoration** on working screens: images are data (covers, products,
avatars, places) in purposeful containers, one consistent treatment across siblings — never a lone
photo floating in a box, never marketing's decorative fades on a work screen. When a moment needs
atmosphere, build it from the token system (tinted panels, token gradients, geometry).
