
created text-to-handwriting building @abellland lead frontend @razorpay
Bengaluru, India
Joined May 2019
- Tweets10.2K
- Following882
- Followers7.1K
- Likes32.1K
Pinned Tweet
In case you missed it at ViteConf and React India,
Abell v1-beta is out now 🥳
Do give it a try and share it with your friends 🤗
Anndd its here!!!
Presenting, Abell v1-beta 🥳
- Low Level and Closer to HTML Static-Site-Generator 🤓
- Supports all Vite Plugins 🤗
- Integrates seamlessly with your favorite tools from ecosystem 🫶🏼
RT to share with your friends 👉🏼👈🏼?
Learn More at
abelljs.org/posts/one
Saurabh retweeted
Hi, it's Darshita. I am a designer.
And I'm pitching myself in public 'cause I'm done with a year full of anxiety.
Everyone says design is dead and AI killed it. But the real parasite was hiding in plain sight.
So here's my film, DESIGN IS DEAD. She's bold, fearless and very PINK 💖
Hiring? My DMs are open.
Is there any engineer / designer who doesn't feel this way? What are you all doing differently?
Saurabh retweeted
Replying to @saurabhdawaree
@saurabhdawaree on giving talk on skills and sub agents!!
He built GTA-7 in 30 mins.🥂
Saurabh retweeted
AI agents are changing how we work and collaborate, but documents are still stuck in the pre-AI era.
Agents can now create beautiful, interactive decks, dashboards, and reports in HTML. But the moment you want to collaborate on them, everything breaks down.
Google Docs wasn’t built for rich, interactive HTML or AI agents. Feedback gets scattered across Slack and email. Every edit means going back to the agent, generating a new file, and sharing another link. No real-time collaboration. No single source of truth.
We built SlashDocs to fix this.
Think Google Docs, but built for AI agents and the documents they create. Host HTML and Markdown in one central hub. Share documents, manage permissions, and comment directly on the content, just like Google Docs.
Agents can read feedback and update the same document in real time. No duplicate files, no endless back-and-forth, and everyone stays in sync.
What started as a small internal experiment in one team has now scaled across @Razorpay. 28,000+ documents created. Over 50% of all documents generated at Razorpay now live on
SlashDocs.
And today, we’re opening it up to everyone. Self-hosted. Agent-agnostic. Fully open source.
AI agents have changed how we create documents. It’s time we changed how we collaborate on them.
Try it: razorpay.com/slash-docs/
Saurabh retweeted
We recently built an AI assistant inside @Razorpay called Slash.
It reads our entire codebase, debugs production incidents, reviews specs, writes code, reviews every single PR, answer tech queries and also raises PRs for small features.
It's easily accessible through Slack. We can tag it in any Slack thread, describe the problem in English, and it gets to work.
Six weeks ago, Slash handled 122 tasks in its first week. Last week it handled 14000+. Queries, analysis, bug fixes, PR reviews, test runs and work that earlier lived across scattered tools and teams can now be done with Slash right within Slack. 1000+ people used it in a single week because it got their work done faster. The whole adoption has been completely organic.
The numbers from last week have been very encouraging - 14,854 tasks completed. 2,150 PRs raised, 1,152 merged, 45% of those PRs shipped with zero human rework.
A payout gets stuck mid-retry during a live incident, an engineer tags Slash and within seconds, it cross-references logs with code and pinpoints a state machine bug blocking the retry-to-failed state transition. Tells the team exactly which logs to check and how to resolve the incident.
With its K8s analyzer skill, Slash scanned a single namespace, right-sized all 11 workers using 48-hour P95 pod metrics, and raised the PR. One run saved $560/month.
A marketing banner bug was fixed with few prompt iterations with a PR raised, merged to prod and deployed in minutes. No front-end developer touched the code.
Security teams ran static security testing and remediation through Slash at org scale. Thousands of findings were purged and many more got validated autonomously.
But Slash isn't just an engineering tool.
Account managers now trace stuck customer payments and integration failures through Slash instead of pinging engineers on Slack. L2 product support tickets get triaged by Slash before they reach engineering.
250+ non-engineers ran thousands of sessions last week. PMs used it for research on our payments infra, customer interviews and product features sometimes raising PRs of their own. Analytics teams built SQL pipelines. 11% of all sessions came from people outside tech and product.
On our company bakkar (watercooler) Slack thread, someone asked Slash jokingly to assign tasks to everyone and it responded in the same tone. It seamlessly started participating in inside jokes and conversations.
The quality compounds with use. Engineers who shipped 11+ Slash PRs averaged a 63% merge rate without rework. First-timers averaged 37%. Across the org, human review comments per PR have dropped more than 40% with Slash starting to do in-depth review of every single change.
We're still early. Large cross-repo refactors, fully agentic sdlc and plan mode are next. But Slash has already changed how people at Razorpay build, debug, and ship every day.
Saurabh retweeted
We are at @opencode buildathon, if anyone is building into agentic space should try whyops.com for out of the box observability.
Saurabh retweeted
GPT 5.4 is now available in Cursor!
We've found it to be more natural and assertive than previous models. It's currently the leader on our internal benchmarks.
Fun fact I learnt recently is that you can get diff of any PR by adding `.diff` at the end of the URL.
Pretty handy if you want to pass it to your AI agent to get context of PR changes in chat
github.com/abelljs/abell/pul…
how that we have agent skills standardised, can we also standardise a single agent directory pls
`.agent/skills` 🙏🏻
AI space does move very fast lesgo
xitter.cf/leerob/status/20187700…
I have realised that there are few tasks that I can do faster than AI. Hence I will be taking over AI's job going forward. Thanks.
Saurabh retweeted
This is a game changer!
Connecting natural languages with a video creation tool which uses code as its source of truth!
It's a match made in heaven! Motion graphics is about to change.
Saurabh retweeted
The video which ADANI doesn't want you to see..
Adani TV (NDTV Marathi) showed @RajThackeray's speech for the first 13 mins, As soon as Raj Thackeray started showing the growing monopoly of Adani across India in last 11 years. They immediately cut off his speech.
Saurabh retweeted
We brought "vibe-coding" to our Design System⚡️
Glad to be featured in @Pragmatic_Eng! We shared with @GergelyOrosz how Blade MCP bridges the gap that external tools couldn't.
Read here 👇 newsletter.pragmaticengineer…
Blade MCP is also Open Source: npmjs.com/package/@razorpay/…
🧵1/3





















