Spent the last few weeks codifying how I work with Claude into a reusable library. Sharing because it might save someone else the same effort.
What it is: 59 skills covering the full lifecycle of building, launching, running, and growing a website. 13 categories: brand discovery, creative briefs, IA, content strategy, brand identity, design systems, content/copy, SEO (foundation + audit suite), product specs, dev (code review, components, accessibility, performance), QA, ops (launch, incident response, monitoring, security), growth, research, and a meta-skill that teaches you to write your own.
What's interesting (vs. just listing skills):
Uniform structure across every skill: when to use, when NOT to use, required inputs, the framework, the workflow, failure patterns, output format, references. The "when NOT to use" sections were where most of my best thinking ended up.
Stack-agnostic on purpose. I started writing them tied to Next.js + Supabase, then realized the skills got way more useful when I forced myself to write them so they'd work on WordPress, Shopify, Webflow, plain HTML, anything. The constraint forced the abstractions to be real.
The SEO audit suite (7 skills) is built around the Ahrefs MCP. It's the one place I broke my "stack-agnostic" rule because it's so much more useful with structured data behind it. The orchestration skill chains the others (backlink, keyword gap, content gap, traffic diagnosis, site health, rank tracking) into a complete audit run.
CI lint validates structure on every contribution. Em dashes, broken refs, frontmatter validity, missing references, mismatched catalog counts. Catches drift before merge.
There's a meta-skill (skill-creation-walkthrough) that codifies how I write skills. The thing that took me longest to articulate was the skill description. Getting the trigger phrases right is the difference between a skill that fires reliably and a skill Claude ignores.
The honest test I used: would these skills survive me losing access to my own setup tomorrow? If a stranger could clone the repo and ship the same quality of output, the work earned its place. Otherwise it was just my tacit knowledge in a folder. Cut a lot during that pass.
MIT licensed. github.com/rampstackco/claude-skills
Happy to answer questions about specific skills, the structure decisions, or what I cut and why.