Portfolio — Rev. 2026.09 · Available for the right brief

Emile Harmel, creative technologist and senior engineer: A thousand frames.Ten on brand.I build the filter.

Emile Harmel — creative technologist and senior TypeScript engineer. Twenty years of judging a page, now compiled into agent pipelines: image, voice and video that stay on brand because code checks them, not because somebody hoped.

Emile Harmel — creative technologist and senior TypeScript engineer. Agent pipelines where code, not hope, decides what ships.

Document
Portfolio — Emile Harmel
Discipline
Creative Technologist · Senior Engineer
Base
Graz, Austria · CET
Date
2026-09
Sheet
01 / 05
§01.1

Latest work

Two products, both live

AI made everything faster. It didn’t make anyone’s taste better — that part has to be built in on purpose, and building it in is what I do. Two products where I did it most recently:

  • Nutrons hub hero: four nut superheroes surf leaves past the World Tree of Nu-Terra.

    Sheet 02 / 05Awesome Nuts GmbH · 2026

    Nutrons

    Brand hub · web game · on-brand image pipeline

    A comic-book snack brand with a world behind every pack. I designed and built the hub and its game, then codified the brand so generated art stays on model.

    Live — portal.getnutrons.com

  • Two clay monsters, a ramp and building blocks: a frame from “Learning Shapes”, a film the MonstoryX pipeline made.

    Sheet 03 / 05Co-founder & chief technologist · 2024 — present

    MonstoryX

    Language game · teacher platform · video agents

    Children speak, monsters listen. Teachers write spoken quests with an AI co-author and approve every word; a multi-agent pipeline films each mission.

    Web Summit Lisbon 2026 · Impact startup

Before these: Mazda Germany’s online sales platform, gematik’s national patient record, AR for Nestlé Wagner, a talking puppet for Super RTL. All work, 2016 — 2026 →

§01.2

Method

How the work gets made
  1. Code decides what ships

    Every model output is followed by something deterministic — a linter, a compiler, a judge with a calibrated threshold. A failure goes back to the model once, with the exact violations.

  2. Canon as a package

    A brand compiled into the machine rather than briefed at it. Sheets, style register, camera grammar and colour, hash-locked to reference plates by tests. When the brand changes, the tests fail — which is the point.

  3. No agent grades its own work

    Owners write, critics prove. The agent that builds never grades it: a critic with fresh context does, blind, against the bar the spec set. I set the architecture, review the diffs and merge what ships. The whole rig has a sheet of its own.

  4. Prototypes that are already code

    FigJam discovery → generative exploration → a Figma design system via MCP → a deployed prototype. The client reviews the thing, not a picture of it.

  5. Make it the team’s

    A capability that lives in one person’s head is a bottleneck with good taste. Mine ships as rules, eval suites and installable plugins — plus coaching until a colleague no longer needs me.

Sheet 04 / 05 → Orchestration: how the agent team runs

Contact — open application, always

Send me the brief.I’ll send back receipts.

Base
Graz, Austria · CET — an hour ahead of London
Languages
English (mother tongue) · German (Grundkenntnisse, improving)
CV — Senior Engineer ↓CV — Creative Technologist ↓

Same person, two lenses. Both are A4 drawing sheets in the Blueprint theme.

One design system, five themes. The CV wears the first, the letters the second. The other three are here — try them, the whole site follows.