Overview
It’s been a while, but here’s an update on Mirori-HP. The previous one is here↓
…Wait, 2024?! I really left it alone for a while. Well, you could say it’s been stable without bugs.
Highlights This Time (a.k.a. Release Notes)
I suddenly felt like writing a really long article. And for that, I wanted long tables of contents (called TOC) to be properly viewable. So now, even long TOCs can be scrolled. This article↓ shows it.
On mobile UI, the table of contents isn’t shown. Just so you know.
I also wanted to write math formulas. So I introduced the KaTeX library to render LaTeX-style formulas. This article↓ uses it.
I’m glad the formulas can now be rendered nicely. On the UI side, if the screen width is narrow, the formulas may overflow. Well… it is what it is.
That’s All
Also, I’ve started introducing AI coding agents into my development workflow, following the current trend. This field evolves week by week, and even if I write “the strongest way to use the best agent I found!”, it would already be outdated the next week, so I don’t feel like explaining my setup in detail. Roughly, I use it like this:
-
I give a prompt like this to Codex↓
-
What I want to implement in Mirori-HP this time is “...”.
- Let Codex subagent and Claude Code subagent review each other alternately and turn the requirements into a design note.
- Let Codex subagent and Claude Code subagent review each other alternately and implement based on the design note.
- When finished, commit the implementation and notify me after creating a pull request.
- When Codex says “I’ve created a pull request,” I check it, merge it, and release. DONE!
How far, and in what way, will AI coding agents evolve from here?
