tinqs/blog
5
0
Fork 0
Code Pull Requests Actions Packages Projects Releases Wiki Activity Issues

Add blog post: Why Voice Is the Missing Input for Game Development

Browse Source 
Voice-to-agent pipelines for real-time bug reporting during playtesting — how speaking bugs while looking at the screen collapses the gap between noticing and tracking.
This commit is contained in:
ozan
2026-06-10 21:43:27 +01:00
parent 56795b680f
commit aaa788b29f
3 changed files with 462 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
index.html
+8 -1
View File
@@ -163,7 +163,14 @@
<a href="pi-flow-native-brain" class="blog-card">
<span class="blog-card__date">4 June 2026</span>
<h2 class="blog-card__title">How Pi Agents Build, Test, and Ship Game Code with Oracle-Backed Flows</h2>
<p class="blog-card__excerpt">We type a slash command, agents fan out through five oracle gates, the game-builder fixes 19 red tests while vision judges check the live game — and it all runs as one autonomous flow.</p>
<p class="blog-card__excerpt">A flow spawns, agents fan out through five oracle gates, the game-builder fixes 19 red tests while vision judges check the live game — and it all runs as one autonomous flow.</p>
<span class="blog-card__read">Read &rarr;</span>
</a>
<a href="voice-missing-input-game-dev" class="blog-card">
<span class="blog-card__date">10 June 2026</span>
<h2 class="blog-card__title">Why Voice Is the Missing Input for Game Development</h2>
<p class="blog-card__excerpt">Speaking a bug while looking at the screen beats typing it from memory ten minutes later. Here's how voice-to-agent pipelines work, why game dev is the ideal use case, and what changes when you stop typing bug reports.</p>
<span class="blog-card__read">Read &rarr;</span>
</a>
Before
After