writing / build-your-own-arsenal

build your own arsenal

everyone's installing skill packs right now

gstack blew up in a week

feels like leverage

but most of the value isn't in generic skills

it's in the stuff that keeps repeating because it broke before

that part doesn't ship


change something

then trace what it breaks

repeat enough times

it's no longer a habit

it's a missing system


ran a simple prompt against the setup

"given claude.md + current skills

what patterns keep showing up that aren't extracted yet"

not looking for ideas

just what's already happening


output isn't new workflows

it's the same steps

already being done

just without a name

kind of obvious in hindsight


filter is simple

what breaks if this step gets skipped

not "is this reusable"

that question is usually wrong

just does something go wrong


if skipping it caused a bug before

it's probably not optional

that part took a while to admit


next decision is scope

shared context → extend

cross-cutting → standalone

most things don't need new commands

just need to stop pretending they're ad-hoc


public packs are useful

but mostly for contrast

not to copy

to see what's missing

different layer entirely


generic packs optimize for average workflows

but most cost comes from specific failure modes

the ones that only show up in a particular setup

that's where the leverage sits


what ends up extracted

trace before change

verify after removal

check contracts against reality

kill paths and prove they're dead

nothing new

just no longer implicit


best skills don't come from browsing packs

they come from the step that keeps repeating

because skipping it broke something

usually annoying

usually unglamorous

still the highest leverage