
Believes in the web ♥️ CTO (https://xitter.cf/t.co/2miQtltDRk) Founder of @OpenWc (https://xitter.cf/t.co/iXd5osdURK) Co Founder of @modern_web_dev (https://xitter.cf/t.co/Cg9YCwJgJF) Ex ING (Lion)
Austria - Vienna
Joined January 2009
- Tweets4K
- Following399
- Followers1.3K
- Likes5.6K
Pinned Tweet
Sharing time 🎉
I have been working a lot on `@rocket/engine` which you can see as a sort of a nuxt/next equivalent but instead of vue/react it works best with web standards like custom elements, ES modules, template literals...
Thomas Allmer retweeted
Announcing mattpocock/skills v1
- Achieved a 63% reduction in token cost for skill descriptions
- Split skills into model-invocable and user-invocable skills, adding /codebase-design, /domain-modeling, and /grilling
- (UPDATED) /writing-great-skills - rewritten from the ground up, encoding my skill-writing best practices
- (UPDATED) /diagnose -> /diagnosing-bugs - now model-invocable, awesome for fixing hard bugs
- (NEW) /ask-matt: a router skill that teaches you how all the engineering skills work together
Thomas Allmer retweeted
A frustrating gap I'm hitting in the skills spec.
TL;DR: I want three tiers of 'invocable'. User-invocable, skill-invocable, and model-invocable. Skill-invocable skills are only invocable by the user, or by skills.
Skills can be marked as model-invocable or user-invocable. Model-invocable skills put their description into context. User-invocable skills are hidden from the model, so no tokens are burned on the description.
But what about skills that you want to BOTH invoke on their own (user-invocable only), but also use as parts of other skills?
An example would be a /review skill, which:
1. Runs some automated checks on the repo
2. Checks the code against the original spec
3. Checks it against some coding standards
What if you want to pull out step 1 into its own skill? /run-automated-checks
You'd create that skill, then reference it in the /review skill: "1. /run-automated-checks"
In order to move that into its own skill, you MUST make it model-invocable - meaning its description goes into context.
This is pointless token waste. You can't omit the description - that goes against spec. But you'd just write a description saying "never invoke this except in other skills".
Anyone working on the skills spec? Has this been considered?
Thomas Allmer retweeted
Watch out! Chrome has a huge bug with <input type="number"> which causes values to change unexpectedly.
It's fixed in Chrome 150, but that won't land until the end of June.
I've always been frustrated with the frontend code AI agents generate.
Backend logic, scripts, pure implementation? Usually pretty good.
But frontend? Often messy.
This might actually solve it. Really looking forward to trying it 👀
youtu.be/bo3i0FzDUYo?si=K5A-…
Thomas Allmer retweeted
Since the day we started Documenso we knew that we would eventually have to write our own PDF library, and now we have!
Introducing LibPDF the library that we’ve always wanted for PDF parsing, manipulation and signing (MIT)
Thomas Allmer retweeted
This year we pushed hard into enterprise: org support, SSO, custom domains, and SOC2 in progress.
Documenso is the open-source DocuSign alternative for teams that need deep integration and full control.
Upgrading your signing infra or tired of vendor lock-in? DMs are open.
Thomas Allmer retweeted
Last week, I spoke at #Frontkon, Brno, Czech Republic, about the state of Progressive Web Apps (PWA), and again, I was amazed at how many available features are not used in web apps because people are simply unaware of them.
I spoke to many developers who were highly surprised about what is currently possible with web apps.
PWAs are a viable and cost-effective alternative to native apps. You only need one codebase to deploy an app on iOS, Android, and desktop and they can be freely distributed on the web without any app store dependencies.
Web apps can work offline for almost a decade now, yet most web apps don't.
Companies even sabotage their own web apps by making them dumbed-down versions of their native apps that only serve to promote their native counterparts.
Why?
Because many companies simply don't know or don't care. They think web apps are "not good enough" and quite frankly, I can't blame them.
Companies like X and Instagram have PWAs that don't even use half of the features available to them and that don't even work offline (while they can!)
So if they can't even do it, web apps must be bad, right?
Wrong.
Web apps can be so much better, but if even big companies don't bother, the smaller ones won't either.
I've made it my mission to educate and show what web apps are capable of (see whatpwacando.today) but without the support of big companies, the adoption of PWAs will have a long way to go.
We need more big companies to invest in web apps to show what is possible. It's in our joint interest to break free from the chains of app stores that can end your business whenever they want by kicking your app out of their stores.
These walled gardens shouldn't decide whether or not your business is allowed to compete. We should be allowed to deploy fully functional web apps that are not crippled by tech companies that deliberately hold back features to benefit the apps in their app stores.
That is what my mission is about.
really looking forward to this ❤️
We’re about to ship our last big refactor: multi-document envelopes ✉️
More than just sending multiple files, this update cleans up settings, fixes long-standing UX issues, and delivers the 10x experience we always imagined ✨
It also clears the way for the full release of API v2.0 🔌
More coming soon!
See what else we’ve shipped:
documenso.com/changelog
documenso.com/blog
Thomas Allmer retweeted
I am very excited to announce the alpha release of the #WebComponents Language Server!!!
Thomas Allmer retweeted
FutureProofHomes.ai now ships to Canada, Australia & New Zealand! 🎉 The store is stocked and shipping is free (for now)! 📦
If you're looking for a completely private, AI-powered voice assistant and multi-room music solution to replace Alexa and Sonos, look no further!
Thomas Allmer retweeted
💥 Today's release is bigger and *beta* than ever. We decluttered, redecorated, and added some new toys (<wa-popover>, <wa-zoomable-frame>, full-page layout patterns, and an npm package). It's your turn to boldly build like no dev has built before: webawesome.com 🚀
Thomas Allmer retweeted
Nexus is our fully private, local AI computer and voice assistant that runs your entire smart home—no cloud, no compromises. Don't believe us? Watch the video! youtu.be/WrreIi8LCiw
Thomas Allmer retweeted
Yes! It is really back, this time with Cross Play!
We’re talking about Friend’s Pass of course - if you buy Split Fiction, anyone can play the ENTIRE game with you for FREE online. And now on ANY platform as well! 💥
Doing all we can to help out 😉
Now it’s up to you to grab a friend on March 6th and dive in.
#SplitFiction
Thomas Allmer retweeted
🚨 Our new API V2 is now in Beta!
We feature native SDKs for Typescript and Go, with Python to follow shortly!
Thomas Allmer retweeted
Today we’re launching our first homegrown AI model: an open source turn detection model for building voice agents.
Instead of relying solely on voice activity detection (VAD), which only considers when a user is speaking, our model also considers what has and is being said in the context of a conversation and predicts when a user is finished expressing their thoughts before the agent responds.
Conversations with AI voice agents using this new model flow much more naturally without constant interruptions from the AI— check it out (more videos, details, and code in the thread):
Thomas Allmer retweeted
This presentation to TC39 has me *worried* for the future of JavaScript.
I
Do not
like this phrasing.
Let's dive in 👇
(1/35)
oh wow TC39 is playing with the idea of JavaScript always requiring a build tool 🤬
I have been using a build less approach for development for years and it's so much more fun and simpler to manage for me and my team.
PS: for the production deployment we use a build of course
Shout out to @ryanckulp and @useTRMNL for what could have been an annoying shopping experience into a delightful conversion 💪
Looking forward to TRMNL and for what it will enable.
Delightful hardware programming I assume 🤗





















