Deep session context hydration with task creation. Use when severity is CRITICAL, when there are unresolved blockers, or when the user asks about session state, handoff status, or what to work on next.
Hydrates session context, checks for drift, and creates tasks from handoffs when resuming critical work.
npx claudepluginhub ramonclaudio/skillsThis skill is limited to using the following tools:
!cat .handoff/state.json 2>/dev/null || echo "No state found — run /handoff:end first"
!cat .handoff/CONTEXT.md 2>/dev/null || echo "No context found"
Branch: !git branch --show-current 2>/dev/null || echo "unknown"
!git status -s 2>/dev/null
Recent commits:
!git log -10 --format='%h %s' 2>/dev/null || echo "No commits"
!gh pr list --limit 5 2>/dev/null || echo "gh not available or no PRs"
_runtime.hostname from state.json. If it matches current hostname (hostname -s) and session_id differs from current session, the previous session may be resumable at protocol level. Note this in output: Previous session resumable: claude --resume <session_id>. This gives full context replay vs. lossy handoff rehydration.source field for confidence ("manual-end" > "auto-save" > "init")TaskList, TaskGet for each — identify handoff/blocker/resume metadataHydrate tasks from state.json (idempotent):
handoff: true and matching session already exist for the current session, skip creation (prevents duplicates on repeated invocation)TaskUpdate status: "completed")blocker: true, handoff: true, session: "${CLAUDE_SESSION_ID}")resume: true, handoff: true, session: "${CLAUDE_SESSION_ID}")Output read-back:
╔═══════════════════════════════════════════╗
║ HANDOFF RECEIVED ║
║ Project: [name] | Stack: [stack] ║
║ Severity: [emoji] ║
╚═══════════════════════════════════════════╝
💡 RESUMABLE: claude --resume <session_id>
(only if hostname matches — full context replay vs lossy rehydration)
SINCE LAST SESSION
├─ Commits: [N] | PRs: [N] merged
└─ Tasks: [N] hydrated
⚠️ WATCH OUT FOR / 🚫 BLOCKERS / ❌ FAILED
[lists]
▶️ RESUME
[Next action, files, context]
────────────────────────────────────
Ready. What would you like to work on?
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.