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

---

# Seeming
Re-skin the whole cast without rewriting their roles.
## What This Skill Does
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.
In this grimoire, Seeming is treated as a metaphorical spell with a shipping-now delivery profile.
Canonical reference input: Seeming (spell).
## 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.

## Prerequisites

- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.

## Procedure

1. Restate the target, the success condition, and any no-touch boundaries before taking action.
2. Identify the presentation-layer surfaces that need to change together.
3. Define the transformation rules for brand, tone, theme, or visual treatment.
4. Return the change set and the QA plan that confirms structure and behavior stayed put.
5. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

## 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.

## Pitfalls / Guardrails

- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- 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.

## Verification

- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.

## Example Invocation
```text
/seeming plan a coordinated presentation-only change across this set of interfaces, assets, or messages
```