Menu
Use when a Hearts of Iron IV mod task needs sourced quotes, cultural remarks, slogans, title-like references, public-domain text, licensed music, sound cues, or audio source documentation.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Use only when the selected HOI4 portrait provider is the Comfy Cloud MCP route.
Use only when the selected HOI4 portrait provider is a configured loopback ComfyUI installation.
Use only when the selected HOI4 portrait provider is an existing RunPod ComfyUI workspace.
Use when creating, sourcing, processing, converting, organizing, wiring, or documenting visual assets for a Hearts of Iron IV mod.
Use for the provider-neutral HOI4 portrait source, prompt, archive, validation, and runtime handoff contract.
Use when coordinating custom Codex subagents for HOI4 mod implementation, asset production, text and audio research, audits, active small patches, planning handoffs, or documentation work.
| name | hoi4-text-audio-research |
| description | Use when a Hearts of Iron IV mod task needs sourced quotes, cultural remarks, slogans, title-like references, public-domain text, licensed music, sound cues, or audio source documentation. |
Use this skill when a HOI4 modding task needs researched text or audio for any feature, event, focus route, decision category, custom GUI, loading screen, main menu change, news item, report image package, achievement theme, country reveal, formable proclamation, or other presentation surface.
This skill is optional. Most features do not need quote, remark, or audio research. Use it only when the user, specification, asset prompt, implementation task, or documentation target asks for sourced wording, cultural reference checks, or music and audio licensing.
This skill does not implement gameplay code. It does not wire sound definitions, GUI, event files, localisation files, focus files, decision files, or .gfx files unless the parent explicitly grants that scope. Its purpose is to produce reliable source notes, recommended text candidates, usable audio candidates, and handoff material that the main agent can implement.
General event implementation belongs to hoi4-events. Visual asset sourcing and processing belongs to hoi4-feature-assets. Animated visual work belongs to hoi4-frame-animation.
Text and audio research prevents two common failures:
A complete research handoff should let the implementation agent know what is safe to use, what is uncertain, what is unsuitable, and what still needs approval.
Use this skill for:
Do not use this skill just to make ordinary localisation sound dramatic. If the task only needs normal event text, focus text, decision text, or tooltips, write those through the owning implementation skill.
Use the narrow research subagents when actual research work is large enough to split out.
| Need | Spawn |
|---|---|
| Quote candidates, exact wording checks, attribution confidence, public-domain text, cultural remarks, slogans, allusions, and short references | hoi4_quote_remark_researcher |
| Music or audio candidates, including presentation cues, license checks, legitimate downloads, conversion notes, and audio handoff notes | hoi4_audio_researcher |
The main agent owns final localisation, final sound wiring, final .gfx or .gui wiring, final documentation integration, and completion claims. Research subagents return evidence and recommendations. They do not make final implementation claims.
Use quote or remark research when a feature needs any of these:
Do not invent quotes. Do not invent slogans and present them as real. Do not use unsourced quote-site wording as if it were reliable.
If the source matters, verify it.
A quote should deepen the feature's specific role. It should not be chosen only because it sounds severe, clever, grim, or famous.
Good quote sources can include:
Avoid:
If attribution is uncertain, mark it uncertain or choose another quote. Do not hide uncertainty.
Start with the feature role and the tone needed. Search for sources that match the exact role instead of only the general topic.
Search terms can combine the feature's themes with:
Do not stop at the first usable line. Find several candidates, compare them, and recommend the best one.
For each considered quote, record:
Use direct quotes sparingly. Keep excerpts short enough for the intended UI surface.
If a translation is used, state that it is a translation when relevant. Do not alter a quote in a way that changes its meaning.
A cultural remark is a short source-aware reaction or allusion. It can be useful for an event option, decision button, achievement hint, custom GUI button, loading quote, presentation card, or other visible surface.
Possible sources include:
The remark should fit the feature's tone. It can be ironic, grim, understated, reverent, fatalistic, bitter, bureaucratic, absurd, or plain, depending on the feature.
For modern copyrighted works, keep any direct quote very short. Prefer brief fragments, title-like references, or paraphrased allusions when a direct quote would create risk.
Do not use long modern song lyrics, film dialogue, book dialogue, or game dialogue.
Do not misquote a line if presenting it as a direct reference.
For every remark candidate, record:
A title-like reference can borrow the shape of a source without copying a long passage. It can work for feature names, route labels, decision categories, achievement working labels, or custom GUI panels.
Use it carefully.
A title-like reference should:
Document the source and whether the phrase is a direct title, adapted title, public-domain source, common phrase, or modern allusion.
Prefer sources in this order:
A quote from an unsourced quote site is not verified. Use it only to find a better source.
For modern cultural references, use official lyrics pages, official scripts, publisher excerpts, rights holder pages, reputable databases, or short clips only as needed to verify exact wording. Keep copyright limits in mind.
Do not reproduce long copyrighted material.
For modern songs, films, games, books, and other protected works:
For public-domain works, still keep quotes concise for UI readability.
If the user requests a long copyrighted passage, do not provide it. Provide a short compliant excerpt, a paraphrase, or a source note instead.
Audio research is needed when a mod feature requires a final music track, cue, loop, sound wrapper, menu track, custom event cue, presentation reveal or aftermath cue, custom GUI sound, loading music, victory cue, defeat cue, route reveal cue, or other audio asset.
The goal is not to find something that sounds vaguely dramatic. The goal is to find legally usable audio that fits the exact feature role and can be documented.
A complete audio task should identify:
Before looking outside the repository, check whether the parent identified an approved existing audio folder, track list, manifest, or music documentation file. Do not browse the entire repo unless the parent asks for reuse checks.
Use an existing track only when:
If no approved suitable track exists, search for audio with clear rights.
Prefer:
Reject:
Composition rights and recording rights are separate. A public-domain composition does not automatically make a modern recording public domain.
Audio length depends on the feature.
Common shapes:
Choose audio by role:
Avoid tracks that sound generally dramatic but do not fit the requested role.
For every candidate and final selected track, document:
If license, title, creator, source, or duration cannot be identified, mark the track unsuitable or blocked unless the user provides the missing information.
Do not call an audio package complete while source or license is unclear.
Preserve original downloaded source files when practical.
Possible editing notes:
Do not make destructive edits without preserving the source file.
For HOI4 audio, final .ogg files commonly need stable sample rate and format. Use repository and vanilla precedents for exact format expectations. When a repository has an existing audio conversion workflow, follow it. If no workflow exists, provide a clear conversion recommendation and mark any uncertainty.
The main agent owns final sound wiring. A research handoff should provide enough data to wire without guessing.
Include when useful:
.ogg pathDo not edit sound definitions unless the parent explicitly grants that scope.
A compact research note should usually include:
# <feature_slug> text and audio research
## Scope
- Feature:
- Requested surface:
- Owner:
- Research question:
## Quote candidates
| Candidate | Source | Confidence | Fit | Risk |
| --- | --- | --- | --- | --- |
## Selected quote
- Text:
- Author or speaker:
- Source:
- Date or period:
- Source URL or path:
- Confidence:
- Copyright or public-domain note:
- Fit note:
## Cultural remark candidates
| Candidate | Source | Type | Risk | Fit |
| --- | --- | --- | --- | --- |
## Selected remark
- Text or allusion:
- Source:
- Type:
- Copyright risk:
- Fit note:
## Audio candidates
| Track | Creator | Source | License | Duration | Fit | Status |
| --- | --- | --- | --- | --- | --- | --- |
## Selected audio
- Title:
- Creator or composer:
- Performer or recording source:
- Source URL or path:
- License:
- Duration:
- Source file:
- Final converted file:
- Suggested id:
- Editing notes:
- Fit note:
- Uncertainty:
## Implementation handoff
- Localisation owner:
- Sound owner:
- Asset owner:
- Documentation owner:
- Blockers:
Use only the sections that fit the actual task. Do not create empty research tables for things the feature does not need.
Sourced quote, remark, or audio research task is complete when the main agent receives:
Do not treat an unverified quote, uncertain audio license, placeholder track, unsourced cultural reference, or missing attribution as complete.
When the installed hoi4-super-events workflow is selected, bind every research handoff to the stable registration ID, presentation role, owning caller, accepted tone, and permanent research note. Compare several quote and response candidates, verify exact wording and attribution, keep modern copyrighted excerpts short, record uncertainty, and reject dramatic language that does not fit the exact reveal, victory, defeat, aftermath, or ending.
Audio remains optional unless the accepted project design explicitly requires it. A required cue needs verified composition and recording rights, a legitimate source, conversion through the project's established workflow, a unique project-scoped sound ID unless reuse was approved, playback and close behavior, and durable documentation. Never invent a format, duration, helper, path, command, license, placeholder cue, generated test tone, or primitive waveform substitute.