DesignAutomation&Plugins

Context

Creative production often breaks down in the gap between the idea and the repeated execution. A concept may be clear, but teams lose time resizing, versioning, renaming, exporting, laying out, checking consistency, or repeating the same manual steps across multiple files. Daha's plugin and automation work began from inside that reality — not as abstract software development, but as a practical response to production friction he experienced as a hands-on creative.

The Challenge

The challenge was to translate creative pain points into usable tools. A plugin for a designer cannot feel like engineering software; it has to be simple, fast, familiar, and shaped around the way creative people actually work under deadlines. The tools needed to reduce repetition without taking control away from the maker.

The Role

Daha identified workflow gaps through direct creative practice, defined the tool logic, shaped the interface behavior, and built plugin concepts across After Effects, InDesign, and Illustrator workflows. His role connected creative direction, production knowledge, UX thinking, and automation — turning repeated manual actions into reusable systems.

The Insight

The key insight is that creative quality is often affected by invisible workflow pressure. When a designer is forced to spend energy on repetitive technical tasks, less energy remains for judgment, refinement, and storytelling. Better tools do not replace creativity; they protect it.

The Strategy

The strategy was to build tools from the maker's point of view. Instead of forcing a designer into a complicated software mindset, the plugins should feel like natural extensions of the creative process: clear controls, direct outcomes, fewer clicks, safer repetition, and less room for avoidable production errors.

The Execution

The work covers a set of small, single-purpose plugins and scripts for Adobe After Effects, InDesign, and Illustrator, each aimed at one recurring production step — resizing and re-exporting layouts across formats, batch renaming and version-tracking files, and checking consistency across a set of assets. Each tool was scoped to fit inside a live production pipeline rather than built as a standalone product: small enough to trust, fast enough to use without breaking focus, and shaped directly from where a deadline actually slows down.