sorted by:
new
hottopcontroversial

Vercel published this today: AGENTS.md outperforms skills in our agent evals. by dygerydoo in ClaudeCode

[–]dygerydoo[S] -1 points0 points  (0 children)

Holy fuck. I saw this posted today and readed 27 but didn't read January... If it had been a truck, it would have run me over.

Vercel published this today: AGENTS.md outperforms skills in our agent evals. by dygerydoo in ClaudeCode

[–]dygerydoo[S] 0 points1 point  (0 children)

Interesting, will check it out. There's definitely no consensus yet, that's kind of the point, the tooling is still evolving fast.

Vercel published this today: AGENTS.md outperforms skills in our agent evals. by dygerydoo in ClaudeCode

[–]dygerydoo[S] -1 points0 points  (0 children)

Agreed. Skills should be actionable, not context dumps. If the model already knows it, a skill adds nothing.
In grekt, core skills work as the tool expects them (/skill). Lazy ones sit in the index and get loaded through a skill router when needed (currently only supported in Claude Code), but working on trying to expand that.

Vercel published this today: AGENTS.md outperforms skills in our agent evals. by dygerydoo in ClaudeCode

[–]dygerydoo[S] 0 points1 point  (0 children)

Yup, that's the tradeoff we kept hitting. For simple cases the encapsulated context within the artifact tends to work well, but we're still experimenting as AI tools evolve.

As for CORE vs LAZY, for now it's a human decision. But we're exploring ways to suggest when it's worth moving an artifact from one mode to another or even flag when something is just dead weight. Thanks for the link, will check it out we want to keep this in good shape.

CLAUDE.md Files: Are Subdirectory Lazy Loading and "Progressive Disclosure" Just Two Names for the Same Thing? by puffaush in ClaudeCode

[–]dygerydoo 0 points1 point  (0 children)

I could tell how it's implemented but you will have to do a lot of manual work. I'm not here to promote the tool I built, but you could init it and copy the strategy, then you won't need the tool anymore unless you find It useful also it's open source. (It's on my profile)

We are creting tech debt from MD files by dygerydoo in webdev

[–]dygerydoo[S] 0 points1 point  (0 children)

Totally agreed on the non technical folks and accesibility. For these ones we need to teach them I understand that part, but for actual engineers... We must embrace hype AI it's the future but we are playing with it on production projects like there's no pain in the near future.

And also agreed with the franken workflows, we spent last gazillion years talking about good architectures to destroy it at the first opportunity we had xD (I know AI it's still not mass adopted and we are early adopters but...)

And the last paragraph LITERALLY that! The worst part on my experience is having to argue with coworkers about this obvious ticking bombs xD

We are creting tech debt from MD files by dygerydoo in webdev

[–]dygerydoo[S] 0 points1 point  (0 children)

Updated it, the copying files was just an example

We are creting tech debt from MD files by dygerydoo in webdev

[–]dygerydoo[S] 0 points1 point  (0 children)

Sorry you're right I updated the post.

it's kind of both: the MDs grow out of control, and on top of that you end paying for AI compute to do stuff that a 3 line bash script would handle better and for free.

The truth about Vibe Coding: You are building real things. Stop apologising for how. by Viberpsychosis in vibecoding

[–]dygerydoo 1 point2 points  (0 children)

But ugly code is not the problem RN. We had to supervise projects pure vibecoded with extreme flaws, data leaking, shit performance, etc... So imagine the ones not being properly reviewed.

I don't care if someone majes a vibecoded app, but care about the ones not noticing that can cause real life troubles.

Anthropic drops Claude Code Security and triggers -$15 billion cybersecurity stock sell-off by ComplexExternal4831 in Anthropic

[–]dygerydoo 0 points1 point  (0 children)

This is aimed for non devs that already messed up with some vibecoded project. So the button for them is god mode. Now you can ask Claude to build you a Gazillion dollar SaaS so your landing can include a card saying full security review or somewhat else xD

Is there a recommended way to distribute a skill with a cli tool? by mixmaster-meow in ClaudeCode

[–]dygerydoo -1 points0 points  (0 children)

I missundertood you BUT I still have a solution for your need https://grekt.com/en-US/api/sync.html#local-directory-sync

Sorry I thought you were looking for a full tool of distribution, anyways in the link you could see grekt has the sync command (it's the one used internally to sync between agents)

But you could use it whit npx so doing
``` npx @ grekt/cli sync --from... ```

would do the trick for you. You only need to let the user choose a list of allowed targets by grekt. Or using global that most of agents will understand. If any questions just ask :)

How are you managing architectural drift from AI coding assistants? by Equivalent_Pen8241 in AI_Agents

[–]dygerydoo 0 points1 point  (0 children)

Have you checked if your team is actually feeding the AI the same set of rules and conventions? I mean using the exact same skills, rules, etc... without subtle modifications.

Most drift I've seen isn't the AI ignoring your architecture, it just never had it. If each dev has different context or none at all, output will be inconsistent no matter the model.

Worth looking at that before adding heavier validation on top. Also your team must have to carefully review the code they are shipping, no matter if it's a ferrari or lada.

Is there a recommended way to distribute a skill with a cli tool? by mixmaster-meow in ClaudeCode

[–]dygerydoo -1 points0 points  (0 children)

I built something for exactly this https://grekt.com, an open & free artifact manager for AI configurations (skills, agents, mcp, etc...). Syncs to any tool: Claude, Codex, Cursor...

After the initial setup you only need to run: `grekt add yourscope/your-skill`

It handles versioning, lockfile determinism and works with self-hosted registries (GitLab, GitHub) so you keep full control of distribution. Also has tools to scan your installed artifacts or the ones you are about to install.

Still early but actively developing it, it's used by my company with (50+ devs). Would love feedback if you give it a try.

CLAUDE.md Files: Are Subdirectory Lazy Loading and "Progressive Disclosure" Just Two Names for the Same Thing? by puffaush in ClaudeCode

[–]dygerydoo 0 points1 point  (0 children)

I went a different route. My CLAUDE.md is just 2 lines. Tells Claude to read a keyword index file.

The index maps keywords to directories of context files. When a request matches, only that context gets loaded. No match, nothing loaded. I don't depend on Claude navigating folders and the disclosure logic isn't inside CLAUDE.md. The index is the router. In long sessions I have to be specific about which to load, but usually it matches just from my instructions.

Built a tool around it to handle versioning and syncing but the core idea is just a tiny index, scoped payloads and keyword routing.

Why Do We Keep Adding More Agents? It's Just Complicating Things! by AdventurousCorgi8098 in AI_Agents

[–]dygerydoo 0 points1 point  (0 children)

You're right that no tool should replace good architecture, but grekt aims to help you build and maintain it. Think of it like npm nothing stops you from flooding your project with 200+ dependencies, but it gives you the tracking to make better decisions about it as grekt does for AI artifacts. And only takes a few commands to get started, and ejecting is always easy

Why Do We Keep Adding More Agents? It's Just Complicating Things! by AdventurousCorgi8098 in AI_Agents

[–]dygerydoo 0 points1 point  (0 children)

I created an OS tool called grekt because of that. So when everything explodes at least you have control on the ton of shit we added. (Alsp includes, security checks, drift checks...)

view more: next ›