The skills
A skill is a folder with instructions in it. Claude loads one when the task matches, so knowledge I'd otherwise repeat every session is written down once. This is the collection as it stands today.
Where they come from
Written by me
Prefixed jja-. Built over time,
usually the third time I explained the same thing.
Third-party
Picked up from the community: algorithmic-art, ask, git-ai-search, playground, prompt-analysis, remotion-best-practices.
Worth stating plainly, because it gets muddled when people share setups:
GSD is not my work.
I use it heavily and it shapes how I plan phases, but credit belongs to
its authors. The jja- skills are mine.
What I've written
Each one started as a correction I got tired of repeating. That's the whole heuristic: if I explain it three times, it becomes a skill.
Press / to search. Fuzzy — typos are fine.
Git & release
5The two you'll hear me mention most. Every commit goes through one of these.
/commit
/release
/release-catchup
/changelog-backfill
/git-hooks Frameworks
6Stack-specific knowledge that would otherwise be re-explained every session.
/astro
/astro-updates
/nuxt
/nuxt-cloudflare
/vue
/scaffold Research & recon
8Pulling the outside world in — competitors, leads, docs, whole sites.
/recon
/perplexity
/lead-dossier
/github-grabber
/site-mirror
/urls
/domain-name-brainstormer
/scout Content & media
9Turning work into artefacts: posts, decks, documents, images, audio.
/blog-writer
/imagen
/docx
/pdf
/xlsx
/notebook
/frontend-slides
/visual-explainer
/unsplash Performance & SEO
3Measuring client sites instead of guessing at them.
/lighthouse
/unlighthouse
/ahrefs Infrastructure
6Cloudflare, payments, automation, notifications, browser control.
/cloudflare-images
/stripe
/ntfy
/playwright
/pinchtab
/email Meta — skills that build skills
14The compounding layer. These are why the collection got to 58.
/skill-creator
/mcp-builder
/memory
/council
/deeper-insights
/stats-dashboard
/project-tasks
/timeclock
/timer
/brand-guidelines
/founder-lab
/ui-cloner
/ui-ux-pro-max
/cc-updates Subagents (33)
Specialised workers spawned for a scoped task — a code reviewer, a researcher, a debugger — each with its own tools and context. The main conversation stays clean while they work in parallel.
Most come from GSD's phase system: planners, executors, verifiers, auditors.
MCP servers (5)
Live data sources the agent can query directly, rather than guessing from training data.
astro-docs claude-data grep nuxt stitch claude-data is the one that matters
most — it's the memory database.
How it's built →
Slash commands
Lighter than a skill — a single prompt saved under a name.
/add
/diff-review
/fact-check
/generate-slides
/generate-web-diagram
/plan-review
/project-recap
/yt-search