Imagine telling someone in 1999…
The year is 2026.
The President is Donald Trump in his second non consecutive term.
The richest man in the world is PayPal cofounder Elon Musk… but not because of fintech or Paypal. Because of rockets, electric cars, AI, satellites, brain chips and something called “Boring Company”.
Apple is worth trillions but its main business isn’t computers… its selling glass rectangles everyone stares at for 9 hours a day.
People don’t watch TV. They watch teenagers explain geopolitics, finance, and relationship advice in ~60 second videos.
The biggest taxi company owns no taxis.
The biggest hotel company owns no hotels.
The most powerful media companies are social networks where everyone argues with strangers for free.
Kids are making millions filming themselves playing video games.
AI Robots write emails, code, legal memos, songs, essays, and breakup texts.
The internet is mostly bots arguing with humans who are trying to prove they aren’t bots.
You can summon a car, groceries, a doctor, a date, a private jet, or a dog walker from your phone.
People pay real money for invisible currencies, digital monkeys, AI girlfriends and pictures that disappear after 24 hours.
The richest companies in the world don’t sell oil, steel, or cars. They sell attention, compute, data, and addiction.
And somehow, after all of that everyone is still using Excel.
@icanvardar Sadly true. I love Notion and the flexibility it provides but it has become intimidating with its sea of features and learning curve, especially to beginners!
Have been using some of those skills for a week now. Although I can’t say it boosted my productivity, it did improve the quality a lot, especially combined with the /clear context command before jumping to implementation.
One thing I’m still struggling with though is the quality of the tickets generated with /to-issues. I’ve found I’ve to often make edits to it, as it either makes assumptions or forget things from original user story.
Does anyone else find their coding agents comments frustrating?
For me, it frequently annoys me with
- Unnecessary comments for a change, especially if it’s a fix rather than a fresh feature
- Frequent references to specifics of other layers (frontend, backend, db) - feel this just adds more noise, especially if you are using agentic workflows
- Always having to explicitly ask for structured doc comments, especially if that module doesn’t have an existing pattern for it
Would love to know if anyone has found ways to work around this consistently
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