Naymur Rahman

Software Engineer @CommandCodeAI ✹ Building a Frontend ecosystem

[Naymur Rahman @naymur_dev]

🚀 Introducing UI-Layouts Blocks

Build faster with:
• 75 unique React blocks
• 10 categories like hero, about, feature, pricing etc

Built entirely with @shadcn, @tailwindcss & @framermotion

Copy paste with shadcn registry: npx shadcn add @ui-layouts/hero-digital-success

[Naymur Rahman @naymur_dev]

Just waiting to see.....

[VoidZero @voidzerodev]

VoidZero is joining Cloudflare.

Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.

Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.

[Naymur Rahman @naymur_dev]

@voidzerodev Congrats, this gonna be hugeeee 💪

[Naymur Rahman @naymur_dev]

@obaidnadeem_ Yep

[Naymur Rahman @naymur_dev]

Seems like orange is now the fav color of llms for design

[Naymur Rahman @naymur_dev]

@mahanot_dikshit super cool, I saw some of your other component , all looks cool

[Naymur Rahman @naymur_dev]

It seems like we both shoutout dotmatrix. it's really a good project thanks @zzzzshawn

[OrcDev @orcdev]

4 UI libs you've never heard of

[Naymur Rahman @naymur_dev]

@arre_ankit Thanks man

[Naymur Rahman @naymur_dev]

Last month's search console performance is crazy 🔥
it's going up! Still, there's a lot of work to do in SEO

[Naymur Rahman @naymur_dev]

@gaganghotra_ Thanks

[Naymur Rahman @naymur_dev]

@sadekships Thanks man

[Naymur Rahman @naymur_dev]

Design always depends on human taste. No matter how good AI becomes at generating visuals, our preferences keep evolving.

We get bored, trends shift, and we crave something fresh. That's when humans step back in to create the next new thing.
I don't know what will happen after AGI arrives, but right now, this is the reality.

What do you think? Will AI ever fully replace human taste in design?

[Naymur Rahman @naymur_dev]

https://t.co/q3T8Uh93BZ

[Naymur Rahman @naymur_dev]

Just found 3 CRAZY good React components 🔥

• Dot Matrix Loader (insanely satisfying)
• Fluid Functionalism: shadcn with Apple-level fluid animations
• Transition[.]dev: all about good transition in UI

Your UI is about to look premium.

Check out all the link 👇

[Naymur Rahman @naymur_dev]

https://t.co/VaJeMVa1Cu

[Naymur Rahman @naymur_dev]

https://t.co/4mQtTWhNcn

[Naymur Rahman @naymur_dev]

https://t.co/Ntd5G2RIr4

[Naymur Rahman @naymur_dev]

Another breakup 💔 nowadays, I'm breaking up to much with tools

[Micky @Rasmic]

I’m going to miss windsurf

[Naymur Rahman @naymur_dev]

@MrAhmadAwais Let's goo 💯

[Naymur Rahman @naymur_dev]

We're on the way of building something truly great 🔥

[Ahmad Awais @MrAhmadAwais]

BIG day for us!!

@CommandCodeAI has crossed $1M in annual run rate, 1 trillion tokens of usage, with over 9K customers, just 24 days after our public beta launch.

we believe this makes it the fastest-growing coding agent harness for open models. 3rd largest by usage.

Command Code is built around two ideas:
1. open models should be production-grade for coding.
2. your coding agent should learn your taste.

we're building for taste and developer experience. so instead of making a soup of thousands of models, we build for the best ones, open or closed. the goal: a coding agent that feels like an iphone, opinionated and with taste, not a random android or a windows phone with no taste.

on the first idea: open models.
we fixed the "open models aren't good enough at tool calling" problem. our research came down to two things, quality and speed, and both trace back to one root cause: broken tool-calls that open models produce, especially when you use a bad harness.

open-model tool-call failures are not deep, they are a small finite set of contract mismatches. so we repair them, with zero token loss. what started as 4 repairs is now the largest repair layer in the space: 36k tool-call fix variants. i wrote the idea up openly¹ a few weeks ago, and it has quietly become a de facto way people fix open models.

developers have either adopted Command Code or used the same idea to build repair harnesses for nearly every top coding agent. i take that as more meaningful validation than anything we could say about ourselves.

on the second idea: taste.
Command Code builds your coding taste into skills, learned from your accepts, rejects, edits, prompts, and the corrections you repeat. over time it drifts away from generic code and toward how you actually ship code. it learns continuously, and while it is early, the direction feels right.

net effect: developers using Command are writing production-quality code on open models, 10x to 100x cheaper, without fighting tool calls, while building repo and team-wide coding taste that compounds.

i believe these numbers are a consequence of getting those two things right.

what's next.
we've applied the same repair idea to ai design slop, and bundled a /design capability² so every developer can level up their design work. the early response has been great.

we have a big roadmap ahead of us. the feedback we hear most is that Command Code feels fundamentally different: an approach built on taste and repair.

we're going open source next month. today we're a cli at the core, and we're also launching a full-fledged gui app, sandboxed background agents, and cooking up something fun i can't wait to share.

we're growing too, hiring in sf and remote worldwide. check open roles on my profile bio.

try it now.
npm i -g command-code

if you like engineering deep dives on how we're doing all this, i've linked some relevant posts below.

[Naymur Rahman @naymur_dev]

What’s stopping you from trying it? 🤔

[Command Code @CommandCodeAI]

MiniMax M3 is now 50% off for the next week!

If you haven’t tried it yet, our Go plan starts at just $1 and includes $10 in usage credits.

[Naymur Rahman @naymur_dev]

@CommandCodeAI Yeppp 💪