Menú
Use when designing, researching, wiring, or documenting Chaos Redux super-events.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Use when designing, implementing, auditing, or fixing Hearts of Iron IV decisions, missions, timed objectives, decision categories, and mission localisation.
Use when designing, implementing, auditing, or fixing Hearts of Iron IV national focus trees.
Use when implementing or updating Chaos Redux events.
Use when expanding Chaos Redux event ideas into detailed specifications before implementation.
Use when creating, sourcing, processing, converting, organizing, wiring, or documenting visual assets for Chaos Redux.
Use when coordinating custom Codex subagents for Chaos Redux implementation, asset production, super-event research, audits, active small patches, planning handoffs, or documentation work.
Basado en la clasificación ocupacional SOC
| name | chaos-redux-super-events |
| description | Use when designing, researching, wiring, or documenting Chaos Redux super-events. |
Use this skill when a Chaos Redux task creates, updates, researches, or wires a super-event.
This skill covers super-event presentation, localisation, quote selection, audio research, image handoff, implementation wiring, and documentation.
General event implementation belongs to chaos-redux-events.
Visual asset sourcing and processing belongs to chaos-redux-event-assets.
A Chaos Redux super-event is a major presentation moment.
It should mark a major event, major escalation, defeat aftermath, or world-end scenario that deserves stronger treatment than a normal popup.
A super-event package must keep these parts aligned:
Do not wire only one part of a super-event. The image, text, quote, audio, event effect, docs, and spreadsheet must agree.
Use this skill for:
chaos-redux-event-assetsDo not use a super-event for every dramatic event. Use it when the campaign moment should feel larger than a normal popup.
chaos-redux-eventsUse chaos-redux-events for the full implementation contract:
chaos-redux-event-assetsUse chaos-redux-event-assets for:
.gfx wiringSuper-event images may be sourced or generated. Prefer generated images for fictional, alternate-history, symbolic, supernatural, high-chaos, or emotionally specific moments. use sourced images when the visual must depict real historical material.
This skill owns:
For actual research work, use the narrow project subagents instead of making one agent research everything at once.
| Need | Spawn |
|---|---|
| Main quote candidates, wording verification, attribution, source confidence, and quote recommendation | chaosx_super_event_quote_researcher |
| Button text, cultural remark, short allusion, slogan, title-like reference, and copyright-risk notes | chaosx_super_event_cultural_remark_researcher |
Audio candidates, license verification, legitimate download, conversion to .ogg, and audio research notes | chaosx_super_event_audio_researcher |
| Real historical, archival, or real-world super-event image that must depict real material | chaosx_asset_source_researcher |
| Fictional, alternate-history, symbolic, supernatural, high-chaos, or emotionally specific generated super-event image | chaosx_generated_event_art |
The main agent owns final localisation, scripted localisation, slot wiring, settings-aware playback wiring, audio id wiring, .gfx image wiring, event trigger wiring, docs alignment, and spreadsheet alignment.
The quote, remark, audio, and image subagents produce research notes, final files where applicable, and handoff notes. They do not edit event files, localisation files, .gfx files, GUI files, sound definition files, or spreadsheet rows unless the parent prompt explicitly expands their scope.
Before wiring a super-event, decide what role it plays.
Common roles:
The role should determine the tone, title, image, quote, and audio.
Do not choose a quote, image, or track because it sounds dramatic in isolation. It must fit the exact super-event role.
Super-event localisation must follow the existing Chaos Redux format.
Example:
chaosx_super_event.1.t: "Undead?"
chaosx_super_event.1.d: "The dead have risen, spreading terror and chaos.\n\nWitnesses describe scenes of horror as reanimated corpses or \"zombies\" began to terrorize cities and rural areas alike. The outbreak's cause appears to be unknown.\n\nAuthorities are urging the public to remain vigilant and avoid contact with anyone exhibiting unusual behavior."
chaosx_super_event.1.a: "Do you like to take a yo-yo for a ride?" # Ironic remark
chaosx_super_event.1.q: "This, then, is how you should pray: 'Our Father in heaven, hallowed be your name.' \n §Y-Matthew 6:9-§!" # An actual quote that fits the situation
Required keys:
.t for title.d for description.a for button text.q for quoteKeep the key numbering aligned with the actual super-event slot.
Do not invent a different localisation pattern unless the existing repo pattern has changed.
A good super-event title should be short, memorable, and specific.
It can be:
Avoid generic titles such as:
Use titles that fit the event's actual identity.
The description should explain the event clearly without turning into a normal event wall of text.
It should:
For secret or uncertain events, use partial information:
Do not reveal a hidden world-ending branch too early.
The button text (.a) should feel like a reaction to the moment.
It may be:
Button text can use a short cultural reference when it fits the super-event.
Possible sources include:
Examples of the kind of source that may be considered include Steely Dan lyrics, a line from The Lord of the Rings, a film line, or a book line, but only if the reference genuinely fits the event.
Use the repository web research workflow from AGENTS.md to verify the exact wording and source of any referenced line.
For modern copyrighted songs, films, books, or games, keep the line very short. Prefer a short fragment, a title-like reference, or a paraphrased allusion when a direct quote would be too long.
Avoid generic button text such as:
The button text should be short enough to fit well in-game.
Document the cultural source in the super-event research note when the button text is a reference.
The quote (.q) should deepen the super-event.
Do not invent quotes.
Do not misattribute quotes.
Do not use a quote unless it fits the specific event.
Use the repository web research workflow from AGENTS.md to find and verify real quotes.
Prefer quotes that can be checked against a reliable source. Primary sources are best. If a primary source is not available, use reputable quote collections, archives, books, speeches, scripture references, or other traceable sources.
Good quote sources can include:
For the main quote, prefer public domain, historical, religious, literary, philosophical, or political sources when possible.
Avoid:
Modern songs, films, books, and games are better suited for the button text or remark (.a) than the main quote (.q).
If a modern cultural line is used as the main quote anyway, it must be very short, and clearly sourced
If attribution is uncertain, mark it uncertain or choose another quote.
Use the repository web research workflow from AGENTS.md for quote research.
Search for quotes by combining the event's core themes with terms such as:
Do not stop at the first quote that sounds good. Find several candidates, compare them, and select the one that best fits the exact super-event role.
For every proposed quote, document:
Use direct quotes sparingly and keep them short enough for the super-event UI.
If the quote is too long, use a shorter excerpt.
Do not alter a quote in a way that changes its meaning.
If a translation is used, state that it is a translation when relevant.
If no strong quote is found, continue searching instead of inventing one.
The button text (.a) can be a meaningful remark or cultural reference.
This is separate from the main quote (.q).
Use the repository web research workflow from AGENTS.md to find and verify cultural references.
Good cultural remark sources can include:
The remark should fit the super-event's tone. It can be ironic, grim, darkly funny, understated, reverent, fatalistic, or bitter.
For modern copyrighted works, keep the direct quote very short. Prefer brief fragments, paraphrased allusions, or title-like references when possible.
For every cultural remark candidate, document:
Do not invent a cultural reference.
Do not misquote a line if presenting it as a direct reference.
Do not use a reference that breaks the tone of the event unless the contrast is intentional.
Use quotes about discovery, doubt, fear, false peace, hidden rot, or the first sign of collapse.
Use quotes about loss of control, failed containment, pride, punishment, betrayal, war, disease, or mass panic.
Use quotes about final judgment, collapse, extinction, fate, prophecy, silence, ruin, or the end of order.
Use quotes about memory, cost, survival, rebuilding, responsibility, or vigilance.
Use quotes about faith, revolution, obedience, sacrifice, destiny, legitimacy, power, or rebirth.
Use quotes about knowledge, arrogance, forbidden inquiry, unintended consequences, or the limits of control.
Super-event audio should make the moment feel distinct.
Core rule: a super-event task is not complete unless its audio is selected, verified, converted, wired, and documented.
Every super-event implementation must include complete audio wiring. Do not leave a completed super-event on default, placeholder, mismatched, wrong-format, or undocumented audio.
Every super-event must have its own unique final track, unique audio id, and unique sound wrapper unless the user explicitly approves a specific reuse before implementation. Do not reuse another super-event's track just because the moments are related.
The final audio should be actual music by default: a musical recording, chant, hymn, orchestral excerpt, song, march, or other track with musical structure. Do not use pure sound effects, drones, pulses, room tone, one-shot stingers, abstract ambience, or texture beds for a super-event unless the user explicitly asks for non-musical audio and the exception is documented.
Never create or accept a super-event track from generated test tones, primitive waveforms, signal-generator output, metronome clicks, generated beeps, simple oscillator layers, noise beds, or quick local synthesis. This includes sine, square, triangle, sawtooth, and similar waveforms, even when mixed with noise or effects. If no real licensed track is available, stop and report the blocker instead of manufacturing a cue.
Never describe a final cue with placeholder provenance such as "restored legacy", "legacy audio package", "repository history", or similar implementation-history wording in player-facing or attribution documentation. The final music table and audio docs must name the actual source title, creator or composer, performer or recording source when known, source URL, license, and duration. Use attribution status verified only after the title and creator/composer are identified and the source/license have been checked.
The final music should be chosen intentionally.
Before looking outside the repository, check whether an approved suitable track already exists in the repo. Inspect:
music/*.oggsound/*.wavmusic/chaosx_super_event_music.assetmusic/chaosx_super_event_music.txtsound/chaosx_sound.assetmusic/chaosx_music_track_list.htmlUse an existing track only when its source, license, duration, and intended use are already documented well enough to trust, and when its tone fits the specific super-event role and pacing.
If no approved suitable track exists, search the internet using the repository web research workflow from AGENTS.md. Do not use unapproved web browsing tools for this repo.
Find music that fits the exact super-event tone, role, and pacing. Prefer tracks between 1 and 2 minutes long. If a better track falls outside that range, document the exception before use and trim the final in-game file to 2 minutes or less unless the user explicitly approves a longer final track.
Prefer:
Reject:
For each candidate and final selected track, verify and document:
Check composition rights and recording rights separately.
A public domain composition does not automatically make a recording public domain.
If the license is unclear, mark it unsuitable and find another option. Do not wire uncertain audio into a completed super-event.
Do not claim a track is public domain without checking.
For every super-event audio package:
music/source/ or music/super_events/; those folders are not persistent source archives..ogg.
Game-ready super-event .ogg files must be 44.1 kHz / 44100 Hz..ogg in the correct event-scoped music folder: music/<event_id>_<event_slug>/super_event_<super_event_id>_<super_event_name>.ogg. Shared defaults or non-event music may remain in music/ only when they are intentionally shared and documented.music/chaosx_super_event_music.asset definitions for every dynamic volume variant that the current audio helper can call.music/chaosx_super_event_music.txt so the station includes a representative entry for every final super-event track.sound/chaosx_sound.asset sound and soundeffect definitions for sound-channel playback. If a sound-channel WAV is used for the same super-event, mirror the folder and filename structure under sound/<event_id>_<event_slug>/super_event_<super_event_id>_<super_event_name>.wav.global.current_super_event_audio_id and the settings-aware playback helper.music/chaosx_music_track_list.html. every super-event track must have a row in the HTML music table, and that row must list the super-event id using the track. If a user-approved reuse exists, document every id in the row and explain the approval in the audio docs.Use the existing Chaos Redux settings-aware playback helper. Do not bypass it.
For every suitable track, propose practical editing notes.
Possible notes:
Do not perform destructive edits without preserving the original source file.
Document any edited derivative file.
When implementing audio, follow the existing Chaos Redux audio pattern.
The implementation should keep these aligned:
global.current_super_event_audio_idEvery super-event must have a specific audio id and a unique final track. Shared audio ids or shared tracks are allowed only when the user explicitly approved the exact reuse.
Use the settings-aware playback helper rather than bypassing it.
Fallbacks are not allowed without discussing them with the user. If final audio is unavailable, stop and explain the blocker instead of silently leaving default or placeholder audio.
Always update music/chaosx_music_track_list.html for every super-event track. Every final super-event track must have a row in that table, and the row must show the super-event ID using the track. User-approved reuse must list every affected ID and the audio docs must explain why reuse was approved.
Update any additional music or audio documentation used by the repo.
For each super-event audio package, document:
.ogg path.wav path, when usedmusic/chaosx_music_track_list.html row with the final track and super-event ID or IDsIf metadata cannot identify the author, title, source, license, or duration, and the user did not provide it, reject the track or ask the user for the missing information instead of guessing.
Before finishing any super-event task, confirm:
.ogg exists.ogg is 44.1 kHz / 44100 Hz.oggmusic/chaosx_super_event_music.txt includes the final super-event track or a representative helper song id for that trackmusic/chaosx_music_track_list.html documents every super-event track and shows the super-event ID or IDs using it.ogg path, sound definition id, and super-event useSuper-event images are handled through chaos-redux-event-assets.
Default rule:
chaos-redux-event-assets and the official $imagegen workflow for generated imagesThe super-event skill should define the image direction:
The asset skill handles:
.gfx wiringWhen wiring a super-event, choose the slot intentionally.
Make sure the implementation:
global.current_super_event_audio_idGetSuperEventImage for the slot's sprite and the title/description/quote/remark getters.gfx fileDo not reuse a slot accidentally.
Do not let two unrelated super-events point to the same current image, text, or audio unless the reuse is intentional and documented.
World-end super-events need stricter alignment.
When a super-event represents a world-end scenario:
chaos-redux-eventsA world-end super-event should feel like an end-state, not a normal escalation.
Use defeat aftermath super-events only when the defeated threat was global or near-global, long enough, and costly enough to reshape the campaign.
The super-event should communicate:
Quotes and music should usually feel reflective, not triumphant without cost.
The event documentation should explain:
Do not leave the docs saying only "super-event added."
For every super-event research package, create or update a markdown note.
Recommended path:
docs/super_events/<event_id>_<event_slug>_super_event_research.md
The note should include:
.ogg pathImprovement addenda can propose new super-events, but a super-event should still mark a real campaign threshold. Do not add one just because a route has a strong image. Use one when a formable changes regional order, a hidden route becomes public, a scripted GUI mechanic reaches a global milestone, a league or world threat emerges, or a defeat aftermath reshapes the campaign.
For formables, the super-event should reflect the formation method. A negotiated federation, violent restoration, occult revival, imperial proclamation, anti-colonial congress, and puppet-backed union should not share the same tone. The title, quote, image, audio, remark, and trigger should reveal the route identity.
Animated portraits or animated scripted GUI assets can support a super-event-adjacent moment, but they are not replacements for the super-event package. The super-event still needs aligned text, quote, image, audio, trigger, docs, etc.
Before closing a super-event task, confirm:
AGENTS.md was used to find and verify real quote candidates.chaos-redux-event-assets.AGENTS.md was used..ogg exists in the correct folder..ogg.music/chaosx_super_event_music.txt includes the final super-event track or a representative helper song id for that track.global.current_super_event_audio_id is set correctly.GetSuperEventImage. otherwise the slot can show default art while the text/audio work.