styles.yml

UI styles configuration: ASCII header, semantic color palette, and separator.

Purpose
Structure
Field reference
Omitting the file
Light / dark resolution
Customizing colors
Common pitfalls
Related commands

Purpose

workspace/styles.yml controls the visual appearance of the dwe CLI: the branded header shown at startup, the seven semantic color tokens used across every UI surface (tables, status sections, command browser, Fang help output), and the separator character used in definition lists.

The CLI loads it and applies your palette at startup. Omitting the file entirely produces identical built-in defaults.

Structure

header:
  lines:
    - "Welcome to"
    - "DWE Laravel"
  font: doom
  tagline: "Local dev, container-orchestrated."

colors:
  accent:  "#2EC3EB"
  success: "#22C55E"
  warning: "#F59E0B"
  danger:  "#EF4444"
  muted:   "#9AA3BB"
  border:  "#334155"
  text:    ""

separator: "·"

Field reference

`header`

Controls the branded header displayed by dwe (no args) and dwe info. The brand identity line ({▪} DWE · <project> · <version>) always renders; the optional tagline and ASCII art are layered on top when configured.

Field	Type	Default	Description
`header.lines`	list of strings	(none)	Text lines rendered as ASCII art under the brand line
`header.font`	string	`standard`	FIGlet font name (doom, banner, big, block, slant, …)
`header.tagline`	string	(none)	Single tagline line rendered in muted color below the brand line

The ASCII block is colored using the accent token. There is no separate header.color — color always derives from the semantic palette.

`colors`

Seven semantic color tokens. Values are raw hex strings (e.g. "#2EC3EB"). Empty / missing entries fall back to the built-in light or dark default for that token (see Light / dark resolution).

Token	Used for
`accent`	Branded surfaces — brand line, ASCII header, section titles, focused borders, table headers, filter matches, active pagination, `{▪}` logomark inner square
`success`	OK / running / enabled states; success notifications; `[--yes ON]` indicator
`warning`	Warning diagnostics; partial / degraded states
`danger`	Error diagnostics; failed notifications
`muted`	Secondary text — counts, separators, dimmed list rows, tree glyphs, inactive pagination, command/flag descriptions; and the `○` stopped stack icon in `dwe prompt`
`border`	Default (unfocused) panel and table borders
`text`	Default body text. Empty means “let the terminal pick the foreground color” — recommended in nearly all cases

The same seven tokens drive Fang’s --help rendering: title / command / flag / program use accent, description / argument use muted.

`separator`

separator: "·"

Character used between label and value in definition items (e.g. Project · laravel).

Omitting the file

If workspace/styles.yml does not exist, the CLI falls back to built-in defaults. It works identically — no error is produced.

Light / dark resolution

Each token has a built-in light and dark hex default. At startup the CLI detects whether the terminal has a dark background once and resolves every token to a single hex string for the rest of the process. The same resolved palette is shared across every surface the CLI renders — tables, status sections, command browser, and Fang’s --help output.

Token	Light default	Dark default
`accent`	`#0EA5E9`	`#2EC3EB`
`success`	`#16A34A`	`#22C55E`
`warning`	`#D97706`	`#F59E0B`
`danger`	`#DC2626`	`#EF4444`
`muted`	`#64748B`	`#9AA3BB`
`border`	`#CBD5E1`	`#334155`
`text`	(empty — terminal default)	(empty — terminal default)

A user-provided non-empty value overrides both modes — overrides are not per-mode. Editing workspace/styles.yml and re-running a dwe command is the supported way to retheme during a session.

Customizing colors

Override any subset of tokens; unset tokens keep their light/dark defaults.

colors:
  accent:  "#A78BFA"   # purple brand
  success: "#10B981"   # teal-leaning green
  muted:   "#94A3B8"

For a monochrome look, set accent and success to the same hue family and let muted/border provide contrast.

Common pitfalls

Using ANSI 256 codes instead of hex — the schema expects hex strings ("#2EC3EB"). Bare numeric codes are not valid.
Forgetting quotes on hex values — YAML usually tolerates #2EC3EB unquoted (it is not a comment after a key), but quoting is the safer habit.
Per-mode overrides — there is no light: / dark: sub-key. A user override applies in both modes; pick a hex that reads well on both backgrounds, or rely on the built-in defaults.
Old keys silently ignored at runtime — the loader is lenient. Use dwe validate to catch stale keys before they become invisible no-ops.

dwe (no args) — shows brand header + compact summary
dwe info — shows full info dashboard with styled output
dwe validate — surfaces rename warnings for legacy palette keys

styles.yml

Contents