better-dsh 0.2.5 → 0.3.0-c

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/bundled/creative/creative-ascii-video.md

@@ -1,265 +0,0 @@
----
-title: "Ascii Video — ASCII video: convert video/audio to colored ASCII MP4/GIF"
-sidebar_label: "Ascii Video"
-description: "ASCII video: convert video/audio to colored ASCII MP4/GIF"
----
-
-{/* 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. */}
-
-# Ascii Video
-
-ASCII video: convert video/audio to colored ASCII MP4/GIF.
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Bundled (installed by default) |
-| Path | `skills/creative\ascii-video` |
-| Version | `1.0.0` |
-| Author | SHL0MS, Hermes Agent |
-| License | MIT |
-| Platforms | linux, macos, windows |
-| Tags | `ASCII`, `Video`, `FFmpeg`, `Terminal-Art` |
-
-## 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.
-:::
-
-# ASCII Video Production Pipeline
-
-## When to use
-
-Use when users request: ASCII video, text art video, terminal-style video, character art animation, retro text visualization, audio visualizer in ASCII, converting video to ASCII art, matrix-style effects, or any animated ASCII output.
-
-## What's inside
-
-Production pipeline for ASCII art video — any format. Converts video/audio/images/generative input into colored ASCII character video output (MP4, GIF, image sequence). Covers: video-to-ASCII conversion, audio-reactive music visualizers, generative ASCII art animations, hybrid video+audio reactive, text/lyrics overlays, real-time terminal rendering.
-
-## Creative Standard
-
-This is visual art. ASCII characters are the medium; cinema is the standard.
-
-**Before writing a single line of code**, articulate the creative concept. What is the mood? What visual story does this tell? What makes THIS project different from every other ASCII video? The user's prompt is a starting point — interpret it with creative ambition, not literal transcription.
-
-**First-render excellence is non-negotiable.** The output must be visually striking without requiring revision rounds. If something looks generic, flat, or like "AI-generated ASCII art," it is wrong — rethink the creative concept before shipping.
-
-**Go beyond the reference vocabulary.** The effect catalogs, shader presets, and palette libraries in the references are a starting vocabulary. For every project, combine, modify, and invent new patterns. The catalog is a palette of paints — you write the painting.
-
-**Be proactively creative.** Extend the skill's vocabulary when the project calls for it. If the references don't have what the vision demands, build it. Include at least one visual moment the user didn't ask for but will appreciate — a transition, an effect, a color choice that elevates the whole piece.
-
-**Cohesive aesthetic over technical correctness.** All scenes in a video must feel connected by a unifying visual language — shared color temperature, related character palettes, consistent motion vocabulary. A technically correct video where every scene uses a random different effect is an aesthetic failure.
-
-**Dense, layered, considered.** Every frame should reward viewing. Never flat black backgrounds. Always multi-grid composition. Always per-scene variation. Always intentional color.
-
-## Modes
-
-| Mode | Input | Output | Reference |
-|------|-------|--------|-----------|
-| **Video-to-ASCII** | Video file | ASCII recreation of source footage | `references/inputs.md` § Video Sampling |
-| **Audio-reactive** | Audio file | Generative visuals driven by audio features | `references/inputs.md` § Audio Analysis |
-| **Generative** | None (or seed params) | Procedural ASCII animation | `references/effects.md` |
-| **Hybrid** | Video + audio | ASCII video with audio-reactive overlays | Both input refs |
-| **Lyrics/text** | Audio + text/SRT | Timed text with visual effects | `references/inputs.md` § Text/Lyrics |
-| **TTS narration** | Text quotes + TTS API | Narrated testimonial/quote video with typed text | `references/inputs.md` § TTS Integration |
-
-## Stack
-
-Single self-contained Python script per project. No GPU required.
-
-| Layer | Tool | Purpose |
-|-------|------|---------|
-| Core | Python 3.10+, NumPy | Math, array ops, vectorized effects |
-| Signal | SciPy | FFT, peak detection (audio modes) |
-| Imaging | Pillow (PIL) | Font rasterization, frame decoding, image I/O |
-| Video I/O | ffmpeg (CLI) | Decode input, encode output, mux audio |
-| Parallel | concurrent.futures | N workers for batch/clip rendering |
-| TTS | ElevenLabs API (optional) | Generate narration clips |
-| Optional | OpenCV | Video frame sampling, edge detection |
-
-## Pipeline Architecture
-
-Every mode follows the same 6-stage pipeline:
-
-```
-INPUT → ANALYZE → SCENE_FN → TONEMAP → SHADE → ENCODE
-```
-
-1. **INPUT** — Load/decode source material (video frames, audio samples, images, or nothing)
-2. **ANALYZE** — Extract per-frame features (audio bands, video luminance/edges, motion vectors)
-3. **SCENE_FN** — Scene function renders to pixel canvas (`uint8 H,W,3`). Composes multiple character grids via `_render_vf()` + pixel blend modes. See `references/composition.md`
-4. **TONEMAP** — Percentile-based adaptive brightness normalization. See `references/composition.md` § Adaptive Tonemap
-5. **SHADE** — Post-processing via `ShaderChain` + `FeedbackBuffer`. See `references/shaders.md`
-6. **ENCODE** — Pipe raw RGB frames to ffmpeg for H.264/GIF encoding
-
-## Creative Direction
-
-### Aesthetic Dimensions
-
-| Dimension | Options | Reference |
-|-----------|---------|-----------|
-| **Character palette** | Density ramps, block elements, symbols, scripts (katakana, Greek, runes, braille), project-specific | `architecture.md` § Palettes |
-| **Color strategy** | HSV, OKLAB/OKLCH, discrete RGB palettes, auto-generated harmony, monochrome, temperature | `architecture.md` § Color System |
-| **Background texture** | Sine fields, fBM noise, domain warp, voronoi, reaction-diffusion, cellular automata, video | `effects.md` |
-| **Primary effects** | Rings, spirals, tunnel, vortex, waves, interference, aurora, fire, SDFs, strange attractors | `effects.md` |
-| **Particles** | Sparks, snow, rain, bubbles, runes, orbits, flocking boids, flow-field followers, trails | `effects.md` § Particles |
-| **Shader mood** | Retro CRT, clean modern, glitch art, cinematic, dreamy, industrial, psychedelic | `shaders.md` |
-| **Grid density** | xs(8px) through xxl(40px), mixed per layer | `architecture.md` § Grid System |
-| **Coordinate space** | Cartesian, polar, tiled, rotated, fisheye, Möbius, domain-warped | `effects.md` § Transforms |
-| **Feedback** | Zoom tunnel, rainbow trails, ghostly echo, rotating mandala, color evolution | `composition.md` § Feedback |
-| **Masking** | Circle, ring, gradient, text stencil, animated iris/wipe/dissolve | `composition.md` § Masking |
-| **Transitions** | Crossfade, wipe, dissolve, glitch cut, iris, mask-based reveal | `shaders.md` § Transitions |
-
-### Per-Section Variation
-
-Never use the same config for the entire video. For each section/scene:
-- **Different background effect** (or compose 2-3)
-- **Different character palette** (match the mood)
-- **Different color strategy** (or at minimum a different hue)
-- **Vary shader intensity** (more bloom during peaks, more grain during quiet)
-- **Different particle types** if particles are active
-
-### Project-Specific Invention
-
-For every project, invent at least one of:
-- A custom character palette matching the theme
-- A custom background effect (combine/modify existing building blocks)
-- A custom color palette (discrete RGB set matching the brand/mood)
-- A custom particle character set
-- A novel scene transition or visual moment
-
-Don't just pick from the catalog. The catalog is vocabulary — you write the poem.
-
-## Workflow
-
-### Step 1: Creative Vision
-
-Before any code, articulate the creative concept:
-
-- **Mood/atmosphere**: What should the viewer feel? Energetic, meditative, chaotic, elegant, ominous?
-- **Visual story**: What happens over the duration? Build tension? Transform? Dissolve?
-- **Color world**: Warm/cool? Monochrome? Neon? Earth tones? What's the dominant hue?
-- **Character texture**: Dense data? Sparse stars? Organic dots? Geometric blocks?
-- **What makes THIS different**: What's the one thing that makes this project unique?
-- **Emotional arc**: How do scenes progress? Open with energy, build to climax, resolve?
-
-Map the user's prompt to aesthetic choices. A "chill lo-fi visualizer" demands different everything from a "glitch cyberpunk data stream."
-
-### Step 2: Technical Design
-
-- **Mode** — which of the 6 modes above
-- **Resolution** — landscape 1920x1080 (default), portrait 1080x1920, square 1080x1080 @ 24fps
-- **Hardware detection** — auto-detect cores/RAM, set quality profile. See `references/optimization.md`
-- **Sections** — map timestamps to scene functions, each with its own effect/palette/color/shader config
-- **Output format** — MP4 (default), GIF (640x360 @ 15fps), PNG sequence
-
-### Step 3: Build the Script
-
-Single Python file. Components (with references):
-
-1. **Hardware detection + quality profile** — `references/optimization.md`
-2. **Input loader** — mode-dependent; `references/inputs.md`
-3. **Feature analyzer** — audio FFT, video luminance, or synthetic
-4. **Grid + renderer** — multi-density grids with bitmap cache; `references/architecture.md`
-5. **Character palettes** — multiple per project; `references/architecture.md` § Palettes
-6. **Color system** — HSV + discrete RGB + harmony generation; `references/architecture.md` § Color
-7. **Scene functions** — each returns `canvas (uint8 H,W,3)`; `references/scenes.md`
-8. **Tonemap** — adaptive brightness normalization; `references/composition.md`
-9. **Shader pipeline** — `ShaderChain` + `FeedbackBuffer`; `references/shaders.md`
-10. **Scene table + dispatcher** — time → scene function + config; `references/scenes.md`
-11. **Parallel encoder** — N-worker clip rendering with ffmpeg pipes
-12. **Main** — orchestrate full pipeline
-
-### Step 4: Quality Verification
-
-- **Test frames first**: render single frames at key timestamps before full render
-- **Brightness check**: `canvas.mean() > 8` for all ASCII content. If dark, lower gamma
-- **Visual coherence**: do all scenes feel like they belong to the same video?
-- **Creative vision check**: does the output match the concept from Step 1? If it looks generic, go back
-
-## Critical Implementation Notes
-
-### Brightness — Use `tonemap()`, Not Linear Multipliers
-
-This is the #1 visual issue. ASCII on black is inherently dark. **Never use `canvas * N` multipliers** — they clip highlights. Use adaptive tonemap:
-
-```python
-def tonemap(canvas, gamma=0.75):
-    f = canvas.astype(np.float32)
-    lo, hi = np.percentile(f[::4, ::4], [1, 99.5])
-    if hi - lo < 10: hi = lo + 10
-    f = np.clip((f - lo) / (hi - lo), 0, 1) ** gamma
-    return (f * 255).astype(np.uint8)
-```
-
-Pipeline: `scene_fn() → tonemap() → FeedbackBuffer → ShaderChain → ffmpeg`
-
-Per-scene gamma: default 0.75, solarize 0.55, posterize 0.50, bright scenes 0.85. Use `screen` blend (not `overlay`) for dark layers.
-
-### Font Cell Height
-
-macOS Pillow: `textbbox()` returns wrong height. Use `font.getmetrics()`: `cell_height = ascent + descent`. See `references/troubleshooting.md`.
-
-### ffmpeg Pipe Deadlock
-
-Never `stderr=subprocess.PIPE` with long-running ffmpeg — buffer fills at 64KB and deadlocks. Redirect to file. See `references/troubleshooting.md`.
-
-### Font Compatibility
-
-Not all Unicode chars render in all fonts. Validate palettes at init — render each char, check for blank output. See `references/troubleshooting.md`.
-
-### Per-Clip Architecture
-
-For segmented videos (quotes, scenes, chapters), render each as a separate clip file for parallel rendering and selective re-rendering. See `references/scenes.md`.
-
-## Performance Targets
-
-| Component | Budget |
-|-----------|--------|
-| Feature extraction | 1-5ms |
-| Effect function | 2-15ms |
-| Character render | 80-150ms (bottleneck) |
-| Shader pipeline | 5-25ms |
-| **Total** | ~100-200ms/frame |
-
-## References
-
-| File | Contents |
-|------|----------|
-| `references/architecture.md` | Grid system, resolution presets, font selection, character palettes (20+), color system (HSV + OKLAB + discrete RGB + harmony generation), `_render_vf()` helper, GridLayer class |
-| `references/composition.md` | Pixel blend modes (20 modes), `blend_canvas()`, multi-grid composition, adaptive `tonemap()`, `FeedbackBuffer`, `PixelBlendStack`, masking/stencil system |
-| `references/effects.md` | Effect building blocks: value field generators, hue fields, noise/fBM/domain warp, voronoi, reaction-diffusion, cellular automata, SDFs, strange attractors, particle systems, coordinate transforms, temporal coherence |
-| `references/shaders.md` | `ShaderChain`, `_apply_shader_step()` dispatch, 38 shader catalog, audio-reactive scaling, transitions, tint presets, output format encoding, terminal rendering |
-| `references/scenes.md` | Scene protocol, `Renderer` class, `SCENES` table, `render_clip()`, beat-synced cutting, parallel rendering, design patterns (layer hierarchy, directional arcs, visual metaphors, compositional techniques), complete scene examples at every complexity level, scene design checklist |
-| `references/inputs.md` | Audio analysis (FFT, bands, beats), video sampling, image conversion, text/lyrics, TTS integration (ElevenLabs, voice assignment, audio mixing) |
-| `references/optimization.md` | Hardware detection, quality profiles, vectorized patterns, parallel rendering, memory management, performance budgets |
-| `references/troubleshooting.md` | NumPy broadcasting traps, blend mode pitfalls, multiprocessing/pickling, brightness diagnostics, ffmpeg issues, font problems, common mistakes |
-
----
-
-## Creative Divergence (use only when user requests experimental/creative/unique output)
-
-If the user asks for creative, experimental, surprising, or unconventional output, select the strategy that best fits and reason through its steps BEFORE generating code.
-
-- **Forced Connections** — when the user wants cross-domain inspiration ("make it look organic," "industrial aesthetic")
-- **Conceptual Blending** — when the user names two things to combine ("ocean meets music," "space + calligraphy")
-- **Oblique Strategies** — when the user is maximally open ("surprise me," "something I've never seen")
-
-### Forced Connections
-1. Pick a domain unrelated to the visual goal (weather systems, microbiology, architecture, fluid dynamics, textile weaving)
-2. List its core visual/structural elements (erosion → gradual reveal; mitosis → splitting duplication; weaving → interlocking patterns)
-3. Map those elements onto ASCII characters and animation patterns
-4. Synthesize — what does "erosion" or "crystallization" look like in a character grid?
-
-### Conceptual Blending
-1. Name two distinct visual/conceptual spaces (e.g., ocean waves + sheet music)
-2. Map correspondences (crests = high notes, troughs = rests, foam = staccato)
-3. Blend selectively — keep the most interesting mappings, discard forced ones
-4. Develop emergent properties that exist only in the blend
-
-### Oblique Strategies
-1. Draw one: "Honor thy error as a hidden intention" / "Use an old idea" / "What would your closest friend do?" / "Emphasize the flaws" / "Turn it upside down" / "Only a part, not the whole" / "Reverse"
-2. Interpret the directive against the current ASCII animation challenge
-3. Apply the lateral insight to the visual design before writing code

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/bundled/creative/creative-baoyu-infographic.md

