# Seeming

> Seeming is coordinated appearance change at scale: mass theming, batch rebranding, global copy tone shifts, and UI-wide presentation updates. The underlying structures stay the same. The spell is about coherent surface transformation, not structural reinvention.

- Skill: `hmbown/seeming` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hmbown/seeming`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hmbown/seeming/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Hmbown (https://skillmd.com/u/hmbown)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hmbown/seeming

---


# Seeming

Re-skin the whole cast without rewriting their roles.

## Overview

Seeming is interpreted here as a metaphorical spell with a shipping-now execution model.

Canonical source: Seeming (spell)

Provider target: OpenClaw

## When To Use

- You need a coordinated presentation change across many screens, assets, or components.
- The work is primarily visual, tonal, or labeling-related rather than architectural.
- You want users to experience a new look without relearning the system.

## Workflow

1. Identify the presentation-layer surfaces that need to change together.
2. Define the transformation rules for brand, tone, theme, or visual treatment.
3. Return the change set and the QA plan that confirms structure and behavior stayed put.

## Deliverables

- A batch presentation-change plan.
- A mapping of old visual or tonal patterns to new ones.
- A regression checklist for unchanged structure and accessibility.

## Guardrails

- Do not let cosmetic changes obscure compliance information, product semantics, or accessibility affordances.
- Call out where the request sounds superficial but would actually require structural changes.

## Default Invocation

Use $seeming to plan a coordinated presentation-only change across this set of interfaces, assets, or messages.