mulmoterminal-theme

Solid

Build a colour scheme of your own for MulmoTerminal — one that joins Midnight, Nord, Daylight and Solarized in Settings' theme picker and can then be pinned per project. Writes `themes` in `~/.mulmoterminal/config.json`, the whole-app palette (panels, borders, accent, text), which has no UI for creating one — Settings only lets you pick from what exists. Use when the user wants their own theme, a dark/light variant that isn't shipped, a scheme drawn from a painting, a photo or a brand's colours, or says the built-in themes are too dark, too blue, too low-contrast. For colouring ONE project's cell (its badge and header), or assigning an existing theme to a directory, use mulmoterminal-dirs instead.

Code & Development 211 stars 30 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
77
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Make a colour scheme of your own `themes` in `~/.mulmoterminal/config.json` defines schemes that appear in Settings' picker next to the four built-ins, and that a project can then name in its `.mulmoterminal.json` `theme` key. Settings can *choose* a theme; nothing in the app can *create* one. This skill is that path. This is the **whole app's** palette — panel backgrounds, borders, accent, text. A single project's badge and header colours are a different thing (`mulmoterminal-dirs`). ## How to run this ### 1. Find out what they're going after Ask for the direction first, with concrete options rather than "what colours?": - **From something that exists** — a painting, a photo, a brand, an editor theme they like. This is the easiest to do well: take 5–8 colours off the source and assign them to roles. - **A variant of a built-in** — "Nord but warmer", "Daylight with more contrast". Use `extends` and write only the keys that differ. - **Light or dark**, if it isn't already obvious. It decides every value below. ### 2. Decide `extends` — and know what it costs ```jsonc { "id": "arles", "label": "Van Gogh (Arles)", "extends": "daylight", "colors": { "--accent": "#c8971e" } } ``` - **With `extends`**, `colors` is a diff over that built-in (`midnight` / `nord` / `daylight` / `solarized`). Anything you leave out is inherited. Start here — it is far easier to get right, and a three-key diff is a real theme. - **Without `extends`**, the theme must set **every** one ...

Details

Author
receptron
Repository
receptron/mulmoterminal
Created
2 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

mulmoterminal-dirs

Colour-code and order the directories you actually work in, from wherever you are. Writes each project's `<project>/.mulmoterminal.json` — name badge, project icon image, the seven chrome colours, xterm palette (`theme` / `colors`), terminal font size, `orderPriority` (where it sits in the grid and in the launcher's chips), and `worktreeEnv` (a value of its own per git worktree for each declared variable — a dev-server port, a database name — so two `yarn dev` do not fight over 3000). Starts from your recent MulmoTerminal directories rather than just the current one, reads the configs you already have, works out the convention you have been following, and continues it for the ones that are unset or off-pattern — so a newly cloned repo gets the colour and rank it should have had. Also owns what the header shows once a STATUS takes the background over — `headerStatusColors` (a colour per working / done / blocked) and `headerStatusTint` — in a project's file and as the global default in `~/.mulmoterminal/config.

211 Updated today
receptron
AI & Automation Featured

add-theme

Add a new color theme to pixtuoid (a full ~90-role palette across 9 groups, rendered into the office). Use when the user says 'add a <name> theme', 'new color scheme', or 'port <palette> to pixtuoid'. Orchestrates the Rust registration PLUS the two steps agents miss — the site manifest bridge test and the committed-media regen.

474 Updated today
IvanWng97
AI & Automation Solid

mulmoterminal-config

The way into configuring MulmoTerminal, and the way to find out how it is configured now. Use for a broad or unsure request — "configure MulmoTerminal", "set this up", "customize this", "what can I change?", first-run setup — and route to the skill that owns the area. Also answers "how is this set up right now?", "why isn't my setting working?", "did that take effect?" by reading the live config — the global `~/.mulmoterminal/config.json`, each project's `.mulmoterminal.json`, and what the app ACTUALLY parsed from them — including keys it dropped in validation, which is the difference between a setting you never made and one that silently never applied. Owns the global settings that have no skill of their own — work comments on an issue (issueWorkComments), the PR clone footer (prWorkdirFooter), the closing summary (appendSystemPrompt), the decision digest (decisionDigest), the periodic dev-work log (worklogEnabled), roster row length (cockpitLines), the grid header's load read-out (showLoadAverage), pinned c

211 Updated today
receptron