codex-rs/tui/styles.md

# Headers, primary, and secondary text

- **Headers:** Use `bold`. For markdown with various header levels, leave in the `#` signs.
- **Primary text:** Default.
- **Secondary text:** Use `dim`.

# Foreground colors

- **Default:** Most of the time, just use the default foreground color. `reset` can help get it back.
- **User input tips, selection, and status indicators:** Use ANSI `cyan`.
- **Success and additions:** Use ANSI `green`.
- **Errors, failures and deletions:** Use ANSI `red`.
- **Codex:** Use ANSI `magenta`.

# Avoid

- Avoid custom colors because there's no guarantee that they'll contrast well or look good in various terminal color themes. (`shimmer.rs` is an exception that works well because we take the default colors and just adjust their levels.)
- Avoid ANSI `black` & `white` as foreground colors because the default terminal theme color will do a better job. (Use `reset` if you need to in order to get those.) The exception is if you need contrast rendering over a manually colored background.
- Avoid ANSI `blue` and `yellow` because for now the style guide doesn't use them. Prefer a foreground color mentioned above.

(There are some rules to try to catch this in `clippy.toml`.)
fix: clean up styles & colors and define in styles.md (#2401) New style guide: # Headers, primary, and secondary text - Headers: Use `bold`. For markdown with various header levels, leave in the `#` signs. - Primary text: Default. - Secondary text: Use `dim`. # Foreground colors - Default: Most of the time, just use the default foreground color. `reset` can help get it back. - Selection: Use ANSI `blue`. (Ed & AE want to make this cyan too, but we'll do that in a followup since it's riskier in different themes.) - User input tips and status indicators: Use ANSI `cyan`. - Success and additions: Use ANSI `green`. - Errors, failures and deletions: Use ANSI `red`. - Codex: Use ANSI `magenta`. # Avoid - Avoid custom colors because there's no guarantee that they'll contrast well or look good on various terminal color themes. - Avoid ANSI `black`, `white`, `yellow` as foreground colors because the terminal theme will do a better job. (Use `reset` if you need to in order to get those.) The exception is if you need contrast rendering over a manually colored background. (There are some rules to try to catch this in `clippy.toml`.) # Testing Tested in a variety of light and dark color themes in Terminal, iTerm2, and Ghostty. 2025-08-18 08:26:29 -07:00			`# Headers, primary, and secondary text`

			- Headers: Use `bold`. For markdown with various header levels, leave in the `#` signs.
			`- Primary text: Default.`
			- Secondary text: Use `dim`.

			`# Foreground colors`

			- Default: Most of the time, just use the default foreground color. `reset` can help get it back.
fix: stop using ANSI blue (#2421) - One less color. - Replaced with cyan which looks better next to other cyan components. 2025-08-18 09:02:25 -07:00			- User input tips, selection, and status indicators: Use ANSI `cyan`.
fix: clean up styles & colors and define in styles.md (#2401) New style guide: # Headers, primary, and secondary text - Headers: Use `bold`. For markdown with various header levels, leave in the `#` signs. - Primary text: Default. - Secondary text: Use `dim`. # Foreground colors - Default: Most of the time, just use the default foreground color. `reset` can help get it back. - Selection: Use ANSI `blue`. (Ed & AE want to make this cyan too, but we'll do that in a followup since it's riskier in different themes.) - User input tips and status indicators: Use ANSI `cyan`. - Success and additions: Use ANSI `green`. - Errors, failures and deletions: Use ANSI `red`. - Codex: Use ANSI `magenta`. # Avoid - Avoid custom colors because there's no guarantee that they'll contrast well or look good on various terminal color themes. - Avoid ANSI `black`, `white`, `yellow` as foreground colors because the terminal theme will do a better job. (Use `reset` if you need to in order to get those.) The exception is if you need contrast rendering over a manually colored background. (There are some rules to try to catch this in `clippy.toml`.) # Testing Tested in a variety of light and dark color themes in Terminal, iTerm2, and Ghostty. 2025-08-18 08:26:29 -07:00			- Success and additions: Use ANSI `green`.
			- Errors, failures and deletions: Use ANSI `red`.
			- Codex: Use ANSI `magenta`.

			`# Avoid`

fix: stop using ANSI blue (#2421) - One less color. - Replaced with cyan which looks better next to other cyan components. 2025-08-18 09:02:25 -07:00			- Avoid custom colors because there's no guarantee that they'll contrast well or look good in various terminal color themes. (`shimmer.rs` is an exception that works well because we take the default colors and just adjust their levels.)
fix: clean up styles & colors and define in styles.md (#2401) New style guide: # Headers, primary, and secondary text - Headers: Use `bold`. For markdown with various header levels, leave in the `#` signs. - Primary text: Default. - Secondary text: Use `dim`. # Foreground colors - Default: Most of the time, just use the default foreground color. `reset` can help get it back. - Selection: Use ANSI `blue`. (Ed & AE want to make this cyan too, but we'll do that in a followup since it's riskier in different themes.) - User input tips and status indicators: Use ANSI `cyan`. - Success and additions: Use ANSI `green`. - Errors, failures and deletions: Use ANSI `red`. - Codex: Use ANSI `magenta`. # Avoid - Avoid custom colors because there's no guarantee that they'll contrast well or look good on various terminal color themes. - Avoid ANSI `black`, `white`, `yellow` as foreground colors because the terminal theme will do a better job. (Use `reset` if you need to in order to get those.) The exception is if you need contrast rendering over a manually colored background. (There are some rules to try to catch this in `clippy.toml`.) # Testing Tested in a variety of light and dark color themes in Terminal, iTerm2, and Ghostty. 2025-08-18 08:26:29 -07:00			- Avoid ANSI `black` & `white` as foreground colors because the default terminal theme color will do a better job. (Use `reset` if you need to in order to get those.) The exception is if you need contrast rendering over a manually colored background.
fix: stop using ANSI blue (#2421) - One less color. - Replaced with cyan which looks better next to other cyan components. 2025-08-18 09:02:25 -07:00			- Avoid ANSI `blue` and `yellow` because for now the style guide doesn't use them. Prefer a foreground color mentioned above.
fix: clean up styles & colors and define in styles.md (#2401) New style guide: # Headers, primary, and secondary text - Headers: Use `bold`. For markdown with various header levels, leave in the `#` signs. - Primary text: Default. - Secondary text: Use `dim`. # Foreground colors - Default: Most of the time, just use the default foreground color. `reset` can help get it back. - Selection: Use ANSI `blue`. (Ed & AE want to make this cyan too, but we'll do that in a followup since it's riskier in different themes.) - User input tips and status indicators: Use ANSI `cyan`. - Success and additions: Use ANSI `green`. - Errors, failures and deletions: Use ANSI `red`. - Codex: Use ANSI `magenta`. # Avoid - Avoid custom colors because there's no guarantee that they'll contrast well or look good on various terminal color themes. - Avoid ANSI `black`, `white`, `yellow` as foreground colors because the terminal theme will do a better job. (Use `reset` if you need to in order to get those.) The exception is if you need contrast rendering over a manually colored background. (There are some rules to try to catch this in `clippy.toml`.) # Testing Tested in a variety of light and dark color themes in Terminal, iTerm2, and Ghostty. 2025-08-18 08:26:29 -07:00
			(There are some rules to try to catch this in `clippy.toml`.)