Growing Up Fast: What Changed in Promptomat Over the Last 3 Days
Over the last few days, Promptomat took a meaningful step from “working prototype” toward a more scalable product foundation.
We didn’t just add features. We started shaping how future features can land faster, cleaner, and with less friction.
The Big Theme: Growth Through Structure
We’re building for the next phase, not just the next commit.
A lot of effort went into refactoring and internal organization. That work may feel invisible from the outside, but it is exactly what makes rapid feature development possible without accumulating chaos.
1) Refactoring Into Clearer Modules
Recent commits focused heavily on splitting responsibilities and reducing monolithic UI logic.
- Core utilities and services were separated more clearly
- UI pieces were reorganized into focused modules and components
- Manager-level structure improved for state, workflow handling, and orchestration logic
This is the kind of work that pays compound interest: faster iteration, safer changes, and easier onboarding for future contributors — human or AI.
2) Major UX Rework (One of Many to Follow)
This sprint also included a major UX rework, with more planned next. The goal was to expand capability while keeping interaction quality under control.
- Workflow UI improvements
- Better helper behavior and interaction quality
- Memory/history-facing UX improvements
- Stronger project and workflow configuration handling
In short: more power, better ergonomics.
3) Early Orchestration Experiments
One of the most important directional bets right now is orchestration.
We’ve started experimenting with orchestration flows and manager-level hooks that prepare the app for richer multi-step guidance and coordination patterns. It’s still evolving, but the groundwork is now clearly visible in both architecture and commit trail.
4) Meta-Layer Maturity
A notable shift: we invested in internal project intelligence via a .meta/ layer.
That includes architecture maps, rules, progress docs, and instruction templates. It’s behind-the-scenes work, but it directly improves delivery quality by making intent and constraints explicit.
5) A Tiny Hidden Gimmick 👀
There’s also a small playful touch in the recent changes. We won’t spoil it yet, but if you pay attention at startup, you might notice Promptomat getting a bit more personality as it scales.
Click image to enlarge →
What This Means Going Forward
- Cleaner structure
- Broader capabilities
- Early orchestration groundwork
- Better internal documentation and process discipline
These last three days weren’t about one flashy feature drop. They were about upgrading the project’s growth engine.
Side note: Codex sandbox workflows continue to be extremely useful for this kind of fast-moving project work — keeping the IDE cleaner while still enabling disciplined execution, validation, and iteration loops.
This is how small projects become durable systems. More soon.