بنقرة واحدة
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Help the user create, install, or package zot themes, including theme-only extensions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Help the user create a new zot extension (slash command, LLM tool, or guard) in any language.
Run a thorough self-review pass on the most recent change.
Diagnose and minimally fix a failing test, then re-run.
| name | write-zot-themes |
| description | Help the user create, install, or package zot themes, including theme-only extensions. |
Use this skill when the user asks for help creating, editing, installing, debugging, or packaging a zot color theme. Read this skill before generating a theme file or advising on theme extension layout.
A zot theme is a JSON file that overrides any subset of zot's built-in light/dark theme values. Theme files are intentionally permissive: nothing is required. A file may contain only colors, only spinner settings, only syntax colors, or only metadata. Missing values always inherit from the built-in detected light/dark default.
User themes are discovered from:
$ZOT_HOME/themes/*.json
Extension themes are discovered in-place from loaded extension dirs:
$ZOT_HOME/extensions/<extension>/theme.json
$ZOT_HOME/extensions/<extension>/themes/theme.json
<project>/.zot/extensions/<extension>/theme.json
<project>/.zot/extensions/<extension>/themes/theme.json
zot does not copy extension themes into $ZOT_HOME/themes; extension
owned themes stay in the extension directory. The settings picker stores
an absolute path for extension-owned themes and loads that file directly.
Valid; inherits all colors/spinner/syntax from zot defaults.
{
"name": "my-theme",
"description": "Metadata only; all visuals inherit zot defaults."
}
{
"name": "pink-accent",
"colors": {
"accent": 204
}
}
{
"name": "split-accent",
"colors": {
"dark": { "accent": 204 },
"light": { "accent": 161 }
}
}
Top-level spinner overrides are valid and apply to both modes.
{
"name": "custom-spinner",
"description": "Only changes the busy spinner.",
"spinner_frames": ["◢", "◣", "◤", "◥"],
"spinner_messages": ["working"],
"spinner_interval_ms": 120
}
If colors.light is missing, zot applies colors.dark overrides on
top of the built-in light default when running in light mode. The
inverse is also true: if dark is missing but light exists, light
settings are used on dark defaults.
{
"name": "custom-spinner",
"description": "An alternative spinner for zot that only displays a single spinner text.",
"colors": {
"dark": {
"spinner_frames": ["◢", "◣", "◤", "◥"],
"spinner_messages": ["working"],
"spinner_interval_ms": 120
}
}
}
All fields below are optional.
{
"name": "my-theme",
"description": "Shown in /settings → color theme.",
"color_descriptions": {
"accent": "Optional documentation for humans. zot ignores this object."
},
"colors": {
"dark": {
"fg": 253,
"muted": 244,
"accent": 111,
"user": 180,
"user_bubble_bg": "#42454b",
"user_bubble_fg": 248,
"assistant": 117,
"tool": 114,
"tool_out": 245,
"error": 203,
"warning": 214,
"spinner": 183,
"selection_bg": 24,
"selection_fg": 231,
"spinner_frames": ["⠋", "⠙", "⠚", "⠞", "⠖", "⠦", "⠴", "⠲", "⠳", "⠓"],
"spinner_messages": ["thinking", "working"],
"spinner_interval_ms": 80,
"syntax_base_style": "monokai",
"syntax": {
"keyword": "#81a1c1 bold",
"keyword_constant": "#81a1c1",
"keyword_declaration": "#81a1c1",
"keyword_namespace": "#81a1c1",
"keyword_reserved": "#81a1c1 bold",
"keyword_type": "#88c0d0",
"name_builtin": "#88c0d0",
"name_function": "#8fbcbb",
"name_class": "#a3be8c bold",
"name_decorator": "#b48ead",
"literal_string": "#a3be8c",
"literal_string_escape": "#bf616a",
"literal_number": "#d08770",
"comment": "#616e88 italic",
"comment_preproc": "#b48ead",
"operator": "#eceff4",
"punctuation": "#d8dee9",
"text": "#e5e9f0"
}
},
"light": {
"fg": 236,
"muted": 244,
"accent": 33
}
}
}
You may also put overrides directly at the top level, or directly
under colors, when they should apply to both modes:
{
"name": "tiny",
"accent": 204,
"colors": {
"spinner_messages": ["shipping"]
}
}
fg — default foreground text.muted — secondary text, dividers, gutters, inactive hints.accent — prompt bar, bullets, links, headings, active markers.user — user role label color; mostly compatibility.user_bubble_bg — background behind user message rows.user_bubble_fg — foreground inside user message rows.assistant — assistant/zot accent and spinner text.tool — tool names, success marks, diff additions.tool_out — plain tool-output text.error — errors, refused calls, diff deletions.warning — warnings and high context-usage state.spinner — reserved spinner color slot.selection_bg — highlighted row background.selection_fg — highlighted row foreground.Most color fields are xterm-256 indexes (0–255).
user_bubble_bg supports richer terminal color forms:
254
"#42454b"
{ "mode": "256", "index": 254 }
{ "mode": "ansi", "index": 100 }
{ "mode": "rgb", "r": 66, "g": 69, "b": 75 }
Spinner settings can appear at top level, under colors, or under
colors.dark / colors.light.
spinner_frames — list of frame strings. Use single-cell glyphs
when possible so status-bar alignment stays clean.spinner_messages — list of messages; zot chooses one per turn.spinner_interval_ms — frame interval in milliseconds; must be
positive. Missing/invalid falls back to 80ms.Example:
{
"spinner_frames": ["◐", "◓", "◑", "◒"],
"spinner_messages": ["shipping pixels", "warming edge cache"],
"spinner_interval_ms": 120
}
Syntax highlighting uses Chroma style entries. Values may include
attributes after the color, such as bold, italic, or underline.
Common fields:
keywordkeyword_constantkeyword_declarationkeyword_namespacekeyword_reservedkeyword_typename_builtinname_functionname_classname_decoratorliteral_stringliteral_string_escapeliteral_numbercommentcomment_preprocoperatorpunctuationtextExample:
{
"colors": {
"dark": {
"syntax_base_style": "monokai",
"syntax": {
"keyword": "#f05b8d",
"name_function": "#b675f1",
"literal_string": "#58c760",
"comment": "#a1a1a1 italic"
}
}
}
}
mkdir -p "$ZOT_HOME/themes"
cp my-theme.json "$ZOT_HOME/themes/my-theme.json"
Then open /settings and choose color theme. zot switches theme
immediately and persists the selection in $ZOT_HOME/config.json.
If a selected theme file is deleted, zot resets the setting to the built-in auto/default theme.
A zot extension can exist only to ship a theme. No slash command, subprocess, or executable is required when the extension contains a valid theme file.
Layout:
$ZOT_HOME/extensions/my-theme-extension/
├── extension.json
└── theme.json
or:
$ZOT_HOME/extensions/my-theme-extension/
├── extension.json
└── themes/
└── theme.json
extension.json for a theme-only extension:
{
"name": "my-theme-extension",
"version": "1.0.0",
"description": "Ships a zot color theme",
"enabled": true
}
No exec is needed when theme.json or themes/theme.json exists.
If exec is present, zot treats it as a normal extension too.
In /settings → color theme, extension themes show source info in
the description, e.g. from extension my-theme-extension — ....
python3 -m json.tool theme.json before installing.