* docs: add runtime-neutral User Input Tools convention across skills Introduce docs/user-input-tools.md as the author-side canonical source and inline the tool-selection rule into every SKILL.md that prompts the user. Also add Skill Self-Containment and User Input Tools sections to CLAUDE.md and the copy-verbatim template to docs/creating-skills.md, so skills stay portable across Claude Code, Codex, Hermes, and other runtimes. * feat: runtime-neutral image generation convention across skills - Introduce inline `## Image Generation Tools` rule in every rendering SKILL.md so skills delegate backend choice instead of hard-coding one; author-side canonical copy lives in docs/image-generation-tools.md. - Add `## Reference Images` support (`--ref`, frontmatter `references:` with direct/style/palette usage) to all seven image-rendering skills. - Move build-batch.ts (with ref propagation into batch JSON) from baoyu-article-illustrator to baoyu-imagine so non-backend skills don't own backend-specific scripts; update baoyu-image-gen stub in sync and relax the CLAUDE.md deprecation note accordingly. * refactor: slim heavy SKILL.md files and move detail to references/ Trim the four largest active skills and move presets, option tables, and confirmation scripts into per-skill references/ so SKILL.md stays focused on the decision flow. - baoyu-slide-deck: 761→258, + styles-gallery.md, confirmation.md - baoyu-image-cards: 657→280, + gallery.md, confirmation.md - baoyu-post-to-wechat: 518→267, + multi-account.md, api-setup.md - baoyu-imagine: 500→230, + providers/, usage-examples.md Also un-deprecate baoyu-image-gen (drop stub warning) so it stays functional alongside baoyu-imagine, and update CLAUDE.md to reflect that both superseded skills are kept in sync rather than stubbed. * refactor: slim four medium SKILL.md files into references/ Continue the P2 pattern on the next tier of skills — move option catalogs, per-provider/adapter detail, and repeated EXTEND.md path boilerplate into their own references so SKILL.md stays focused on the decision flow. - baoyu-comic: 380→297 (art/tone/preset tables → auto-selection.md; Step 7 expanded detail → workflow.md) - baoyu-infographic: 312→207 (layouts/styles/combinations/keywords → gallery.md; ASCII box tables → markdown tables) - baoyu-format-markdown: 376→296 (title + summary generation → title-summary.md; ASCII box tables → markdown tables) - baoyu-url-to-markdown: 334→169 (quality gate + recovery → quality-gate.md; adapters + media download → adapters.md) * chore: sync deprecated skills with their replacements Per project policy, baoyu-xhs-images and baoyu-image-gen are kept functional alongside the active skills they were superseded by. Sync their SKILL.md bodies and references/ to the slimmed baoyu-image-cards and baoyu-imagine versions respectively, so cross-cutting fixes stay consistent. Only the frontmatter (name, description, version, homepage) differs — content is identical. - baoyu-xhs-images: 657→281 (synced with baoyu-image-cards + new confirmation.md, gallery.md) - baoyu-image-gen: 408→231 (synced with baoyu-imagine + new providers/, usage-examples.md) * refactor: collapse EXTEND.md boilerplate into priority tables Replace the dual bash/powershell existence-check blocks and ASCII box art with a single markdown priority table across nine SKILL.md files. The runtime-neutral phrasing removes shell-specific snippets without losing the priority semantics. * fix: address refactor-skills branch review findings - image-gen: restore EXTEND.md paths to baoyu-image-gen (were pointing at baoyu-imagine) and mark descriptions of both deprecated skills as [Deprecated]. - xhs-images: sync neon/warm palettes with image-cards to add the "do not render color names/hex as visible text" safety sentence. - infographic: restore Layout Gallery (21), Style Gallery (21), Recommended Combinations, and Keyword Shortcuts inline (previous refactor split them out but SKILL.md still depended on them), and add the missing references/config/first-time-setup.md + preferences-schema.md. - image-cards / xhs-images / slide-deck / format-markdown: restore the sections that got over-slimmed into references/ (galleries, presets, dimensions, auto-selection, style x layout matrix, title/summary flow) and drop the now-empty shell files. - docs/image-generation-tools.md: note that backend skills themselves (baoyu-imagine, baoyu-image-gen, baoyu-danger-gemini-web) are exempt from the ## Image Generation Tools section requirement. * feat(image-gen): sync Z.AI GLM-Image provider from baoyu-imagine Add Z.AI as a full provider in the deprecated baoyu-image-gen skill so it stays in sync with baoyu-imagine's provider list. - new scripts/providers/zai.ts + zai.test.ts (verbatim port; test factory trimmed to match image-gen's CliArgs shape). - types.ts: "zai" added to Provider union and default_model. - main.ts: rate-limit defaults, provider help text, env var help, --provider validation, loadProviderModule, detectProvider auto-detect chain, getModelForProvider, YAML parser allow-lists. - references/config: Q2e Z.AI model question + zai slot in the preferences schema and batch.provider_limits. Scope is intentionally limited to the Z.AI chain; unrelated drift between image-gen and imagine (OpenAI image-API dialect, aspectRatioSource, imageSizeSource) is left alone. * docs: align inline-convention wording and note backend-skill exemption - docs/user-input-tools.md: fix stale "links here" wording so it matches the inline convention already enforced everywhere else. - CLAUDE.md §Image Generation Tools: inline the backend-skill exemption so readers don't need to cross-reference docs/image-generation-tools.md.
15 KiB
Detailed Workflow Procedures
Step 1: Pre-check
1.0 Detect & Save Reference Images ⚠️ REQUIRED if images provided
Check if user provided reference images. Handle based on input type:
| Input Type | Action |
|---|---|
| Image file path provided | Copy to references/ subdirectory → can use --ref |
| Image in conversation (no path) | ASK user for file path with AskUserQuestion |
| User can't provide path | Extract style/palette verbally → append to prompts (NO frontmatter references) |
CRITICAL: Only add references to prompt frontmatter if files are ACTUALLY SAVED to references/ directory.
If user provides file path:
- Copy to
references/NN-ref-{slug}.png - Create description:
references/NN-ref-{slug}.md - Verify files exist before proceeding
If user can't provide path (extracted verbally):
- Analyze image visually, extract: colors, style, composition
- Create
references/extracted-style.mdwith extracted info - DO NOT add
referencesto prompt frontmatter - Instead, append extracted style/colors directly to prompt text
Description File Format (only when file saved):
---
ref_id: NN
filename: NN-ref-{slug}.png
---
[User's description or auto-generated description]
Verification (only for saved files):
Reference Images Saved:
- 01-ref-{slug}.png ✓ (can use --ref)
- 02-ref-{slug}.png ✓ (can use --ref)
Or for extracted style:
Reference Style Extracted (no file):
- Colors: #E8756D coral, #7ECFC0 mint...
- Style: minimal flat vector, clean lines...
→ Will append to prompt text (not --ref)
1.1 Determine Input Type
| Input | Output Directory | Next |
|---|---|---|
| File path | EXTEND.md default_output_dir (default: imgs-subdir). If not configured, confirm in 1.2. |
→ 1.2 |
| Pasted content | illustrations/{topic-slug}/ |
→ 1.4 |
Backup rule for pasted content: If source.md exists in target directory, rename to source-backup-YYYYMMDD-HHMMSS.md before saving.
1.2-1.4 Configuration (file path input only)
Check preferences and existing state, then ask ALL needed questions in ONE AskUserQuestion call (max 4 questions).
Questions to include (skip if preference exists or not applicable):
| Question | When to Ask | Options |
|---|---|---|
| Output directory | No default_output_dir in EXTEND.md |
{article-dir}/imgs/ (Recommended), {article-dir}/, {article-dir}/illustrations/, illustrations/{topic-slug}/ |
| Existing images | Target dir has .png/.jpg/.webp files |
supplement, overwrite, regenerate |
| Article update | Always (file path input) | update, copy |
Preference Values (if configured, skip asking):
default_output_dir |
Path |
|---|---|
same-dir |
{article-dir}/ |
imgs-subdir |
{article-dir}/imgs/ |
illustrations-subdir |
{article-dir}/illustrations/ |
independent |
illustrations/{topic-slug}/ |
1.5 Load Preferences (EXTEND.md) ⛔ BLOCKING
CRITICAL: If EXTEND.md not found, MUST complete first-time setup before ANY other questions or steps. Do NOT proceed to reference images, do NOT ask about content, do NOT ask about type/style — ONLY complete the preferences setup first.
# macOS, Linux, WSL, Git Bash
test -f .baoyu-skills/baoyu-article-illustrator/EXTEND.md && echo "project"
test -f "${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-article-illustrator/EXTEND.md" && echo "xdg"
test -f "$HOME/.baoyu-skills/baoyu-article-illustrator/EXTEND.md" && echo "user"
# PowerShell (Windows)
if (Test-Path .baoyu-skills/baoyu-article-illustrator/EXTEND.md) { "project" }
$xdg = if ($env:XDG_CONFIG_HOME) { $env:XDG_CONFIG_HOME } else { "$HOME/.config" }
if (Test-Path "$xdg/baoyu-skills/baoyu-article-illustrator/EXTEND.md") { "xdg" }
if (Test-Path "$HOME/.baoyu-skills/baoyu-article-illustrator/EXTEND.md") { "user" }
| Result | Action |
|---|---|
| Found | Read, parse, display summary → Continue |
| Not found | ⛔ BLOCKING: Run first-time setup ONLY (config/first-time-setup.md) → Complete and save EXTEND.md → Then continue |
Supports: Watermark | Preferred type/style | Custom styles | Language | Output directory
Step 2: Setup & Analyze
2.1 Analyze Content
| Analysis | Description |
|---|---|
| Content type | Technical / Tutorial / Methodology / Narrative |
| Illustration purpose | information / visualization / imagination |
| Core arguments | 2-5 main points to visualize |
| Visual opportunities | Positions where illustrations add value |
| Recommended type | Based on content signals and purpose |
| Recommended density | Based on length and complexity |
2.2 Extract Core Arguments
- Main thesis
- Key concepts reader needs
- Comparisons/contrasts
- Framework/model proposed
CRITICAL: If article uses metaphors (e.g., "电锯切西瓜"), do NOT illustrate literally. Visualize the underlying concept.
2.3 Identify Positions
Illustrate:
- Core arguments (REQUIRED)
- Abstract concepts
- Data comparisons
- Processes, workflows
Do NOT Illustrate:
- Metaphors literally
- Decorative scenes
- Generic illustrations
2.4 Analyze Reference Images (if provided in Step 1.0)
For each reference image:
| Analysis | Description |
|---|---|
| Visual characteristics | Style, colors, composition |
| Content/subject | What the reference depicts |
| Suitable positions | Which sections match this reference |
| Style match | Which illustration types/styles align |
| Usage recommendation | direct / style / palette |
| Usage | When to Use |
|---|---|
direct |
Reference matches desired output closely |
style |
Extract visual style characteristics only |
palette |
Extract color scheme only |
Step 3: Confirm Settings ⚠️
Do NOT skip. Use ONE AskUserQuestion call with max 4 questions. Q1, Q2, Q3 are ALL REQUIRED.
Q1: Preset or Type ⚠️ REQUIRED
Based on Step 2 content analysis, recommend a preset first (sets both type & style). Look up style-presets.md "Content Type → Preset Recommendations" table.
- [Recommended preset] — [brief: type + style + why] (Recommended)
- [Alternative preset] — [brief]
- Or choose type manually: infographic / scene / flowchart / comparison / framework / timeline / mixed
If user picks a preset → skip Q3 (type & style both resolved). If user picks a type → Q3 is REQUIRED.
Q2: Density ⚠️ REQUIRED - DO NOT SKIP
- minimal (1-2) - Core concepts only
- balanced (3-5) - Major sections
- per-section - At least 1 per section/chapter (Recommended)
- rich (6+) - Comprehensive coverage
Q3: Style ⚠️ REQUIRED (skip if preset chosen in Q1)
If EXTEND.md has preferred_style:
- [Custom style name + brief description] (Recommended)
- [Top compatible core style 1]
- [Top compatible core style 2]
- Other (see full Style Gallery)
If no preferred_style (present Core Styles first):
- [Best compatible core style] (Recommended)
- [Other compatible core style 1]
- [Other compatible core style 2]
- Other (see full Style Gallery)
Core Styles (simplified selection):
| Core Style | Maps To | Best For |
|---|---|---|
minimal-flat |
notion | General, knowledge sharing, SaaS |
sci-fi |
blueprint | AI, frontier tech, system design |
hand-drawn |
sketch/warm | Relaxed, reflective, casual |
editorial |
editorial | Processes, data, journalism |
scene |
warm/watercolor | Narratives, emotional, lifestyle |
poster |
screen-print | Opinion, editorial, cultural, cinematic |
Style selection based on Type × Style compatibility matrix (styles.md).
In Step 5.1, read styles/<style>.md for visual elements and rendering rules.
Q4: Palette (optional)
If preset did not specify a palette, and the user may benefit from a palette override, offer available palettes:
- Default (use style's built-in colors) (Recommended)
macaron— soft pastel blocks on warm creamwarm— warm earth tones, no cool colorsneon— vibrant neon on dark backgrounds
Skip if: preset already resolved palette, or preferred_palette set in EXTEND.md.
See Palette Gallery in styles.md and full specs in palettes/<palette>.md.
Q5: Image Text Language ⚠️ REQUIRED when article language ≠ EXTEND.md language
Detect article language from content. If different from EXTEND.md language setting, MUST ask:
- Article language (match article content) (Recommended)
- EXTEND.md language (user's general preference)
Skip only if: Article language matches EXTEND.md language, or EXTEND.md has no language setting.
Display Reference Usage (if references detected in Step 1.0)
When presenting outline preview to user, show reference assignments:
Reference Images:
| Ref | Filename | Recommended Usage |
|-----|----------|-------------------|
| 01 | 01-ref-diagram.png | direct → Illustration 1, 3 |
| 02 | 02-ref-chart.png | palette → Illustration 2 |
Step 4: Generate Outline
Save as {output-dir}/outline.md (all paths below are relative to the output directory determined in Step 1.1/1.2):
---
type: infographic
density: balanced
style: blueprint
image_count: 4
references: # Only if references provided
- ref_id: 01
filename: 01-ref-diagram.png
description: "Technical diagram showing system architecture"
- ref_id: 02
filename: 02-ref-chart.png
description: "Color chart with brand palette"
---
## Illustration 1
**Position**: [section] / [paragraph]
**Purpose**: [why this helps]
**Visual Content**: [what to show]
**Type Application**: [how type applies]
**References**: [01] # Optional: list ref_ids used
**Reference Usage**: direct # direct | style | palette
**Filename**: 01-infographic-concept-name.png
## Illustration 2
...
Requirements:
- Each position justified by content needs
- Type applied consistently
- Style reflected in descriptions
- Count matches density
- References assigned based on Step 2.4 analysis
Step 5: Generate Images
5.1 Create Prompts ⛔ BLOCKING
Every illustration MUST have a saved prompt file before generation begins. DO NOT skip this step.
For each illustration in the outline:
- Create prompt file:
{output-dir}/prompts/NN-{type}-{slug}.md - Include YAML frontmatter:
--- illustration_id: 01 type: infographic style: custom-flat-vector --- - Load style specs: Read
styles/<style>.mdfor visual elements, style rules, and rendering instructions - Load palette specs (if palette specified): Read
palettes/<palette>.mdfor colors and background. Palette colors replace the style's default Color Palette. If no palette specified, use the style's built-in colors. - Follow type-specific template from prompt-construction.md, using rendering from style + colors from palette (or style default)
- Prompt quality requirements (all REQUIRED):
Layout: Describe overall composition (grid / radial / hierarchical / left-right / top-down)ZONES: Describe each visual area with specific content, not vague descriptionsLABELS: Use actual numbers, terms, metrics, quotes from the article — NOT generic placeholdersCOLORS: Specify hex codes from palette (or style default) with semantic meaningSTYLE: Describe line treatment, texture, mood, character rendering per style rulesASPECT: Specify ratio (e.g.,16:9)
- Apply defaults: composition requirements, character rendering, text guidelines, watermark
- Backup rule: If prompt file exists, rename to
prompts/NN-{type}-{slug}-backup-YYYYMMDD-HHMMSS.md
Verification ⛔: Before proceeding to 5.2, confirm ALL prompt files exist:
Prompt Files:
- prompts/01-infographic-overview.md ✓
- prompts/02-infographic-distillation.md ✓
...
DO NOT pass ad-hoc inline text to --prompt without first saving prompt files. The generation command should either use --promptfiles prompts/NN-{type}-{slug}.md or read the saved file content for --prompt.
Execution choice:
- If multiple illustrations already have saved prompt files and the task is now plain generation, prefer the chosen backend's batch interface (if it offers one); otherwise generate sequentially
- Use subagents only when each illustration still needs separate prompt rewriting, style exploration, or other per-image reasoning before generation
CRITICAL - References in Frontmatter:
- Only add
referencesfield if files ACTUALLY EXIST inreferences/directory - If style/palette was extracted verbally (no file), append info to prompt BODY instead
- Before writing frontmatter, verify:
test -f references/NN-ref-{slug}.png
5.2 Select Generation Skill
Check available skills. If multiple, ask user.
5.3 Process References ⚠️ REQUIRED if references saved in Step 1.0
DO NOT SKIP if user provided reference images. For each illustration with references:
-
VERIFY files exist first:
test -f references/NN-ref-{slug}.png && echo "exists" || echo "MISSING"- If file MISSING but in frontmatter → ERROR, fix frontmatter or remove references field
- If file exists → proceed with processing
-
Read prompt frontmatter for reference info
-
Process based on usage type:
| Usage | Action | Example |
|---|---|---|
direct |
Add reference path to --ref parameter |
--ref references/01-ref-brand.png |
style |
Analyze reference, append style traits to prompt | "Style: clean lines, gradient backgrounds..." |
palette |
Extract colors from reference, append to prompt | "Colors: #E8756D coral, #7ECFC0 mint..." |
- Check image generation skill capability:
Skill Supports --ref |
Action |
|---|---|
| Yes (e.g., baoyu-imagine with Google) | Pass reference images via --ref |
| No | Convert to text description, append to prompt |
Verification: Before generating, confirm reference processing:
Reference Processing:
- Illustration 1: using 01-ref-brand.png (direct) ✓
- Illustration 2: extracted palette from 02-ref-style.png ✓
5.4 Apply Watermark (if enabled)
Add: Include a subtle watermark "[content]" at [position].
5.5 Generate
- For each illustration:
- Backup rule: If image file exists, rename to
NN-{type}-{slug}-backup-YYYYMMDD-HHMMSS.md - If references with
directusage: include--refparameter - Generate image
- Backup rule: If image file exists, rename to
- After each: "Generated X/N"
- On failure: retry once, then log and continue
Step 6: Finalize
6.1 Update Article
Insert after corresponding paragraph, using path relative to article file:
default_output_dir |
Insert Path |
|---|---|
imgs-subdir |
 |
same-dir |
 |
illustrations-subdir |
 |
independent |
 (relative to cwd) |
Alt text: concise description in article's language.
6.2 Output Summary
Article Illustration Complete!
Article: [path]
Type: [type] | Density: [level] | Style: [style]
Location: [directory]
Images: X/N generated
Positions:
- 01-xxx.png → After "[Section]"
- 02-yyy.png → After "[Section]"
[If failures]
Failed:
- NN-zzz.png: [reason]