Run any Skill in Manus with one click

add-theme

Stars396

Forks24

UpdatedJuly 11, 2026 at 01:06

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

IvanWng97

IvanWng97/pixtuoid

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	add-theme
version	1.0.0
description	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.
metadata	{"scope":"pixtuoid repo only"}

add-theme (v1)

A theme is a pub static Theme with ~90 color roles across 9 groups (surface, office, lighting, furniture, effects, ui, tool_glow, ApplianceColors for corridor appliances, and SourceColors for per-CLI dashboard badge hues). Every field must be supplied — corridor appliances render wrong until each theme provides its own set.

When to use

"Add a <name> theme" / "new color scheme" / "port <palette>".

The checklist

Full current steps: .github/prompts/add-theme.prompt.md

the theme notes in crates/pixtuoid/src/tui/CLAUDE.md. Read an existing theme (e.g. crates/pixtuoid-scene/src/theme/dracula.rs) for the full field set, then:

Create crates/pixtuoid-scene/src/theme/<name>.rs — fill EVERY field; never fall back to the normal palette.
Register: mod in theme/mod.rs, append &<NAME> to ALL_THEMES, theme_by_name() resolves the kebab-case name.
Each palette key must map to a UNIQUE RGB — the renderer recolors by RGB equality (recolor_frame); duplicate keys collide silently.

The two steps agents miss (both have teeth)

site/src/themes.json row (id = the kebab-case name) — theme_gallery_manifest_matches_all_themes (theme/mod.rs) asserts the manifest ids == ALL_THEMES names, so the theme fails just test until the row exists. The site never runs the binary, so this bridge test is the only guard that the switcher stays in sync.
just gen-media — themes.json drives the committed theme stills; a new theme drifts them, so regenerate and commit them or the smoke gen-check reds the PR (the same error the bridge test's message points at).

(Full step list + field details: add-theme.prompt.md + the tui CLAUDE.md theme notes — this skill headlines the two teeth steps agents miss.)

Finish

just test — appliance_palette_is_legible_for_every_theme + the snapshot tests must pass; update insta snapshots if the theme list changed.
Visually verify — render the snapshot example and eyeball the office (see the beautify-decoration skill); a palette that passes the legibility guard can still read badly.
just preflight, then the two-lens-review skill (a theme is public-facing — add the editorial/film-critic lens for the rendered stills).

More from this repository

same repository

add-source

IvanWng97/pixtuoid

Wire a new agent-CLI Source adapter into pixtuoid (a new coding CLI whose sessions become office sprites). Use when the user says 'add support for <CLI>', 'add a source for <tool>', or 'integrate <agent CLI>'. Orchestrates the cross-crate checklist whose steps have TEST TEETH — the ones a diff-scoped edit silently misses (site manifest bridge, per-source badge hue, home-dir fn, plus the two `pixtuoid/tests/*` integration goldens that `-p <crate> --lib` never builds).

2026-07-22396

procedural-lofi

IvanWng97/pixtuoid

Generate a royalty-free lofi (or rain / typing / chime / any ambient) soundtrack ENTIRELY in code — no sampled audio ships. Fingerprint a beloved reference recording, shape synthesis to the measured spectral + temporal curve, freeze one human-blessed take into constant tables, and re-synthesize at launch (loop the bed, scatter the foreground → never repeats, ~0 KB, no licensing risk). Use when adding ambient/generative audio to an app, game, terminal UI, or site, or on 'add another lofi/rain/ambient sound'. Bundles the parameter tables (LOFI-BIBLE.md) + the numpy fingerprint/synth/freeze pipeline.

2026-07-20396

two-lens-review

IvanWng97/pixtuoid

Run pixtuoid's review protocol at either scope — the mandatory pre-merge DIFF gate (2+ differentiated-lens agents on the diff) or a whole-codebase AUDIT (subsystem × factor fan-out over the whole tree). Both draw ONE shared factor taxonomy + verify contract + disposition; they differ only in population and orchestration. Use before merging ANY PR, on 'review this PR/branch' / 'is this ready to merge' (diff scope), or on 'whole-codebase review' / pre-release / periodic audit (whole-codebase scope). Encodes the five hard requirements, the escalation triggers, the adversarial finder→verify fan-out, and the disposition sweep the repo learned the hard way.

2026-07-19396

beautify-decoration

IvanWng97/pixtuoid

Iterate on the visual identity of a top-down pixel-art decoration (sprite + layout integration) in pixtuoid. Use when redesigning an existing decoration (pantry, lounge, meeting room, cubicle decor) or adding a new one. Captures the rebuild trap, the visual-verification loop, resolution constraints, sprite-format pitfalls, and the layout-integration checklist that we learned the hard way during the pantry beautify session.

2026-07-19396

name	add-theme
version	1.0.0
description	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.
metadata	{"scope":"pixtuoid repo only"}

add-theme (v1)

When to use

"Add a <name> theme" / "new color scheme" / "port <palette>".

The checklist

Full current steps: .github/prompts/add-theme.prompt.md

the theme notes in crates/pixtuoid/src/tui/CLAUDE.md. Read an existing theme (e.g. crates/pixtuoid-scene/src/theme/dracula.rs) for the full field set, then:

Create crates/pixtuoid-scene/src/theme/<name>.rs — fill EVERY field; never fall back to the normal palette.
Register: mod in theme/mod.rs, append &<NAME> to ALL_THEMES, theme_by_name() resolves the kebab-case name.
Each palette key must map to a UNIQUE RGB — the renderer recolors by RGB equality (recolor_frame); duplicate keys collide silently.

The two steps agents miss (both have teeth)

site/src/themes.json row (id = the kebab-case name) — theme_gallery_manifest_matches_all_themes (theme/mod.rs) asserts the manifest ids == ALL_THEMES names, so the theme fails just test until the row exists. The site never runs the binary, so this bridge test is the only guard that the switcher stays in sync.
just gen-media — themes.json drives the committed theme stills; a new theme drifts them, so regenerate and commit them or the smoke gen-check reds the PR (the same error the bridge test's message points at).

(Full step list + field details: add-theme.prompt.md + the tui CLAUDE.md theme notes — this skill headlines the two teeth steps agents miss.)

Finish

just test — appliance_palette_is_legible_for_every_theme + the snapshot tests must pass; update insta snapshots if the theme list changed.
Visually verify — render the snapshot example and eyeball the office (see the beautify-decoration skill); a palette that passes the legibility guard can still read badly.
just preflight, then the two-lens-review skill (a theme is public-facing — add the editorial/film-critic lens for the rendered stills).