• Sidebars: normal (240-260px fixed width, solid background, simple border-right, no floating shells, no rounded outer corners)
• Headers: normal (simple text, no eyebrows, no uppercase labels, no gradient text, just h1/h2 with proper hierarchy)
• Sections: normal (standard padding 20-30px, no hero blocks inside dashboards, no decorative copy)
• Navigation: normal (simple links, subtle hover states, no transform animations, no badges unless functional)
• Buttons: normal (solid fills or simple borders, 8-10px radius max, no pill shapes, no gradient backgrounds)
• Cards: normal (simple containers, 8-12px radius max, subtle borders, no shadows over 8px blur, no floating effect)
• Forms: normal (standard inputs, clear labels above fields, no fancy floating labels, simple focus states)
• Inputs: normal (solid borders, simple focus ring, no animated underlines, no morphing shapes)
• Modals: normal (centered overlay, simple backdrop, no slide-in animations, straightforward close button)
• Dropdowns: normal (simple list, subtle shadow, no fancy animations, clear selected state)
• Tables: normal (clean rows, simple borders, subtle hover, no zebra stripes unless needed, left-aligned text)
• Lists: normal (simple items, consistent spacing, no decorative bullets, clear hierarchy)
• Tabs: normal (simple underline or border indicator, no pill backgrounds, no sliding animations)
• Badges: normal (small text, simple border or background, 6-8px radius, no glows, only when needed)
• Avatars: normal (simple circle or rounded square, no decorative borders, no status rings unless functional)
• Icons: normal (simple shapes, consistent size 16-20px, no decorative icon backgrounds, monochrome or subtle color)
• Typography: normal (system fonts or simple sans-serif, clear hierarchy, no mixed serif/sans combos, readable sizes 14-16px body)
• Spacing: normal (consistent scale 4/8/12/16/24/32px, no random gaps, no excessive padding)
• Information density: normal (one primary task or reading surface per screen, secondary context revealed progressively, no competing columns by default)
• Borders: normal (1px solid, subtle colors, no thick decorative borders, no gradient borders)
• Shadows: normal (subtle 0 2px 8px rgba(0,0,0,0.1) max, no dramatic drop shadows, no colored shadows)
• Transitions: normal (100-200ms ease, no bouncy animations, no transform effects, simple opacity/color changes)
• Layouts: normal (standard grid/flex, no creative asymmetry, predictable structure, clear content hierarchy, and a clear primary surface)
• Grids: normal (consistent columns, standard gaps, no creative overlaps, responsive breakpoints, and only use multi-column when the content benefits from side-by-side comparison)
• Flexbox: normal (simple alignment, standard gaps, no creative justify tricks)
• Containers: normal (max-width 1200-1400px, centered, standard padding, no creative widths)
• Wrappers: normal (simple containing divs, no decorative purposes, functional only)
• Panels: normal (simple background differentiation, subtle borders, no floating detached panels, no glass effects, and no always-open companion panels unless they are essential)
• Toolbars: normal (simple horizontal layout, standard height 48-56px, clear actions, no decorative elements)
• Footers: normal (simple layout, standard links, no decorative sections, minimal height)
• Breadcrumbs: normal (simple text with separators, no fancy styling, clear hierarchy)

• A screen should have one dominant surface. If the main job is filling a form, the form is the surface. If the main job is reading a chart, planner, gantt, map, canvas, or table, that surface gets the space.
• Do not place a secondary details column beside a planner, chart, or other dense visualization by default. Put details below, behind a drawer, in an inspector that opens on selection, or in a separate step.
• Multi-column layouts are acceptable for compact, related form inputs on wide screens. They are not the default for summaries, alerts, guidance, notes, calculators, charts, or selection details.
• If two areas both require reading, scrolling, and decision-making, they should usually not sit side by side on initial load.
• Summaries should be concise and adjacent to the action only when they reduce effort. If the summary repeats what the user can already infer from the main surface, move it lower or hide it until needed.
• Warnings, tips, and helper notes should not all be visible at once. Show the highest-priority guidance first and progressively reveal the rest.
• On desktop, extra width is not a reason to add another column. Empty space is better than a cluttered second rail.
• For planning and scheduling interfaces, default to one wide board or timeline with lightweight controls above it. Selection details should appear on demand, not occupy permanent width from first render.

• A landing page needs its sections. If hero needs full sections, if dashboard needs full sections with sidebar and everything else laid out properly. DO NOT invent a new layout.
• In your internal reasoning act as if you dont see this, list all the stuff you would do, AND DONT DO IT!
• Try to replicate figma/designer made components dont invent your own

