edrethardo

Use when adding or modifying DungeonEngine content (items, affixes, weapons, enemies, bosses, enemy roles, skills, materials, levels) or generating assets, and to check known pitfalls/gotchas before touching combat, loot, networking, split-screen, or entity…

Produce or update the CINEMATIC trailer — HUD-free camera-path takes (orbit/glide/follow), the biome tour on deep floors, the seven-biome weapon montage, loot shower, chakram follow-kill and storm orbit, word-by-word title intro and logo-walk outro;…

Produce or update a DungeonEngine trailer — shoot deterministic takes with the --record/--camera/--stage pipeline, generate the gold/red title cards, cut via the EDL scripts, QC frames, and export the Steam master. Trigger for "neuer Trailer", "Trailer…

Produce or update the GAMEPLAY trailer — HUD-on, dungeon-only, honest footage; bot-played takes per beat (frozen-orb opener, class beats, boss trio, chakram storm, couch split, death beat), scan-derived trims, tools/cut_gameplay.sh as the EDL. Trigger for…

Use when you need DungeonEngine internals — the type/constant cheat sheet and MAX_* caps, the per-frame game loop, data lifecycles (hit feedback, entity/projectile/item drop, server-authoritative loot), JSON config schemas…

Use when adding a brand-new enemy to DungeonEngine — generating its voxel mesh and skin via the Python asset tools, wiring the material / mesh registry / enemies.json, and implementing a behavioral gimmick (composed shipped roles + an onHitEffect, or a…

Use when writing or updating CHANGELOG.md for DungeonEngine — collect every commit since the last v* tag, translate them into player-facing entries, and flag compatibility breaks (PROTOCOL_VERSION / SAVE_VERSION / controls.json). Trigger for "write a…

Use when adding a new milestone boss to DungeonEngine — a bosses.json entry (stats, roles, personality, skill, projectile, loot guarantee, floor placement), optionally a dedicated generated mesh + skin + limb config. Trigger for "add a boss", "new floor…

Use when the user asks to create a ticket in chat — "erstelle ein Ticket", "leg ein Ticket an", "schreib das als Ticket auf", "mach daraus ein Ticket", "das sollten wir als Ticket festhalten".

Use when a task type has occurred twice, when the user says "always do it this way", or when following a skill produced a bad result — extract or improve a skill.

Use before starting work, after reaching any working state, at session end, and when the user asks to undo or go back — keeps every change recoverable and the history readable.

Use when the user asks this session to pull or work its Werkbank ticket — "zieh dir ein Ticket", "hol dir dein Ticket", "hast du ein Ticket?", "arbeite dein Ticket ab" — find the open ticket for THIS project on the Werkbank board and work it.

Use when the user asks THIS chat session to receive a project's Werkbank tickets — "registrier dich für dieses Projekt", "melde dich als Session an", "du sollst die Tickets für X bekommen", "register this session" — make the board hand this project's…

Use this skill whenever you work a Werkbank ticket inside this repository — via chat request ("bearbeite WB-n"), via a handover from the board, or as a dispatched run. Single source of truth for the workflow; do not duplicate it elsewhere.

Use when the user asks to work the tickets ("arbeite die Tickets ab", "erledige Ticket WB-3", "was steht an?"), and when the board hands a ticket to this chat — dispatch or visibly work tickets and report results.

Use when the user asks to start, open, stop, or restart the Werkbank board ("starte das Board", "mach das Board auf", "Board neu starten"), or when server code changed and needs a restart.

Use after any user-visible change or architectural decision — update user docs, dev docs, CHANGELOG and the indexes in the same session as the change.

Use when the user requests a new feature or change, before building anything — give an honest, plain-language cost assessment first.

Use at session end, after completing or abandoning any task, or when an approach fails — record what happened in docs/journal/ so no future session re-investigates it.

Use when writing acceptance criteria, when about to report something as verified or done, and when the hard rules call for an adversarial review — every check has to say what it cannot see.

Use when docs/journal/INDEX.md contains the UNINITIALIZED marker — first-run setup; interview the user, set up git, install shared skills, configure the machine.

Use when the user wants this developer-agent setup added to a project they already have, or when they start working on code that lives in another folder — installs the configuration into their repo without breaking what is already there.

Use before starting work, after reaching any working state, at session end, and when the user asks to undo or go back — keeps every change recoverable and the history readable.

Use before writing any logic the user will trust — sums, filters, imports, anything money- or record-shaped — and before claiming that anything works.