Sabitlenmiş Tweet
scrxde
16.5K posts
scrxde retweetledi
Damn bro u never look at this twitter but I hit 500k followers, something I never thought would happen. I never really post on here too often anymore but that’s actually an insane milestone for anyone to ever hit. I’m forever grateful for everything and if you follow me, thank you ❤️
English
One has Cashback other is not donating, Dali will Donate Fully
This little girl Struggling in Gaza is going super viral on twitter, and even being compared to Punch
Her name is Yara and her family has been separated from her in the midst of war
There's a whole instagram account for her as well as a gofundme
I will be turning off cashback and instead donating the creator fees to the gofundme in the instagram bio instagram.com/yara_family5/
English
scrxde retweetledi
@mudler_it @BeboongZk @cowboyonchain @ismaildoureihi @FlatFinancials @MeltedMindz @kentmurphys @BagsApp @finnbags the entire point of the coin is to sponsor localAI, take a look at @GeoffreyHuntley he has raised 100k for his coding program so he can continue to build forward!
English
of AGENTS.md and skills I love one thing: it forces us to create dev document for a project properly, and, of some sorta allows us to contribute just via spoken human language. The barrier of documenting is low and good projects already have that, so it's a win-win.
David Cramer@zeeg
Something we've been trying out the last few days: instead of prompt stuffing AGENTS.md (especially in subfolders), add skills to the repository. So far the results seem better. Its totally possible its entirely behavioral ("just tell it to use the skill" vs assuming it does the right thing), but thats actually fine. Two things that we've done that I think are successful: 1) A bunch of tedium has gone into global skills (github.com/getsentry/skil…) 2) Specific skills in repos that follow patterns ("ui-design", "db-migration", "write-docs", etc.. github.com/getsentry/abac…) Then instead of throwing everything into AGENTS.md, its a lot simpler to just refer it to skills ("when doing X, use Y skill). It requires you to treat the skills like you'd treat any other code investment: maintain and distribute them. This is why I think its also important to do project-scoped configuration for everything (note: see the claude-settings-audit skill). You really need to build these once for the team (or once for the project), and maintain and iterate on them when they have problems. Anyways, so far so good. Nothing ground breaking - just an easy way to share prompt templates - but its smoothing out a lot of silly time sinks. I really want to see some of these behaviors become more cross-agent capable. Cursor's agent will pick up the in-repo skills, but the Claude plugins are specific to Claude right now.
English