• Everything you are used to doing and is a basic "YES" to you.
• No oversized rounded corners.
• No pill overload.
• No floating glassmorphism shells as the default visual language.
• No soft corporate gradients used to fake taste.
• No generic dark SaaS UI composition.
• No decorative sidebar blobs.
• No "control room" cosplay unless explicitly requested.
• No serif headline + system sans fallback combo as a shortcut to "premium."
• No

  Segoe UI

  ,

  Trebuchet MS

  ,

  Arial

  ,

  Inter

  ,

  Roboto

  , or safe default stacks unless the product already uses them.
• No sticky left rail unless the information architecture truly needs it.
• No metric-card grid as the first instinct.
• No fake charts that exist only to fill space.
• No two-column layout where both columns are dense and both demand attention on initial load.
• No right-side details rail beside charts, planners, or timelines unless the workflow genuinely requires simultaneous cross-reference.
• No summary column beside a form when the summary can sit above, below, or after submission.
• No using available desktop width as an excuse to keep helper text, alerts, notes, and controls all visible at once.
• No turning every operational screen into a board-plus-inspector split view.
• No random glows, blur haze, frosted panels, or conic-gradient donuts as decoration.
• No "hero section" inside an internal UI unless there is a real product reason.
• No alignment that creates dead space just to look expensive.
• No overpadded layouts.
• No mobile collapse that just stacks everything into one long beige sandwich.
• No ornamental labels like "live pulse", "night shift", "operator checklist" unless they come from the product voice.
• No generic startup copy.
• No style decisions made because they are easy to generate.
• No Headlines of any sort

<div class="headline">
  <small>Team Command</small>
  <h2>One place to track what matters today.</h2>
  <p>
    The layout stays strict and readable: live project health,
    team activity, and near-term priorities without the usual
    dashboard filler.
  </p>
</div>

• <small>

  headers are NOT allowed
• Big no to rounded

  span

  s
• Colors going towards blue -- NOPE, bad. Dark muted colors are best.
• Anything in the structure of this card is a BIG no.

<div class="team-note">
  <small>Focus</small>
  <strong>
    Keep updates brief, blockers visible, and next actions easy to spot.
  </strong>
</div>

• Border radii in the 20px to 32px range across everything ( uses 12px everywhere - too much)
• Repeating the same rounded rectangle on sidebar, cards, buttons, and panels
• Sidebar width around 280px with a brand block on top and nav links below (: 248px with brand block)
• Floating detached sidebar with rounded outer shell
• Canvas chart placed in a glass card with no product-specific reason
• Donut chart paired with hand-wavy percentages
• UI cards using glows instead of hierarchy
• Mixed alignment logic where some content hugs the left edge and some content floats in center-ish blocks
• Dense two-column application shells where the main work area and the supporting context panel both scroll and compete for attention
• Overuse of muted gray-blue text that weakens contrast and clarity
• "Premium dark mode" that really means blue-black gradients plus cyan accents ( has radial gradients in background)
• UI typography that feels like a template instead of a brand
• Eyebrow labels (: "MARCH SNAPSHOT" uppercase with letter-spacing)
• Hero sections inside dashboards ( has full hero-strip with decorative copy)
• Decorative copy like "Operational clarity without the clutter" as page headers
• Section notes and mini-notes everywhere explaining what the UI does
• Transform animations on hover (: translateX(2px) on nav links)
• Dramatic box shadows (: 0 24px 60px rgba(0,0,0,0.35))
• Status indicators with ::before pseudo-elements creating colored dots
• Muted labels with uppercase + letter-spacing ( overuses this pattern)
• Pipeline bars with gradient fills (: linear-gradient(90deg, var(--primary), #4fe0c0))
• KPI cards in a grid as the default dashboard layout ( has 3-column kpi-grid)
• Form plus estimate-summary side-by-side layouts where the summary is visible before the user has entered enough data to need it
• Gantt, planner, and chart screens with a permanent details column that steals width from the main visualization
• "Team focus" or "Recent activity" panels with decorative internal copy
• Tables with tag badges for every status ( overuses .tag class)
• Workspace blocks in sidebar with call-to-action buttons
• Brand marks with gradient backgrounds (: linear-gradient(135deg, #2a2a2a, #171717))
• Nav badges showing counts or "Live" status ( has nav-badge class)
• Quota/usage panels with progress bars ( has three quota sections)
• Footer lines with meta information (: "Northstar dashboard • dark mode • single-file HTML")
• Trend indicators with colored text (: trend-up, trend-flat classes)
• Rail panels on the right side with "Today" schedule ( has full right rail)
• Multiple nested panel types (panel, panel-2, rail-panel, table-panel)

• Colors should stay calm, not fight.
• You are bad at picking colors follow this priority order when selecting colors:

1. Highest priority: Use the existing colors from the user's project if they are provided (You can search for them by reading a few files).
2. If the project does not provide a palette, get inspired from one of the predefined palettes below.
3. Do not invent random color combinations unless explicitly requested.

You do not have to always choose the first palette. Select one randomly when drawing inspiration.