Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkillsAuthors › paulnsorensen

paulnsorensen

@paulnsorensen on GitHub →

12 Claude Code skills authored by paulnsorensen.

updated 2026-05-23 · showing 1–12 of 12 by quality score

Average Pro QualityScore: 75.3/100

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

This skill should be used when the user asks to read, view, show, open, or display the contents of a file or directory — phrases like "read src/auth.ts", "show me this file",…
This skill should be used when the user asks to edit, replace, modify, update, change, delete, or insert code in a file — phrases like "replace this function", "delete lines…
This skill should be used when the user has an `/age` report (or any list of review findings, CI failures, or a "fix these" instruction) and wants the selected items resolved —…
This skill should be used when the user has a fuzzy idea, half-formed feature, or design direction and wants to converge on a spec — phrases like "let's design X", "I'm thinking…
This skill should be used when the user has an approved spec or unambiguous task with a high-blast-radius footprint and wants the whole pipeline (cook → press → age → cure → age →…
This skill should be used when the user wants to think out loud, rubber-duck a design, walk through trade-offs, or explore an ambiguous problem WITHOUT producing production code…
This skill should be used when the user wants a metacognitive vibecheck gate before code is shared for review or a pull request is opened — phrases like "/hard-cheese", "/cheese…
This skill should be used when a git merge, rebase, or cherry-pick has produced conflicts and the user wants them resolved — phrases like "melt the conflicts", "fix the merge…
This skill should be used whenever the user asks to research, look up, compare, or investigate something external to the immediate codebase — phrases like "research X", "look up…
This skill should be used when the user has an approved spec that decomposes into 5+ independent behavioural curds and wants the whole pipeline run in parallel with reviewable PRs…
This skill should be used when the user asks to find a symbol, definition, caller, import, or text pattern in the codebase — phrases like "where is X defined", "what calls Y",…
This skill should be used right after `/cook` produces green changes, when the user wants the test surface hardened before review or shipping — phrases like "press the changes",…
Search all 12 skills by paulnsorensen →