Welcome: Building Tools, Experiments, and a Game Project
This blog is a structured public lab notebook documenting my private projects, tools, and experiments — built with heavy use of AI collaboration. It serves three purposes at once: a development log, a place to reflect on what works (and what doesn’t), and a living portfolio of real work in progress.
For years I wanted to build an ambitious game project but never found the right balance of time, scope, and momentum. Modern AI tools changed that equation. Tasks that once took days can now be prototyped in hours, which makes tackling large solo projects far more realistic.
Instead of waiting for a “perfect moment,” I started building — and documenting everything along the way. This blog captures that process in a structured form.
What You’ll Find Here
- Experiments with AI-assisted development workflows
- Tools created to support larger projects
- Technical deep dives and rapid prototypes
- Honest notes about trade-offs, failures, and discoveries
- Progress toward a long-term game project
Posts are intentionally concise and focused on transferable insights rather than exhaustive tutorials.
First Example: Promptomat
Promptomat is a small tool created to reduce friction when working with AI on complex tasks. Writing structured prompts repeatedly is slow and error-prone, especially when projects involve many files and constraints.
The tool generates well-formed prompts from templates, context packs, and task descriptions — essentially acting as a launchpad for consistent AI interactions.
Key ideas behind the tool:
- Reduce cognitive overhead when starting tasks
- Standardize prompt structure for complex projects
- Quickly assemble relevant context
- Keep everything lightweight and dependency-free
Simple mode: Tree-style workflow selection with centered launch button.
Detailed mode: Full configuration with context packs and task inputs.
Built in under two hours using vanilla web technologies, it demonstrates how quickly useful tooling can emerge when development and documentation happen in parallel.
Why Document Publicly?
Writing things down forces clarity. It also creates a timeline of decisions, experiments, and outcomes that would otherwise disappear into commit history.
This blog is also part of an ongoing AI-Experiment: how far can structured collaboration between a human and AI accelerate solo development?
Takeaways
- Large projects become approachable when broken into small, tool-supported steps
- AI is most effective when workflows are structured
- Rapid prototypes often evolve into real infrastructure
- Documentation doubles as both reflection and portfolio
Next
- Explore tools and experiments as they emerge
- Follow progress toward the long-term game project
- Iterate on workflows that make solo development sustainable