better-dsh 0.2.5-c → 0.2.5-e

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/optional/creative/creative-heartmula.md

@@ -1,191 +0,0 @@
----
-title: "Heartmula — HeartMuLa: Suno-like song generation from lyrics + tags"
-sidebar_label: "Heartmula"
-description: "HeartMuLa: Suno-like song generation from lyrics + tags"
----
-
-{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
-
-# Heartmula
-
-HeartMuLa: Suno-like song generation from lyrics + tags.
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Optional — install with `hermes skills install official/creative/heartmula` |
-| Path | `optional-skills/creative\heartmula` |
-| Version | `1.0.0` |
-| Author | Teknium (teknium1), Hermes Agent |
-| License | MIT |
-| Platforms | linux, macos, windows |
-| Tags | `music`, `audio`, `generation`, `ai`, `heartmula`, `heartcodec`, `lyrics`, `songs` |
-| Related skills | [`audiocraft-audio-generation`](/docs/user-guide/skills/optional/creative/creative-audiocraft-audio-generation), [`songwriting-and-ai-music`](/docs/user-guide/skills/bundled/creative/creative-songwriting-and-ai-music) |
-
-## Reference: full SKILL.md
-
-:::info
-The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
-:::
-
-# HeartMuLa - Open-Source Music Generation
-
-## Overview
-HeartMuLa is a family of open-source music foundation models (Apache-2.0) that generates music conditioned on lyrics and tags, with multilingual support. Generates full songs from lyrics + tags. Comparable to Suno for open-source. Includes:
-- **HeartMuLa** - Music language model (3B/7B) for generation from lyrics + tags
-- **HeartCodec** - 12.5Hz music codec for high-fidelity audio reconstruction
-- **HeartTranscriptor** - Whisper-based lyrics transcription
-- **HeartCLAP** - Audio-text alignment model
-
-## When to Use
-- User wants to generate music/songs from text descriptions
-- User wants an open-source Suno alternative
-- User wants local/offline music generation
-- User asks about HeartMuLa, heartlib, or AI music generation
-
-## Hardware Requirements
-- **Minimum**: 8GB VRAM with `--lazy_load true` (loads/unloads models sequentially)
-- **Recommended**: 16GB+ VRAM for comfortable single-GPU usage
-- **Multi-GPU**: Use `--mula_device cuda:0 --codec_device cuda:1` to split across GPUs
-- 3B model with lazy_load peaks at ~6.2GB VRAM
-
-## Installation Steps
-
-### 1. Clone Repository
-```bash
-cd ~/  # or desired directory
-git clone https://github.com/HeartMuLa/heartlib.git
-cd heartlib
-```
-
-### 2. Create Virtual Environment (Python 3.10 required)
-```bash
-uv venv --python 3.10 .venv
-. .venv/bin/activate
-uv pip install -e .
-```
-
-### 3. Fix Dependency Compatibility Issues
-
-**IMPORTANT**: As of Feb 2026, the pinned dependencies have conflicts with newer packages. Apply these fixes:
-
-```bash
-# Upgrade datasets (old version incompatible with current pyarrow)
-uv pip install --upgrade datasets
-
-# Upgrade transformers (needed for huggingface-hub 1.x compatibility)
-uv pip install --upgrade transformers
-```
-
-### 4. Patch Source Code (Required for transformers 5.x)
-
-**Patch 1 - RoPE cache fix** in `src/heartlib/heartmula/modeling_heartmula.py`:
-
-In the `setup_caches` method of the `HeartMuLa` class, add RoPE reinitialization after the `reset_caches` try/except block and before the `with device:` block:
-
-```python
-# Re-initialize RoPE caches that were skipped during meta-device loading
-from torchtune.models.llama3_1._position_embeddings import Llama3ScaledRoPE
-for module in self.modules():
-    if isinstance(module, Llama3ScaledRoPE) and not module.is_cache_built:
-        module.rope_init()
-        module.to(device)
-```
-
-**Why**: `from_pretrained` creates model on meta device first; `Llama3ScaledRoPE.rope_init()` skips cache building on meta tensors, then never rebuilds after weights are loaded to real device.
-
-**Patch 2 - HeartCodec loading fix** in `src/heartlib/pipelines/music_generation.py`:
-
-Add `ignore_mismatched_sizes=True` to ALL `HeartCodec.from_pretrained()` calls (there are 2: the eager load in `__init__` and the lazy load in the `codec` property).
-
-**Why**: VQ codebook `initted` buffers have shape `[1]` in checkpoint vs `[]` in model. Same data, just scalar vs 0-d tensor. Safe to ignore.
-
-### 5. Download Model Checkpoints
-```bash
-cd heartlib  # project root
-hf download --local-dir './ckpt' 'HeartMuLa/HeartMuLaGen'
-hf download --local-dir './ckpt/HeartMuLa-oss-3B' 'HeartMuLa/HeartMuLa-oss-3B-happy-new-year'
-hf download --local-dir './ckpt/HeartCodec-oss' 'HeartMuLa/HeartCodec-oss-20260123'
-```
-
-All 3 can be downloaded in parallel. Total size is several GB.
-
-## GPU / CUDA
-
-HeartMuLa uses CUDA by default (`--mula_device cuda --codec_device cuda`). No extra setup needed if the user has an NVIDIA GPU with PyTorch CUDA support installed.
-
-- The installed `torch==2.4.1` includes CUDA 12.1 support out of the box
-- `torchtune` may report version `0.4.0+cpu` — this is just package metadata, it still uses CUDA via PyTorch
-- To verify GPU is being used, look for "CUDA memory" lines in the output (e.g. "CUDA memory before unloading: 6.20 GB")
-- **No GPU?** You can run on CPU with `--mula_device cpu --codec_device cpu`, but expect generation to be **extremely slow** (potentially 30-60+ minutes for a single song vs ~4 minutes on GPU). CPU mode also requires significant RAM (~12GB+ free). If the user has no NVIDIA GPU, recommend using a cloud GPU service (Google Colab free tier with T4, Lambda Labs, etc.) or the online demo at https://heartmula.github.io/ instead.
-
-## Usage
-
-### Basic Generation
-```bash
-cd heartlib
-. .venv/bin/activate
-python ./examples/run_music_generation.py \
-  --model_path=./ckpt \
-  --version="3B" \
-  --lyrics="./assets/lyrics.txt" \
-  --tags="./assets/tags.txt" \
-  --save_path="./assets/output.mp3" \
-  --lazy_load true
-```
-
-### Input Formatting
-
-**Tags** (comma-separated, no spaces):
-```
-piano,happy,wedding,synthesizer,romantic
-```
-or
-```
-rock,energetic,guitar,drums,male-vocal
-```
-
-**Lyrics** (use bracketed structural tags):
-```
-[Intro]
-
-[Verse]
-Your lyrics here...
-
-[Chorus]
-Chorus lyrics...
-
-[Bridge]
-Bridge lyrics...
-
-[Outro]
-```
-
-### Key Parameters
-| Parameter | Default | Description |
-|-----------|---------|-------------|
-| `--max_audio_length_ms` | 240000 | Max length in ms (240s = 4 min) |
-| `--topk` | 50 | Top-k sampling |
-| `--temperature` | 1.0 | Sampling temperature |
-| `--cfg_scale` | 1.5 | Classifier-free guidance scale |
-| `--lazy_load` | false | Load/unload models on demand (saves VRAM) |
-| `--mula_dtype` | bfloat16 | Dtype for HeartMuLa (bf16 recommended) |
-| `--codec_dtype` | float32 | Dtype for HeartCodec (fp32 recommended for quality) |
-
-### Performance
-- RTF (Real-Time Factor) ≈ 1.0 — a 4-minute song takes ~4 minutes to generate
-- Output: MP3, 48kHz stereo, 128kbps
-
-## Pitfalls
-1. **Do NOT use bf16 for HeartCodec** — degrades audio quality. Use fp32 (default).
-2. **Tags may be ignored** — known issue (#90). Lyrics tend to dominate; experiment with tag ordering.
-3. **Triton not available on macOS** — Linux/CUDA only for GPU acceleration.
-4. **RTX 5080 incompatibility** reported in upstream issues.
-5. The dependency pin conflicts require the manual upgrades and patches described above.
-
-## Links
-- Repo: https://github.com/HeartMuLa/heartlib
-- Models: https://huggingface.co/HeartMuLa
-- Paper: https://arxiv.org/abs/2601.10547
-- License: Apache-2.0

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/optional/creative/creative-hyperframes.md

@@ -1,222 +0,0 @@
----
-title: "Hyperframes — Render MP4/WebM videos from HTML compositions"
-sidebar_label: "Hyperframes"
-description: "Render MP4/WebM videos from HTML compositions"
----
-
-{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
-
-# Hyperframes
-
-Render MP4/WebM videos from HTML compositions.
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Optional — install with `hermes skills install official/creative/hyperframes` |
-| Path | `optional-skills/creative\hyperframes` |
-| Version | `1.0.0` |
-| Author | heygen-com |
-| License | Apache-2.0 |
-| Platforms | linux, macos, windows |
-| Tags | `creative`, `video`, `animation`, `html`, `gsap`, `motion-graphics` |
-| Related skills | [`manim-video`](/docs/user-guide/skills/bundled/creative/creative-manim-video), [`meme-generation`](/docs/user-guide/skills/optional/creative/creative-meme-generation) |
-
-## Reference: full SKILL.md
-
-:::info
-The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
-:::
-
-# HyperFrames
-
-HTML is the source of truth for video. A composition is an HTML file with `data-*` attributes for timing, a GSAP timeline for animation, and CSS for appearance. The HyperFrames engine captures the page frame-by-frame and encodes to MP4/WebM with FFmpeg.
-
-**Complement to `manim-video`:** Use `manim-video` for mathematical/geometric explainers (equations, 3B1B-style). Use `hyperframes` for motion-graphics, talking-head with captions, product tours, social overlays, shader transitions, and anything driven by real video/audio media.
-
-## When to Use
-
-- User asks for a rendered video from text, a script, or a website
-- Animated title cards, lower thirds, or typographic intros
-- Captioned narration video (TTS + captions synced to waveform)
-- Audio-reactive visuals (beat sync, spectrum bars, pulsing glow)
-- Scene-to-scene transitions (crossfade, wipe, shader warp, flash-through-white)
-- Social overlays (Instagram/TikTok/YouTube style)
-- Website-to-video pipeline (capture a URL, produce a promo)
-- Any HTML/CSS/JS animation that must render deterministically to a video file
-
-Do **not** use this skill for:
-- Pure math/equation animation (→ `manim-video`)
-- Image generation or memes (→ `meme-generation`, image models)
-- Live video conferencing or streaming
-
-## Quick Reference
-
-```bash
-npx hyperframes init my-video               # scaffold a project
-cd my-video
-npx hyperframes lint                        # validate before preview/render
-npx hyperframes preview                     # live-reload preview (long-lived server, port 3002)
-npx hyperframes render --output final.mp4   # render to MP4
-npx hyperframes doctor                      # diagnose environment issues
-```
-
-`preview` is a **long-lived** Next.js server that holds Chrome render workers open. Always stop it when done (see [Cleanup](#cleanup)) — a forgotten preview keeps idle `chrome-headless-shell` workers alive that, on GPU-less hosts (WSL, containers, CI), spin a CPU core each indefinitely via software WebGL (swiftshader).
-
-Render flags: `--quality draft|standard|high` · `--fps 24|30|60` · `--format mp4|webm` · `--docker` (reproducible) · `--strict`.
-
-Full CLI reference: [references/cli.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/cli.md).
-
-## Setup (one-time)
-
-```bash
-bash "$(dirname "$(find ~/.hermes/skills -path '*/hyperframes/SKILL.md' 2>/dev/null | head -1)")/scripts/setup.sh"
-```
-
-The script:
-1. Verifies Node.js >= 22 and FFmpeg are installed (prints fix instructions if not).
-2. Installs the `hyperframes` CLI globally (`npm install -g hyperframes@>=0.4.2`).
-3. Pre-caches `chrome-headless-shell` via Puppeteer — **required** for best-quality rendering via Chrome's `HeadlessExperimental.beginFrame` capture path.
-4. Runs `npx hyperframes doctor` and reports the result.
-
-See [references/troubleshooting.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/troubleshooting.md) if setup fails.
-
-## Procedure
-
-### 1. Plan before writing HTML
-
-Before touching code, articulate at a high level:
-- **What** — narrative arc, key moments, emotional beats
-- **Structure** — compositions, tracks (video/audio/overlays), durations
-- **Visual identity** — colors, fonts, motion character (explosive / cinematic / fluid / technical)
-- **Hero frame** — for each scene, the moment when the most elements are simultaneously visible. This is the static layout you'll build first.
-
-**Visual Identity Gate (HARD-GATE).** Before writing ANY composition HTML, a visual identity must be defined. Do NOT write compositions with default or generic colors (`#333`, `#3b82f6`, `Roboto` are tells that this step was skipped). Check in order:
-
-1. **`DESIGN.md` at project root?** → Use its exact colors, fonts, motion rules, and "What NOT to Do" constraints.
-2. **User named a style** (e.g. "Swiss Pulse", "dark and techy", "luxury brand")? → Generate a minimal `DESIGN.md` with `## Style Prompt`, `## Colors` (3-5 hex with roles), `## Typography` (1-2 families), `## What NOT to Do` (3-5 anti-patterns).
-3. **None of the above?** → Ask 3 questions before writing any HTML:
-   - Mood? (explosive / cinematic / fluid / technical / chaotic / warm)
-   - Light or dark canvas?
-   - Any brand colors, fonts, or visual references?
-
-   Then generate a `DESIGN.md` from the answers. Every composition must trace its palette and typography back to `DESIGN.md` or explicit user direction.
-
-### 2. Scaffold
-
-```bash
-npx hyperframes init my-video --non-interactive
-```
-
-Templates: `blank`, `warm-grain`, `play-mode`, `swiss-grid`, `vignelli`, `decision-tree`, `kinetic-type`, `product-promo`, `nyt-graph`. Pass `--example <name>` to pick one, `--video clip.mp4` or `--audio track.mp3` to seed with media.
-
-### 3. Layout before animation
-
-Write the static HTML+CSS for the **hero frame first** — no GSAP yet. The `.scene-content` container must fill the scene (`width:100%; height:100%; padding:Npx`) with `display:flex` + `gap`. Use padding to push content inward — never `position: absolute; top: Npx` on a content container (content overflows when taller than the remaining space).
-
-Only after the hero frame looks right, add `gsap.from()` entrances (animate **to** the CSS position) and `gsap.to()` exits (animate **from** it).
-
-See [references/composition.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/composition.md) for the full data-attribute schema and composition rules.
-
-### 4. Animate with GSAP
-
-Every composition must:
-- Register its timeline: `window.__timelines["<composition-id>"] = tl`
-- Start paused: `gsap.timeline({ paused: true })` — the player controls playback
-- Use finite `repeat` values (no `repeat: -1` — breaks the capture engine). Calculate: `repeat: Math.ceil(duration / cycleDuration) - 1`.
-- Be deterministic — no `Math.random()`, `Date.now()`, or wall-clock logic. Use a seeded PRNG if you need pseudo-randomness.
-- Build synchronously — no `async`/`await`, `setTimeout`, or Promises around timeline construction.
-
-See [references/gsap.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/gsap.md) for the core GSAP API (tweens, eases, stagger, timelines).
-
-### 5. Transitions between scenes
-
-Multi-scene compositions require transitions. Rules:
-1. **Always use a transition between scenes** — no jump cuts.
-2. **Always use entrance animations** on every scene element (`gsap.from(...)`).
-3. **Never use exit animations** except on the final scene — the transition IS the exit.
-4. The final scene may fade out.
-
-Use `npx hyperframes add <transition-name>` to install shader transitions (`flash-through-white`, `liquid-wipe`, etc.). Full list: `npx hyperframes add --list`.
-
-### 6. Audio, captions, TTS, audio-reactive, highlighting
-
-- **Audio:** always a separate `<audio>` element (video is `muted playsinline`).
-- **TTS:** `npx hyperframes tts "Script text" --voice af_nova --output narration.wav`. List voices with `--list`. Voice ID first letter encodes language (`a`/`b`=English, `e`=Spanish, `f`=French, `j`=Japanese, `z`=Mandarin, etc.) — the CLI auto-infers the phonemizer locale; pass `--lang` only to override. Non-English phonemization requires `espeak-ng` installed system-wide.
-- **Captions:** `npx hyperframes transcribe narration.wav` → word-level transcript. Pick style from the transcript tone (hype / corporate / tutorial / storytelling / social — see the table in `references/features.md`). **Language rule:** never use `.en` whisper models unless the audio is confirmed English — `.en` translates non-English audio instead of transcribing it. Every caption group MUST have a hard `tl.set(el, { opacity: 0, visibility: "hidden" }, group.end)` kill after its exit tween — otherwise groups leak visible into later ones.
-- **Audio-reactive visuals:** pre-extract audio bands (bass / mid / treble) and sample per-frame inside the timeline with a `for` loop of `tl.call(draw, [], f / fps)` — a single long tween does NOT react to audio. Map bass → `scale` (pulse), treble → `textShadow`/`boxShadow` (glow), overall amplitude → `opacity`/`y`/`backgroundColor`. Avoid equalizer-bar clichés — let content guide the visual, audio drive its behavior.
-- **Marker-style highlighting:** highlight, circle, burst, scribble, sketchout effects for text emphasis are deterministic CSS+GSAP — see `references/features.md#marker-highlighting`. Fully seekable, no animated SVG filters.
-- **Scene transitions:** every multi-scene composition MUST use transitions (no jump cuts). Pick from CSS primitives (push slide, blur crossfade, zoom through, staggered blocks) or shader transitions (`flash-through-white`, `liquid-wipe`, `cross-warp-morph`, `chromatic-split`, etc.) via `npx hyperframes add`. Mood and energy tables live in `references/features.md#transitions`. Do not mix CSS and shader transitions in the same composition.
-
-### 7. Lint, validate, inspect, preview, render
-
-```bash
-npx hyperframes lint              # catches missing data-composition-id, overlapping tracks, unregistered timelines
-npx hyperframes validate          # WCAG contrast audit at 5 timestamps
-npx hyperframes inspect           # visual layout audit — overflow, off-frame elements, occluded text
-npx hyperframes preview           # live browser preview
-npx hyperframes render --quality draft --output draft.mp4    # fast iteration
-npx hyperframes render --quality high --output final.mp4     # final delivery
-```
-
-`hyperframes validate` samples background pixels behind every text element and warns on contrast ratios below 4.5:1 (or 3:1 for large text). `hyperframes inspect` is the layout-side companion — runs the page at multiple timestamps and flags issues that a static lint can't see (a caption that wraps past the safe area only at 4.5s, a card that overflows when its title is the longest variant, an element that ends up behind a transition shader). Run `inspect` especially on compositions with speech bubbles, cards, captions, or tight typography.
-
-### 8. Website-to-video (if the user gives a URL)
-
-Use the 7-step capture-to-video workflow in [references/website-to-video.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/website-to-video.md): capture → DESIGN.md → SCRIPT.md → storyboard → composition → render → deliver.
-
-## Cleanup
-
-`render` is one-shot (workers exit when it finishes). `preview` is **not** — it runs a background Next.js server that keeps Chrome workers resident until you stop it. Never leave one running: on GPU-less hosts each idle worker's swiftshader process pegs a CPU core, and a preview left open for days stacks up multiple.
-
-Stop a preview when the user is done reviewing (or before starting a new one):
-
-```bash
-pkill -f "hyperframes.*preview"     # the Studio server (frees port 3002)
-pkill -f chrome-headless-shell      # its render workers; only safe if nothing else uses them
-```
-
-If unsure whether other tools use `chrome-headless-shell`, check first: `pgrep -af chrome-headless-shell`. Recover a wedged host (many idle workers spinning CPU) the same way — see [references/troubleshooting.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/troubleshooting.md#runaway-cpu-from-leftover-preview-workers).
-
-## Pitfalls
-
-- **Leaving `preview` running** — it's a long-lived server holding Chrome workers; on WSL/containers/CI those idle workers spin a CPU core each (software WebGL). Stop it when done — see [Cleanup](#cleanup).
-
-- **`HeadlessExperimental.beginFrame' wasn't found`** — Chromium 147+ removed this protocol. Ensure you're on `hyperframes@>=0.4.2` (auto-detects and falls back to screenshot mode). Escape hatch: `export PRODUCER_FORCE_SCREENSHOT=true`. See [hyperframes#294](https://github.com/heygen-com/hyperframes/issues/294) and [references/troubleshooting.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/troubleshooting.md).
-- **System Chrome (not `chrome-headless-shell`)** — renders hang for 120s then timeout. Run `npx puppeteer browsers install chrome-headless-shell` (setup.sh does this). `hyperframes doctor` reports which binary will be used.
-- **`repeat: -1` anywhere** — breaks the capture engine. Always compute a finite repeat count.
-- **`gsap.set()` on clip elements that enter later** — the element doesn't exist at page load. Use `tl.set(selector, vars, timePosition)` inside the timeline instead, at or after the clip's `data-start`.
-- **`<br>` inside content text** — forced breaks don't know the rendered font width, so natural wrap + `<br>` double-breaks. Use `max-width` to let text wrap. Exception: short display titles where each word is deliberately on its own line.
-- **Animating `visibility` or `display`** — GSAP can't tween these. Use `autoAlpha` (handles both visibility and opacity).
-- **Calling `video.play()` or `audio.play()`** — the framework owns playback. Never call these yourself.
-- **Building timelines async** — the capture engine reads `window.__timelines` synchronously after page load. Never wrap timeline construction in `async`, `setTimeout`, or a Promise.
-- **Standalone `index.html` wrapped in `<template>`** — hides all content from the browser. Only **sub-compositions** loaded via `data-composition-src` use `<template>`.
-- **Using video for audio** — always muted `<video>` + separate `<audio>`.
-
-## Verification
-
-Before and after rendering:
-
-1. **Lint + validate + inspect pass:** `npx hyperframes lint --strict && npx hyperframes validate && npx hyperframes inspect` (lint catches structural issues, validate catches contrast, inspect catches visual layout / overflow issues — see troubleshooting.md if warnings appear).
-2. **Animation choreography** — for new compositions or significant animation changes, run the animation map. `npx hyperframes init` copies the skill scripts into the project, so the path is project-local:
-   ```bash
-   node skills/hyperframes/scripts/animation-map.mjs <composition-dir> \
-     --out <composition-dir>/.hyperframes/anim-map
-   ```
-   Outputs a single `animation-map.json` with per-tween summaries, ASCII Gantt timeline, stagger detection, dead zones (>1s with no animation), element lifecycles, and flags (`offscreen`, `collision`, `invisible`, `paced-fast` &lt;0.2s, `paced-slow` >2s). Scan summaries and flags — fix or justify each. Skip on small edits.
-3. **File exists + non-zero:** `ls -lh final.mp4`.
-4. **Duration matches `data-duration`:** `ffprobe -v error -show_entries format=duration -of default=nw=1:nk=1 final.mp4`.
-5. **Visual check:** extract a mid-composition frame: `ffmpeg -i final.mp4 -ss 00:00:05 -vframes 1 preview.png`.
-6. **Audio present if expected:** `ffprobe -v error -show_streams -select_streams a -of default=nw=1:nk=1 final.mp4 | head -1`.
-
-If `hyperframes render` fails, run `npx hyperframes doctor` and attach its output when reporting.
-
-## References
-
-- [composition.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/composition.md) — data attributes, timeline contract, non-negotiable rules, typography/asset rules
-- [cli.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/cli.md) — every CLI command (init, capture, lint, validate, inspect, preview, render, transcribe, tts, doctor, browser, info, upgrade, benchmark)
-- [gsap.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/gsap.md) — GSAP core API for HyperFrames (tweens, eases, stagger, timelines, matchMedia)
-- [features.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/features.md) — captions, TTS, audio-reactive, marker highlighting, transitions (load on demand)
-- [website-to-video.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/website-to-video.md) — 7-step capture-to-video workflow
-- [troubleshooting.md](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/creative\hyperframes/references/troubleshooting.md) — OpenClaw fix, env vars, common render errors

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/optional/creative/creative-impeccable.md

@@ -1,56 +0,0 @@
----
-title: "Impeccable — Frontend design guidance, upstream-maintained (impeccable)"
-sidebar_label: "Impeccable"
-description: "Frontend design guidance, upstream-maintained (impeccable)"
----
-
-{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
-
-# Impeccable
-
-Frontend design guidance, upstream-maintained (impeccable).
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Optional — install with `hermes skills install official/creative/impeccable` |
-| Path | `optional-skills/creative\impeccable` |
-| Version | `4.1.2` |
-| Author | Paul Bakaus (pbakaus) |
-| License | Apache-2.0 |
-| Platforms | linux, macos, windows |
-| Tags | `design`, `frontend`, `ui`, `ux`, `web-design`, `anti-slop` |
-| Related skills | [`claude-design`](/docs/user-guide/skills/bundled/creative/creative-claude-design), [`popular-web-designs`](/docs/user-guide/skills/bundled/creative/creative-popular-web-designs) |
-
-## Reference: full SKILL.md
-
-:::info
-The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
-:::
-
-# Impeccable (upstream-maintained)
-
-> **Catalog stub.** This entry is maintained upstream at
-> [pbakaus/impeccable](https://github.com/pbakaus/impeccable): the project
-> ships and verifies a Hermes-native skill bundle under `.hermes/skills/`.
-> `hermes skills install impeccable` pulls the current bundle live from that
-> repo (quarantined and scanned like any hub install) — this directory holds
-> only the catalog metadata, so the vendored copy can never go stale.
-
-Impeccable is a design language for AI coding agents: one skill exposing 23
-sub-commands (`/impeccable init`, `craft`, `shape`, `critique`, `audit`,
-`polish`, `bolder`, `quieter`, `distill`, `harden`, `onboard`, `animate`,
-`colorize`, `typeset`, `layout`, `delight`, `overdrive`, `clarify`, `adapt`,
-`optimize`, `extract`, `document`, `live`), explicit anti-pattern guidance
-(overused fonts, purple gradients, nested cards, bounce easing), and a
-61-rule deterministic detector CLI (`npx impeccable detect`) that needs no
-LLM or API key.
-
-After install, start with:
-
-```
-/impeccable init
-```
-
-Full documentation: https://impeccable.style