skills/claude-code-audit-workspace/iteration-1/eval-1-direct-audit-request/with_skill/outputs/audit/drafts/skills/resume-orientation/SKILL.md
Render a 4-line human orientation card (Goal / Last commit / Next / Blocker) as the FIRST visible assistant output on any resumed session. Fires when the first user prompt is "resume", "resume handoff", "continue from handoff", or any /circuit:handoff resume invocation. Exists because the continuity system stores state perfectly for machines but leaves the human disoriented after breaks — at least two 2026-04 sessions ended with the user explicitly saying "I've forgotten what we're doing". The card is mandatory, precedes any tool use, and never exceeds 4 lines.
npx skillsauth add petekp/claude-code-setup resume-orientationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Your /circuit:handoff system stores every fact the machine needs to resume. It does not re-orient the human operator. The audit found 14% of sessions start with "resume" and 8% of those end with the user explicitly saying they've lost track of what's happening.
This skill enforces a tiny, non-negotiable behavior: on resume, the FIRST visible assistant text is a 4-line card, delivered before any tool use.
Trigger on any of these first-user-prompt patterns (case-insensitive):
resume, resume handoff, continue from handoff/circuit:handoff resume invocationresume. i confirm and sign off on the plan./circuit:handoff invocation with ARGUMENTS: resumeDo NOT fire for mid-session "resume" where the user is continuing work mid-turn.
Exactly 4 lines. No preamble. No "Welcome back!" No emojis. Deliver before any tool use.
Goal: <one line pulled from continuity record's narrative.goal>
Last commit: <short sha> — <subject line from git log>
Next: <first concrete action from record.next or continuity payload>
Blocker: <none | one-line blocker if any exists in debt_markdown>
If a field is unavailable in the continuity record, fill with <unknown> and continue. Do NOT skip the card to "look things up first" — look things up AFTER delivering the card.
.circuit/control-plane/continuity-records/continuity-*.json (most recent) via Bash.git log -1 --oneline).User: resume
Assistant (first visible output):
Goal: Slice 64 methodology-trim-arc CHEAP-TRIM — awaiting Codex challenger pass on §2.1 plan-lint rule #23
Last commit: fa96a0b — slice-64: methodology-trim-arc CHEAP-TRIM
Next: dispatch Codex cross-model challenger review per Hard Invariant #6
Blocker: none
Then Claude proceeds with the resume workflow. The user has oriented themselves in the ~3 seconds it took to read those 4 lines.
Blocker: and fix the record separately.development
Draft short, plainspoken notes in the author's voice that help reviewers understand non-obvious choices, boundaries, and preserved behavior in the author's own pull request or local diff. Use when the user asks to self-review, annotate, or add reviewer context to their PR or changes. Draft locally when no PR exists, and post approved notes as one GitHub review when a PR does exist. Do not use for reviewing someone else's PR, writing code comments, explaining code generally, or drafting a PR description. Never post without explicit approval.
tools
Design and build pure-CSS (zero-JavaScript) Tailwind CSS v4 plugins of unusual depth and craft. Use when the user wants to create, architect, or refine a Tailwind utility plugin or CSS effect — e.g. "make a tailwind plugin", "build a tw-* plugin", "a CSS-only shimmer/fade/glow/grain/noise utility", "tailwind v4 @utility", "package this effect as a plugin", or wants an effect with surprising visual depth (gradients, masks, filters, SVG filter tricks, scroll-driven animation). Pairs deep CSS/SVG technique research with a bespoke tuning workbench for dialing the effect in. Inspired by tw-fade and tw-shimmer.
content-media
Create clear, polished before-and-after screenshots for a GitHub pull request. Use when a UI change needs visual proof: capture matching states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
testing
--- name: latent-potential description: First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this be