4 ms·

But... plain Claude does that. At least for my codebase, which is nowhere close to your 10m line. But we do processing on lots of data (~100TB) and Claude defin

But... plain Claude does that. At least for my codebase, which is nowhere close to your 10m line. But we do processing on lots of data (~100TB) and Claude definitely builds one-off tools and scripts to analyze it, which works pretty great in my experience. What sort of skills are you referring to?

jmalicki 7mo ago
If you build up and save some of those scripts, skills help Claude remember how and when to use them. Skills are crazy useful to tell Claude how to debug your particular project, especially when you have a library of useful scripts for doing so.
FINDarkside 7mo ago
I think people are looking at skills the wrong way. It's not like it gives it some kind of superpowers it couldn't do otherwise. Ideally you'll have Claude write the skills anyway. It's just a shortcut so you don't have to keep rewriting a prompt all over again and/or have Claude keep figuring out how to do the same thing repeatedly. You can save lots of time, tokens and manual guidance by having well thought skills. Some people use these to "larp" some kind of different job roles etc and I don't think that's productive use of skills unless the prompts are truly exceptional.
- jmalicki 7mo ago
  I have sometimes found "LARPing job roles" to be useful for expectations for the codebase. Claude is kind of decent at doing "when in Rome" sort of stuff with your codebase, but it's nice to reinforce, and remind it how to deploy, what testing should be done before a PR, etc.
- abustamam 7mo ago
  At work I use skills to maintain code consistency. We instrumented a solid "model view viewmodel" architecture for a front-end app, because without any guard rails it was doing redundant data fetching and type casts and just messy overall. Having a "mvvm" rule and skill that defines the boundaries keeps the llm from writing a bunch of nonsense code that happens to work.
  - dotancohen 7mo ago
    This sounds great - skills to ensure that the code maintains proper separation of concerns and is packaged properly. I'd love to know how this skill was phased.
    - abustamam 7mo ago
      Honestly I started with Obra superpowers and worked with my boss to brainstorm the best way to keep separation of concerns, and we just stepped on rakes as we developed and had Obra superpowers suggest updates to our rules/skills. It's certainly an iterative process but it gets better every iteration.
      - dotancohen 7mo ago
        Thank you. I've never heard of Obra Superpowers, I'm looking at it now.
  - pydry 7mo ago
    A deterministic layer linter would be better for this.
    - abustamam 7mo ago
      Possibly, and we do use linters, but linters don't stop LLMs from going off the rails. It does end up fixing itself because of the linter, but then the results are only as good as the linter itself.
DontTrustOver25 7mo ago
[dead]

jmalicki 7mo ago

If you build up and save some of those scripts, skills help Claude remember how and when to use them. Skills are crazy useful to tell Claude how to debug your particular project, especially when you have a library of useful scripts for doing so.

FINDarkside 7mo ago

I think people are looking at skills the wrong way. It's not like it gives it some kind of superpowers it couldn't do otherwise. Ideally you'll have Claude write the skills anyway. It's just a shortcut so you don't have to keep rewriting a prompt all over again and/or have Claude keep figuring out how to do the same thing repeatedly. You can save lots of time, tokens and manual guidance by having well thought skills. Some people use these to "larp" some kind of different job roles etc and I don't think that's productive use of skills unless the prompts are truly exceptional.

jmalicki 7mo ago
I have sometimes found "LARPing job roles" to be useful for expectations for the codebase. Claude is kind of decent at doing "when in Rome" sort of stuff with your codebase, but it's nice to reinforce, and remind it how to deploy, what testing should be done before a PR, etc.
abustamam 7mo ago
At work I use skills to maintain code consistency. We instrumented a solid "model view viewmodel" architecture for a front-end app, because without any guard rails it was doing redundant data fetching and type casts and just messy overall. Having a "mvvm" rule and skill that defines the boundaries keeps the llm from writing a bunch of nonsense code that happens to work.
- dotancohen 7mo ago
  This sounds great - skills to ensure that the code maintains proper separation of concerns and is packaged properly. I'd love to know how this skill was phased.
  - abustamam 7mo ago
    Honestly I started with Obra superpowers and worked with my boss to brainstorm the best way to keep separation of concerns, and we just stepped on rakes as we developed and had Obra superpowers suggest updates to our rules/skills. It's certainly an iterative process but it gets better every iteration.
    - dotancohen 7mo ago
      Thank you. I've never heard of Obra Superpowers, I'm looking at it now.
- pydry 7mo ago
  A deterministic layer linter would be better for this.
  - abustamam 7mo ago
    Possibly, and we do use linters, but linters don't stop LLMs from going off the rails. It does end up fixing itself because of the linter, but then the results are only as good as the linter itself.

DontTrustOver25 7mo ago

[dead]