Vibe Coding to Production, VS Code Markdown Editor Extension
My resolution for 2025 was to vibe code something to production, and release it to WWW. I was hoping I will do a Web or Mobile App, but turns out it's a VS Code Extension, solving a common pain of editing markdown files in VS Code, Cursor, Anti Gravity, Windsurf etc.
Is it 100% Vibe Coded?
Yes, for sure!
I never knew how to create VS Code Extension, the first prompt did it all.
I know JavaScript and Typescript basics because of my Angular & Salesforce LWC background, but not very hands on in coding since past few years, I do it on side sometimes for fun, I am CEO of a Salesforce consultancy.
What helped me most was PLAN mode in Claude Code, Cursor and AntiGravity, I use that to create detailed MD plans to review how feature will look like in extension UX/wireframes and some integration points with code, forex: this mermaid plan
This plan mode helped me vibe code a detailed plan, and avoided error loops to a good extent, as most of the time in vibe coding was in vibe planning. I ensured, to carefully read the plan before telling LLM to build it. Actually, after this much planning, the role of LLM was trivial, as everything was spec-ed out.
This also helped me create detailed on demand context of what I did with a feature in the past, I asked LLMs to refer these plans before making code changes.
But the 80:20 rule applies, after 15 mins of vibe coding started the real challenge to ensure more features can be stacked on top of basic Markdown Editing, some features took 8–12 hours in vibe planning/coding and testing takes a lot of time.
Why another Markdown Editor?
VS Code has mostly Preview extensions or Free extension which are behind paywall for features.
With vibe coding, I was able to build v1 of this extension in < 15 mins, including testing it for the 1st time on VS Code.
Thus the value or charm of code as an IP is gone in AI era, and I decoded to open source it, so that anyone with vibe to code via AI can keep the momentum and continue to build the extension.
What is unique about this Markdown Editor?
Watch following video for a quick demo
Top Class Image support
On spot renaming of images, no more juggling in workspace/finder/explorer to find image file, change name and edit Markdown code.
On spot resizing of images, which is a pretty often use case, when you get a huge screenshot in MBs, which can fill up your repo space really quick (not ideal), and makes rendering of README and other public documentation slow, bad for SEO too.
The in place resizing starts when you add an image, it suggests the size is huge, and suggest a better resolution. Not only that, you can resize later also, and it always backups the original image, allowing easy restore of accidental resize.
Excellent Table Management
Right click and manage cells/rows, and type/format in place without fiddling with `|` chars.
Insert Tables, with required cols and rows
Superb Link Control: Easily add words before or after caption selection, without fiddling hard with brackets and other Markdown syntax
Outlines without changing the Markdown File:
Command Palette > Markdown for Humans — Outline, and you can click on sidebar to reach H1 — H6 without guessing where they are located.
We also have inline outline generation without breaking the doc, so that one can easily know the doc structure.
GitHub Alerts: Supporting all types of GitHub alerts for excellent appeal
Love for Mermaids
We all love Mermaid on Markdown, we support nearly 15 templates for rapidly creating diagrams
Not just that one can double-click any Mermaid diagram for in-place editing.
Installation links
Suggest a feature, report a bug or raise PR
https://github.com/concretios/markdown-for-humans on this open source repo, with AI and vibe coding, the code has no value, thus we are keeping this extension free and open source.
In case you dont code, please feel free to use vibe coding to describe a feature as per our task plan template - so that any developer can pick it, once we move it to our roadmap, or can be used in discussions on GitHub for healthy debate about the future roadmap and how a feature makes most sense.
