visionik.md

I use my "spare time" to write code in a powerful new programming language:

English/Markdown

I half-jokingly posted on X:

For example:

1. Data.mom (it's not public yet) - someone's gotta serve these tables… might as well be .mom. Built a Go+Gin+HTMX+Bootstrap web application foundation (now called VisionGo) with OAuth single-sign-on, WebAuthn support, header/body/footer templates, account menu, light/dark mode, theming support, a repository interface for required data, and a repository implementation for SQLite and Postgres. From there built a full app to do what data.mom does. Which I shouldn't talk about yet (until patents are filed), but it's slick as hell. Then added openTelemetry to Data.mom using..
2. Ago https://vis.bot/g/ago - my first attempt at an ideal system to help agentic coders analyze app issues and performance with openTelemetry in spans and formats agents better understand. More to come in the future; the latest release isn't on Github yet. I pivoted the "help agents code better" with... Warping, which I'll describe later, below. Until then I realized I also needed...
3. https://vis.bot/g/vcontext - my attempt to advance the short (to-do), medium (plans) , and long-term (playbooks) memory of agentic coding systems; to optimize for parallel-agent development, including parallel poly-agents; and create a standard format for todo/plans/playbooks and PRD and SPECIFICATION files that lead to plans and to-do lists.
   
   User Interview → PRD → Specification → Plans → To-Do lists → Playbooks
   
   Then Playbooks become lessons-learned to improve all of the above.
   
   vContext supports an enhanced, token-conserving, JSON format called TRON, so I wrote...
4. https://vis.bot/g/trongo - a Go library that is an exact duplicate of the Go system JSON library, but with full TRON support.
5. Then circled back to use the VisionGo framework to build VisionCal, my own calendar client. Why? I've always wanted a calendar client that works like Superhuman Email. So I built one. Just for me. For now.
   
   About this time I discovered the amazing https://clawdbot.com and started writing various things for it, including:
6. https://vis.bot/g/ouracli - a command line interface to pull health & sleep data from my Oura ring. ClawdBot includes this in my morning briefing and runs a week-on-week analysis of trends and changes.
7. https://vis.bot/g/dashdash - more spec work. Enable CLI's like ouracli to explain how AI's can use them with --ai-help. It's grown to be about other forms of usage-discovery.
8. Adding an Agent Client Protocol interface to ClawdBot. Because Discord, Slack, Telegram, and WhatsApp just were not enough. I need ClawdBot in my IDE and working with Toad. Now in early testing in new ClawdBot versions https://github.com/clawdbot/clawdbot/pull/122
9. https://github.com/steipete/gogcli/pull/30 - added support for comments to gog, the very handy CLI for Google mail/docs/calendar/drive/chat/etc.
10. https://github.com/steipete/gogcli/pull/53 - also fixed gog support for recurring calendar events.
11. Switching direction for a bit, built https://vis.bot/g/uptop - because we don't have enough top variations. Well, at least none like uptop.: Completely modular/plug-in based, built in Python to support easy plug-in authoring but mostly so I could use the beautiful Textual TUI. It's also completely useable as a CLI or a Prometheus collector. Ported to Mojo + Python for performance. This is the foundation of something else I've wanted to build. More to come.
12. Built 5 small but sexy websites in one weekend, all with modern vibes and the just-as-modern stack of TypeScript, React, Next.js, Shadcn/ui, and Cloudflare Pages/Workers. https://dronescale.com, https://entrenext.com, https://reminderbot.ai, https://visionik.com, and https://zendicate.com.
13. Built https://vis.bot/g/fizz and https://vis.bot/g/libfizz to have a sane CLI for the great https://fizzy.do ... there is was a CLI already (and a few new ones since I wrote this one) but I didn't like it.
14. Built https://vis.bot/g/mstodo to have a CLI for Microsoft To Do. I don't use many Microsoft products, but I loved Wunderlist; which Microsoft bought and rebuilt as MS To Do.
15. Building https://vis.bot/g/mogcli to implement a Microsoft ecosystem equivalent to gog. It's based on what I learned building mstodo and implements a CLI for Microsoft Mail, Calendar, Contacts, OneDrive, Office365, SharePoint, Teams, and more.
16. Building a real-time voice & video interface for ClawdBot. Not public yet. Built on WebRTC, works great from any browser. Does some things I've never seen before, and some things I haven't seen in a long time.
    Looking forward to showing this off.
17. Building https://vis.bot/g/tronpy to complete the trifecta of TRON format libraries. This is a work-in-progress that I'm building with a new coding tool + warping.
18. Analyzed 10 years of emails and text messages to build a markdown file that "teaches" an AI how to write like me.
19. Built jtk. Which, alas, I also shouldn't talk about yet as patents are underway.
20. And finally, built Warping - now on its second BETA release, Warping is a layered framework for AI-assisted development that gives AI agents consistent rules to follow. Instead of re-explaining your preferences every chat, you write them once in markdown files that stack. It's basically AGENTS.md on steroids — structured, composable, and designed for AI agents to actually follow consistently. And it works. Really, really well. Insanely well. Sometimes frighteningly well.
    
    Warping was originally built just for me and for the amazing Warp Agentic Development Enviornment, a combination a great terminal client + a great agentic coder + the start of a decent IDE. It's now in use by an alpha-testing group of 12 developers, and it's working across Warp, Claude, OpenCode, ClawdBot, and more. I use Warping to build new releases of Warping. It's not limited to code: I used Warping to build the vContext and dashdash specifications.
    

Everything above was built by agentic coding. Everything after #3 was built with my Warping framework. Warping takes everything I've learned about the technical and business best-practices of coding and building products and codifies it into markdown files.

visionik is my screen-name/gamer-name/nick-name/alias/handle/gamertag.

Warping is visionik.md

And to be clear, when I say everything was built agentic, almost all with warping/visionik.md ... I mean I didn't write a single line of the code or copy in any of these projects. Not one. It's all beautiful output, with beautiful interfaces (GUI, TUI, API, or CLI), and 75%+ unit test coverage. I'm generating about 1200 lines of test code for every 1000 lines of working code.

All while my main job is Zendicate, where we have signed term sheets to fund over $12m in deals in the next 3 months. My second job is at Sighthound, where we are building the 5th generation of our computer vision hardware and the 8th generation of our computer vision software. My 3rd job is at DroneScale, and my 4th is a new startup in stealth mode.

TL;DR - all 20 of these projects were built in the gaps between my "real jobs" over the last 3 months. I didn't write a single line of "code'. Yet it's probably the best code I've written in my career. No slop, no mess, and more testing (unit, fuzzing, and integration) than I've ever had in personal or professional products.

Everything is different now.

Ignore AI at your professional peril.

I estimate that as of today I am at ~12x my 2024 productivity level. I believe I can get to 100x by the end of the year. I'll be using this page to update that journey.

PS: while writing this article I got tired of typing "long" https://github.com/visionik/project URL's. So I used Warp+Warping to register vis.bot and build a github URL shortener for my projects in the form vis.bot/g/project-name. Took about 10 minutes total.