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-cleanup (the repo debt nobody wants to pay).
// /wrap-continue · light capture, mandatory push,// hot-resume pickup prompt rendered inline.//// Used when recycling a long-lived thread mid-task,// not when ending a session for real.//// Pairs with /compact as token-discipline tooling.
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.
Skills are easier to write than to name. The hard part is the boundary between two skills that look similar · what /wrap and /wrap-continue do differently is the whole reason both exist. Names that don't carry that distinction get used wrong.
The artifact is the argument. Words exist only to help you read what the artifact is already saying.