@@ -1,256 +0,0 @@
----
-title: "Baoyu Infographic — Infographics: 21 layouts x 21 styles (信息图, 可视化)"
-sidebar_label: "Baoyu Infographic"
-description: "Infographics: 21 layouts x 21 styles (信息图, 可视化)"
----
-
-{/* 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. */}
-
-# Baoyu Infographic
-
-Infographics: 21 layouts x 21 styles (信息图, 可视化).
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Bundled (installed by default) |
-| Path | `skills/creative\baoyu-infographic` |
-| Version | `1.56.1` |
-| Author | 宝玉 (JimLiu) |
-| License | MIT |
-| Platforms | linux, macos, windows |
-| Tags | `infographic`, `visual-summary`, `creative`, `image-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.
-:::
-
-# Infographic Generator
-
-Adapted from [baoyu-infographic](https://github.com/JimLiu/baoyu-skills) for Hermes Agent's tool ecosystem.
-
-Two dimensions: **layout** (information structure) × **style** (visual aesthetics). Freely combine any layout with any style.
-
-## When to Use
-
-Trigger this skill when the user asks to create an infographic, visual summary, information graphic, or uses terms like "信息图", "可视化", or "高密度信息大图". The user provides content (text, file path, URL, or topic) and optionally specifies layout, style, aspect ratio, or language.
-
-## Options
-
-| Option | Values |
-|--------|--------|
-| Layout | 21 options (see Layout Gallery), default: bento-grid |
-| Style | 21 options (see Style Gallery), default: craft-handmade |
-| Aspect | Named: landscape (16:9), portrait (9:16), square (1:1). Custom: any W:H ratio (e.g., 3:4, 4:3, 2.35:1) |
-| Language | en, zh, ja, etc. |
-
-## Layout Gallery
-
-| Layout | Best For |
-|--------|----------|
-| `linear-progression` | Timelines, processes, tutorials |
-| `binary-comparison` | A vs B, before-after, pros-cons |
-| `comparison-matrix` | Multi-factor comparisons |
-| `hierarchical-layers` | Pyramids, priority levels |
-| `tree-branching` | Categories, taxonomies |
-| `hub-spoke` | Central concept with related items |
-| `structural-breakdown` | Exploded views, cross-sections |
-| `bento-grid` | Multiple topics, overview (default) |
-| `iceberg` | Surface vs hidden aspects |
-| `bridge` | Problem-solution |
-| `funnel` | Conversion, filtering |
-| `isometric-map` | Spatial relationships |
-| `dashboard` | Metrics, KPIs |
-| `periodic-table` | Categorized collections |
-| `comic-strip` | Narratives, sequences |
-| `story-mountain` | Plot structure, tension arcs |
-| `jigsaw` | Interconnected parts |
-| `venn-diagram` | Overlapping concepts |
-| `winding-roadmap` | Journey, milestones |
-| `circular-flow` | Cycles, recurring processes |
-| `dense-modules` | High-density modules, data-rich guides |
-
-Full definitions: `references/layouts/<layout>.md`
-
-## Style Gallery
-
-| Style | Description |
-|-------|-------------|
-| `craft-handmade` | Hand-drawn, paper craft (default) |
-| `claymation` | 3D clay figures, stop-motion |
-| `kawaii` | Japanese cute, pastels |
-| `storybook-watercolor` | Soft painted, whimsical |
-| `chalkboard` | Chalk on black board |
-| `cyberpunk-neon` | Neon glow, futuristic |
-| `bold-graphic` | Comic style, halftone |
-| `aged-academia` | Vintage science, sepia |
-| `corporate-memphis` | Flat vector, vibrant |
-| `technical-schematic` | Blueprint, engineering |
-| `origami` | Folded paper, geometric |
-| `pixel-art` | Retro 8-bit |
-| `ui-wireframe` | Grayscale interface mockup |
-| `subway-map` | Transit diagram |
-| `ikea-manual` | Minimal line art |
-| `knolling` | Organized flat-lay |
-| `lego-brick` | Toy brick construction |
-| `pop-laboratory` | Blueprint grid, coordinate markers, lab precision |
-| `morandi-journal` | Hand-drawn doodle, warm Morandi tones |
-| `retro-pop-grid` | 1970s retro pop art, Swiss grid, thick outlines |
-| `hand-drawn-edu` | Macaron pastels, hand-drawn wobble, stick figures |
-
-Full definitions: `references/styles/<style>.md`
-
-## Recommended Combinations
-
-| Content Type | Layout + Style |
-|--------------|----------------|
-| Timeline/History | `linear-progression` + `craft-handmade` |
-| Step-by-step | `linear-progression` + `ikea-manual` |
-| A vs B | `binary-comparison` + `corporate-memphis` |
-| Hierarchy | `hierarchical-layers` + `craft-handmade` |
-| Overlap | `venn-diagram` + `craft-handmade` |
-| Conversion | `funnel` + `corporate-memphis` |
-| Cycles | `circular-flow` + `craft-handmade` |
-| Technical | `structural-breakdown` + `technical-schematic` |
-| Metrics | `dashboard` + `corporate-memphis` |
-| Educational | `bento-grid` + `chalkboard` |
-| Journey | `winding-roadmap` + `storybook-watercolor` |
-| Categories | `periodic-table` + `bold-graphic` |
-| Product Guide | `dense-modules` + `morandi-journal` |
-| Technical Guide | `dense-modules` + `pop-laboratory` |
-| Trendy Guide | `dense-modules` + `retro-pop-grid` |
-| Educational Diagram | `hub-spoke` + `hand-drawn-edu` |
-| Process Tutorial | `linear-progression` + `hand-drawn-edu` |
-
-Default: `bento-grid` + `craft-handmade`
-
-## Keyword Shortcuts
-
-When user input contains these keywords, **auto-select** the associated layout and offer associated styles as top recommendations in Step 3. Skip content-based layout inference for matched keywords.
-
-If a shortcut has **Prompt Notes**, append them to the generated prompt (Step 5) as additional style instructions.
-
-| User Keyword | Layout | Recommended Styles | Default Aspect | Prompt Notes |
-|--------------|--------|--------------------|----------------|--------------|
-| 高密度信息大图 / high-density-info | `dense-modules` | `morandi-journal`, `pop-laboratory`, `retro-pop-grid` | portrait | — |
-| 信息图 / infographic | `bento-grid` | `craft-handmade` | landscape | Minimalist: clean canvas, ample whitespace, no complex background textures. Simple cartoon elements and icons only. |
-
-## Output Structure
-
-<!-- ascii-guard-ignore -->
-```
-infographic/{topic-slug}/
-├── source-{slug}.{ext}
-├── analysis.md
-├── structured-content.md
-├── prompts/infographic.md
-└── infographic.png
-```
-<!-- ascii-guard-ignore-end -->
-
-Slug: 2-4 words kebab-case from topic. Conflict: append `-YYYYMMDD-HHMMSS`.
-
-## Core Principles
-
-- Preserve source data faithfully — no summarization or rephrasing (but **strip any credentials, API keys, tokens, or secrets** before including in outputs)
-- Define learning objectives before structuring content
-- Structure for visual communication (headlines, labels, visual elements)
-
-## Workflow
-
-### Step 1: Analyze Content
-
-**Load references**: Read `references/analysis-framework.md` from this skill.
-
-1. Save source content (file path or paste → `source.md` using `write_file`)
-   - **Backup rule**: If `source.md` exists, rename to `source-backup-YYYYMMDD-HHMMSS.md`
-2. Analyze: topic, data type, complexity, tone, audience
-3. Detect source language and user language
-4. Extract design instructions from user input
-5. Save analysis to `analysis.md`
-   - **Backup rule**: If `analysis.md` exists, rename to `analysis-backup-YYYYMMDD-HHMMSS.md`
-
-See `references/analysis-framework.md` for detailed format.
-
-### Step 2: Generate Structured Content → `structured-content.md`
-
-Transform content into infographic structure:
-1. Title and learning objectives
-2. Sections with: key concept, content (verbatim), visual element, text labels
-3. Data points (all statistics/quotes copied exactly)
-4. Design instructions from user
-
-**Rules**: Markdown only. No new information. Preserve data faithfully. Strip any credentials or secrets from output.
-
-See `references/structured-content-template.md` for detailed format.
-
-### Step 3: Recommend Combinations
-
-**3.1 Check Keyword Shortcuts first**: If user input matches a keyword from the **Keyword Shortcuts** table, auto-select the associated layout and prioritize associated styles as top recommendations. Skip content-based layout inference.
-
-**3.2 Otherwise**, recommend 3-5 layout×style combinations based on:
-- Data structure → matching layout
-- Content tone → matching style
-- Audience expectations
-- User design instructions
-
-### Step 4: Confirm Options
-
-Use the `clarify` tool to confirm options with the user. Since `clarify` handles one question at a time, ask the most important question first:
-
-**Q1 — Combination**: Present 3+ layout×style combos with rationale. Ask user to pick one.
-
-**Q2 — Aspect**: Ask for aspect ratio preference (landscape/portrait/square or custom W:H).
-
-**Q3 — Language** (only if source ≠ user language): Ask which language the text content should use.
-
-### Step 5: Generate Prompt → `prompts/infographic.md`
-
-**Backup rule**: If `prompts/infographic.md` exists, rename to `prompts/infographic-backup-YYYYMMDD-HHMMSS.md`
-
-**Load references**: Read the selected layout from `references/layouts/<layout>.md` and style from `references/styles/<style>.md`.
-
-Combine:
-1. Layout definition from `references/layouts/<layout>.md`
-2. Style definition from `references/styles/<style>.md`
-3. Base template from `references/base-prompt.md`
-4. Structured content from Step 2
-5. All text in confirmed language
-
-**Aspect ratio resolution** for `{{ASPECT_RATIO}}`:
-- Named presets → ratio string: landscape→`16:9`, portrait→`9:16`, square→`1:1`
-- Custom W:H ratios → use as-is (e.g., `3:4`, `4:3`, `2.35:1`)
-
-Save the assembled prompt to `prompts/infographic.md` using `write_file`.
-
-### Step 6: Generate Image
-
-Use the `image_generate` tool with the assembled prompt from Step 5.
-
-- Map aspect ratio to image_generate's format: `16:9` → `landscape`, `9:16` → `portrait`, `1:1` → `square`
-- For custom ratios, pick the closest named aspect
-- On failure, auto-retry once
-- Save the resulting image URL/path to the output directory
-
-### Step 7: Output Summary
-
-Report: topic, layout, style, aspect, language, output path, files created.
-
-## References
-
-- `references/analysis-framework.md` — Analysis methodology
-- `references/structured-content-template.md` — Content format
-- `references/base-prompt.md` — Prompt template
-- `references/layouts/<layout>.md` — 21 layout definitions
-- `references/styles/<style>.md` — 21 style definitions
-
-## Pitfalls
-
-1. **Data integrity is paramount** — never summarize, paraphrase, or alter source statistics. "73% increase" must stay "73% increase", not "significant increase".
-2. **Strip secrets** — always scan source content for API keys, tokens, or credentials before including in any output file.
-3. **One message per section** — each infographic section should convey one clear concept. Overloading sections reduces readability.
-4. **Style consistency** — the style definition from the references file must be applied consistently across the entire infographic. Don't mix styles.
-5. **image_generate aspect ratios** — the tool only supports `landscape`, `portrait`, and `square`. Custom ratios like `3:4` should map to the nearest option (portrait in that case).