agent-skills · how I run Claude Code as a designer
Three skill families I use every day. Wrap (session hygiene), orchestrator (long-lived threads that don't write code), and gh-clean-branches (the repo debt nobody wants to pay).
// agent-skills · three families, eight skills// wrap: /wrap + /wrap-continue (session hygiene)// orchestrator: /scaffold + /update (state management)// gh: /gh-clean-branches + /gh-fork-sync + /gh-pr-triage + /gh-stale-issues//// Drop skills/ into your Claude Code project.// Each skill is a SKILL.md. No config, no deps.
Eight skills in three families. /wrap and /wrap-continue handle end-of-session vs. mid-task context resets. /orchestrator:scaffold and /orchestrator:update maintain the long-lived orchestrator thread itself. Four /gh-* skills clean up the debt that accumulates around a busy GitHub account.
Every Claude session ends one of two ways: you're done, or your context window is getting expensive. Those are different situations and they need different behavior. I wrote the skills the first time I noticed myself running the same close-out flow twice in a day.
The artifact is the argument. Words exist only to help you read what the artifact is already saying.