Imported from Xiddler/PORTABLE_ENV (themes/warm-burnout/warp/AGENTS.md). Install upstream with npx skills add Xiddler/PORTABLE_ENV --skill warp. Copyright stays with the author.

Warp -- Agent Instructions

Platform Reference

See the root AGENTS.md for the canonical palette, design principles, and brand rules. Do not duplicate palette tables here.

Warp Theme Format

• Warp custom themes are YAML files, one per variant. Spec: https://docs.warp.dev/terminal/appearance/custom-themes.
• Install path: ~/.warp/themes/ (macOS), ${XDG_DATA_HOME:-$HOME/.local/share}/warp-terminal/themes/ (Linux), %APPDATA%\warp\Warp\data\themes\ (Windows).
• Themes are picked at runtime via Settings > Appearance > Themes > Custom.
• Hex values must include the # prefix. Both 6-digit hex and quoted strings are accepted; we quote everything for YAML safety.

Color Key Mapping

The 8-key set in each ANSI block must be exactly black, red, green, yellow, blue, magenta, cyan, white. Order in the YAML file is irrelevant to Warp but kept conventional for readability.

File Naming

• Dark theme: warm-burnout-dark.yaml
• Light theme: warm-burnout-light.yaml
• Lowercase hyphenated. Warp derives the display name from the name: key inside the file, not from the filename.

Emphasis Color Discipline

Warp themes are pure terminal colors plus a single chrome accent. The chrome fields (accent, background, foreground, cursor) must stay warm. Steel-blue #90aec0 (dark types) and #285464 (light types) are reserved for editor types and must not appear in chrome.

ANSI blue (terminal_colors.normal.blue and .bright.blue) is exempt: programs depend on the standard 16-color slot for ANSI blue, and terminal programs may use this color in syntax-highlighted prompts and file listings. Drop the canonical ghostty values verbatim.

Out of Scope

• background_image: not used in any Warm Burnout platform.
• gradients: not used.
• Submission to the public warpdotdev/themes community repo: separate effort.