1173206772/photo-skills / skills/hk-multiverse-photo
hk-multiverse-photo
VerifiedTransform supplied Hong Kong, city, street, vehicle, skyline, or harbor photographs into bold multiverse-collision still images that preserve source geometry while combining real photography, flat 2D animation, and dimensional 3D/cel rendering. Use for Spider-Verse-inspired city edits, cyberpunk universe collisions, distinct style fields, phase-wheel sectors, vehicle timeline portals, tram interchange scenes, Douyin/9:16 batches, selective frame revisions, coherent multi-image series, or original HK//VERSE archive annotations. Generate an original visual system without copying characters, official logos, or film frames. Do not use for video unless the user explicitly asks for motion.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.7 KB |
| agents/openai.yaml | config | 260 B |
| references/annotation-system.md | markdown | 13.7 KB |
| references/collision-layouts.md | markdown | 30.3 KB |
| references/universe-atlas.md | markdown | 9.3 KB |
| scripts/make_annotation_svg.pyexecutable | script | 14.0 KB |
| scripts/validate_image.pyexecutable | script | 8.1 KB |
references/annotation-system.md
View on GitHub# HK//VERSE annotation overlay
Add this original archive overlay only after the clean multiverse still is frozen. When clean and tagged outputs are requested together, “frozen” means the clean plate passed internal visual QA and was saved as a separate file; continue directly to annotation. Pause for user approval only when the user explicitly asks to approve the clean plate first. Render exact text and diagrams as a transparent SVG with `scripts/make_annotation_svg.py`, then composite that SVG over the untouched clean plate.
## Contents
1. [Contract](#contract)
2. [Field identities](#field-identities)
3. [Required content](#required-content)
4. [Script configuration](#script-configuration)
5. [Adaptive placement](#adaptive-placement)
6. [Working example](#working-example)
7. [Render and deliver](#render-and-deliver)
8. [Validation](#validation)
## Contract
- Keep `*_clean.png` unchanged. The annotation script creates a transparent SVG; it does not contain or alter the clean plate.
- Put every user-visible title, label, number, and footer string in JSON. Never ask ImageGen or another image model to draw archive text.
- Use the built-in original `HK//VERSE` orbital mark. Never insert the official Spider-Man logo, a spider emblem, mask-eye symbol, franchise wordmark, or copied title treatment.
- Show a field record and location, a Chinese and English title, the active/incoming fields, 2–5 scene-specific callouts, and a split bottom summary.
- Keep radar and chroma information optional. The script supports a phase radar directly. It has no `chroma` JSON key; when useful, put a concise chroma note in one footer segment or extend the generated SVG afterward as exact vector graphics.
- Reposition modules for every scene. Use negative space and keep panels, labels, and leaders away from faces, people, vehicle silhouettes, and the main visual hook.
- Keep claims observational. Do not invent a precise location, person, date, or technical reading from appearance alone.
## Field identities
Use these meanings everywhere. Do not redefine U01–U05 as generic visual qualities.
| ID | Label | Annotation color | Meaning |
| --- | --- | --- | --- |
| `U01` | `VECTOR-99` | `#14D9E8` | Dark architectural futurism, cyan depth slabs, hard scan seams |
| `U02` | `NOIR` | `#EEF3F5` | Silver-gelatin monochrome, hard light wedges, one restrained clue |
| `U03` | `CEL-RIG` | `#F0A8D4` | Clean cel systems, diagnostic geometry, calibrated modules |
| `U04` | `MUMBA` | `#FFB21A` | Warm flat pigment, stacked terraces, orbital painted bands |
| `U05` | `PUNK` | `#FF176F` | Screen-print energy, registration offsets, stencil motion |
| `PHOTO` | `SOURCE` | `#C9D2D8` | Source-locked photographic anchor |
Use one field as `PRIMARY` and two to four as `INCOMING`, matching the clean plate. Include `PHOTO / SOURCE / ANCHOR` when the photographic territory is useful to explain. The script accepts at most six legend rows.
## Required content
### Field record, location, and title
The title block renders:
```text
HK//VERSE
FIELD // <record> · <location>
<title_cn> / <title_en>
ACTIVE <active items>
```
Supply both `title_cn` and `title_en`. Keep the Chinese title short enough to end before the English title begins; the script places English at a fixed 235 px offset and does not wrap. Keep `record`, `location`, and `active` compact.
### Active and incoming legend
Use `active` as a short array such as `['U01 PRIMARY', 'U03 INCOMING']`. The script accepts one to six entries of at most 18 characters each and wraps after the third entry. Build matching `legend` rows with the canonical ID, label, and role. The script does not derive one from the other, so verify them manually.
Use roles such as `PRIMARY`, `INCOMING`, and `ANCHOR`. Omit inactive universes unless the user requests a complete five-field index.
### Scene-specific callouts
Write 2–5 short observations tied to visible collision features, for example `U01 // DEPTH SLAB`, `U03 // CALIBRATION RING`, or `U05 // FRAME-SKIP ECHO`. Do not use generic filler or invented measurements.
Place each label box in negative space and each target on the described feature. The script draws one elbow leader and a circular endpoint. Keep callout leaders from crossing faces or each other. Prefer 2–6 English words or a similarly compact Chinese label; callouts do not wrap.
### Optional radar and chroma
Set `radar` to `false` to omit it. Omission, `null`, or `{}` enables the default radar, so use the literal Boolean `false` when no radar is wanted. When enabled, `radar.at` is its center point and `primary` controls the colored phase vector.
For a wheel or other measured radial scene, provide one to six actual phase arcs in `radar.sectors`. Each object uses image-plane `start`, `end`, and `color`; angles use 0° at 12 o'clock and increase clockwise. Supplying sectors replaces the decorative phase vector. Do not show the default radar on a wheel frame when the fixed vector would contradict the visible sector map.
The current radar is an abstract phase indicator, not a five-value analytical chart. Do not claim it contains measured scores. The current script has no separate chroma renderer; put optional chroma copy in `footer.center`, such as `CHROMA // CYAN + ACID`, or add a later vector module without touching the clean plate.
### Split bottom summary
Use `footer.left`, `footer.center`, and `footer.right` as three concise records. Typical content is field/location at left, active media or chroma at center, and source-lock/status at right. If the lower-center hero would be covered, set `center` to an empty string and split the information between left and right.
## Script configuration
All coordinates are canvas pixels, not normalized values. A point is a two-number array `[x, y]` inside `0..width` and `0..height`.
### Top-level keys
| Key | Type | Script behavior |
| --- | --- | --- |
| `width` | integer | Canvas width; defaults to `1080`, minimum `600` |
| `height` | integer | Canvas height; defaults to `1920`, minimum `800` |
| `record` | string | Field record; defaults to `001` |
| `location` | string | Location line; defaults to `HONG KONG / FIELD` |
| `title_cn` | string | Chinese title; defaults to `多元宇宙现场` |
| `title_en` | string | English title; defaults to `DIMENSION COLLISION` |
| `primary` | universe ID or hex color | Colors the optional radar phase vector; defaults to `U01` |
| `active` | array of strings | Exact items joined on the title block's `ACTIVE` line |
| `legend` | array of objects | Up to six field rows; see below |
| `callouts` | array of objects | Scene callouts; use 2–5 |
| `layout` | object | Positions title, legend, and footer baseline |
| `radar` | `false` or object | Disables the radar or positions it with `at` |
| `footer` | object | Supplies the three bottom strings |
### Nested keys
- `legend[]`: supply one to six rows; require `id`, `label`, and `role`; optionally set `color`. With no color, the script uses `id` as the palette lookup. The script rejects, rather than truncates, longer arrays.
- `callouts[]`: supply two to five entries; require `label`, `label_at`, and `target`; optionally set `color` and numeric `width` (default `250`, minimum `120`).
- `layout`: set `title: [x,y]`, `legend: [x,y]`, and numeric `footer_y`.
- `radar`: set `false`, set `{ "at": [x,y] }` for the abstract phase vector, or add `sectors: [{"start": 0, "end": 90, "color": "U03"}]` for actual radial phase arcs.
- `footer`: set exact strings in `left`, `center`, and `right`.
For `color` and `primary`, use `U01`–`U05`, `PHOTO`, `#RGB`, or `#RRGGBB`. Prefer universe IDs so the script palette remains consistent.
The SVG escapes JSON strings before inserting them. Keep the JSON UTF-8 and verify that the selected SVG rasterizer has Chinese glyph coverage.
## Adaptive placement
Inspect the approved clean plate before writing coordinates. Mark the face/hero silhouette, protected signs and landmarks, callout targets, and the largest quiet edge regions.
At the 1080×1920 reference size, account for these script footprints:
- `layout.title` is the logo origin. Its panel spans approximately `x-18` to `x+532` and `y-18` to `y+158`.
- `layout.legend` is the legend heading origin. Rows start 27 px below it and advance by 34 px; reserve about 280 px of width.
- Each callout label begins at `label_at`, is 46 px high, and uses its configured `width`. Its elbow projects 32 px toward the target.
- `radar.at` is the radar center. Reserve about 60 px on every side and 80 px below it for the phase label.
- `layout.footer_y` is the baseline for all three footer strings. Reserve at least 24 px below it.
Use roughly 50–60 px outer margins at 1080×1920. Place the title in the best upper-edge negative space and the legend on a different quiet edge. Move callout labels, rather than their targets, away from the hero. Keep footer strings short enough that the left, centered, and right-aligned segments do not collide.
Do not reuse one coordinate template across a batch. Flip title/legend sides, vary radar placement or disable it, and route callouts according to each image's negative space. Keep the data hierarchy consistent even when placement changes.
The script's type sizes are fixed for the 1080×1920 reference canvas: Chinese title 32 px, English title 17 px, legend 14 px, callouts 15 px, and footer 13 px. For another canvas size, choose all pixel coordinates manually and inspect the result; the script does not automatically scale typography or module dimensions.
The title and callouts have translucent dark panels. The legend and footer do not. Place the latter over low-detail dark or midtone regions where the light text remains readable; move them instead of changing the clean image.
## Working example
This configuration uses U01 as primary, U03 and U05 as incoming fields, three callouts, an enabled radar, and a three-part footer:
```json
{
"width": 1080,
"height": 1920,
"record": "HKV-042",
"location": "中環 / CENTRAL, HONG KONG",
"title_cn": "維港相位交匯",
"title_en": "HARBOUR PHASE INTERCHANGE",
"primary": "U01",
"active": ["U01 PRIMARY", "U03 INCOMING", "U05 INCOMING"],
"legend": [
{"id": "U01", "label": "VECTOR-99", "role": "PRIMARY"},
{"id": "U03", "label": "CEL-RIG", "role": "INCOMING"},
{"id": "U05", "label": "PUNK", "role": "INCOMING"},
{"id": "PHOTO", "label": "SOURCE", "role": "ANCHOR"}
],
"callouts": [
{
"label": "U01 // DEPTH SLAB",
"label_at": [60, 430],
"target": [430, 650],
"color": "U01",
"width": 270
},
{
"label": "U03 // CALIBRATION RING",
"label_at": [748, 760],
"target": [635, 910],
"color": "U03",
"width": 282
},
{
"label": "U05 // FRAME-SKIP ECHO",
"label_at": [60, 1160],
"target": [405, 1090],
"color": "U05",
"width": 286
}
],
"layout": {
"title": [54, 58],
"legend": [780, 82],
"footer_y": 1830
},
"radar": {
"at": [116, 1690],
"sectors": [
{"start": 350, "end": 170, "color": "U01"},
{"start": 190, "end": 250, "color": "U03"},
{"start": 270, "end": 330, "color": "U05"}
]
},
"footer": {
"left": "FIELD 042 // CENTRAL",
"center": "CHROMA // CYAN + ACID",
"right": "PHOTO BASE // SOURCE-LOCKED"
}
}
```
Treat these coordinates as a working syntax example, not a reusable layout. Reposition them after inspecting the actual clean plate.
## Render and deliver
Run the script with absolute or resolved paths:
```bash
python3 scripts/make_annotation_svg.py annotation.json annotation.svg
```
The script refuses to overwrite an existing SVG. Pass `--force` only after confirming that replacement is intended.
Render the SVG to a transparent raster with an available SVG renderer, then composite it over the clean plate at the same dimensions. Do not regenerate the clean artwork to fix annotation text or placement; edit the JSON and rerun the vector pass.
Deliver non-destructively:
```text
<stem>_clean.png
<stem>_tagged.png
<stem>_annotation.svg
<stem>_annotation.json
```
Retain the SVG and JSON whenever annotations are requested so exact copy and placement remain editable.
The JSON-to-SVG text content is deterministic. A tagged raster is byte-stable only when the same font files and renderer version are used. Pin the renderer and embed or supply the same licensed CJK-capable fonts for archival reproduction; otherwise inspect the raster for font substitution and do not claim byte-identical layout across machines.
## Validation
- Run the script and require a zero exit status plus `WROTE: <path>`.
- Open the SVG by itself and the final tagged raster. Inspect both at full size and thumbnail size.
- Compare `record`, `location`, both titles, `active`, every legend row, callout, and footer segment against the JSON exactly.
- Confirm `U01 VECTOR-99`, `U02 NOIR`, `U03 CEL-RIG`, `U04 MUMBA`, and `U05 PUNK` wherever those IDs appear. These are the public, original field labels; do not substitute official character or franchise names in the overlay.
- Confirm `primary`, `active`, legend roles, callout colors, and the clean plate's actual fields agree.
- Confirm 2–5 callouts are scene-specific, terminate on the intended features, do not cross each other, and do not cross a face.
- Confirm no title, legend, radar, callout panel, or footer covers a face, hero silhouette, source-critical sign, vehicle identity, or main collision hook.
- Confirm Chinese glyphs render, long strings do not collide or clip, footer segments remain separated, and legend/footer contrast is readable.
- Confirm the tagged raster has the same dimensions as the clean plate and that the clean file remains unchanged.
- Confirm the overlay contains only the original HK//VERSE mark and no official Spider-Man logo or borrowed franchise mark.
If validation fails, change JSON copy or pixel coordinates and rerun the SVG. Never repair exact text with image generation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |