Night Park
Park a late-night Claude Code session with a handoff file and exact resume command for tomorrow.
Overview
night-park is a journey-wide agent skill that parks your Claude Code session with a handoff doc and resume command—usable whenever a solo builder needs to stop mid-work without losing parallel-session context.
Install
npx skills add https://github.com/fearovex/claude-config --skill night-parkWhat is this skill?
- Zero-interaction end-to-end run: analyzes chat, writes handoff, mirrors to engram, prints claude --resume command
- Persists docs/handoffs/session-<id>-<slug>.md locally (gitignored) plus engram topic_key handoff/<slug>
- Uses current CLAUDE_CODE_SESSION_ID so parallel sessions stay distinguishable
- Triggers include /night-park, park session, and Spanish phrases for end-of-day parking
- Substantive summary designed for a 30-second read before resuming the exact session
- Two persistence targets: local handoffs file and engram mirror
- Single-invocation zero-interaction workflow
Adoption & trust: 1 installs on skills.sh; 1 GitHub stars; trending (+100% hot-view momentum).
What problem does it solve?
You run several Claude Code sessions in parallel and cannot tomorrow remember which session ID was attacking which problem.
Who is it for?
Heavy Claude Code users who stop mid-task overnight and need deterministic session breadcrumbs across projects.
Skip if: Teams that do not use Claude Code session IDs, workflows without engram, or one-shot tasks finished in a single sitting with no resume need.
When should I use this skill?
/night-park, night park, park session, me voy a dormir, guardar sesion, parking nocturno, handoff session.
What do I get? / Deliverables
You get a local handoff markdown file, an engram-tagged summary, and a copy-paste claude --resume <id> command to restart the exact session in seconds.
- docs/handoffs/session-<id>-<slug>.md
- engram entry with topic_key handoff/<slug>
- Printed claude --resume <id> command
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Park halfway through an API migration so tomorrow you resume the same session ID on the failing endpoint.
Stop after a long review pass and capture open findings before morning merge decisions.
End a evening thread draft session with links and tone notes preserved for the next publish push.
Hand off an intermittent production bug investigation with repro steps and hypotheses intact.
Pause a late scoping chat and resume the same tradeoff discussion without re-uploading constraints.
How it compares
One-shot session parking ritual—not a general project management template or git-based WIP branch workflow.
Common Questions / FAQ
Who is night-park for?
Solo builders using Claude Code who parallelize deep work across terminals and need reliable end-of-day handoffs tied to session IDs.
When should I use night-park?
Before sleep during Build feature work, mid-debug in Ship, after Launch copy drafts, or any Operate iterate night when you must resume the same session—not a new chat—tomorrow.
Is night-park safe to install?
It writes local handoff files and engram entries from conversation content; review the Security Audits panel on this Prism page and keep docs/handoffs gitignored as intended.
SKILL.md
READMESKILL.md - Night Park
# night-park > One-shot "park this session" command for end-of-day handoff across multiple > parallel Claude Code sessions. Reads the current `CLAUDE_CODE_SESSION_ID`, > drafts a substantive summary from the conversation, persists it to disk and > to engram, and emits the resume command. **Triggers**: `/night-park`, night park, park session, me voy a dormir, guardar sesion, parking nocturno, handoff session --- ## Purpose Working very late across 3+ Claude Code sessions in parallel makes it impossible to remember tomorrow which session was attacking which problem. This skill drops a tagged breadcrumb per session: a real summary you can read in 30 seconds and resume the EXACT session by ID with one command. The handoff lives in two places: - **`docs/handoffs/session-<id>-<slug>.md`** — readable by you, by your IDE, and by any future Claude session opened in that project. Local to the project; not meant to be committed (gitignored). - **Engram** with `topic_key: handoff/<slug>` and the `session_id` embedded — searchable from any future session in any project via `mem_search handoff`. --- ## Process The skill runs end-to-end with NO user interaction. No drafts to confirm, no slug to pass, no questions. The user invoked this because they want to stop thinking — respect that. ### Step 1 — Read the session ID Read the environment variable `CLAUDE_CODE_SESSION_ID`. Use the full UUID (do NOT truncate). If the variable is empty, abort with a one-line message: `night-park: CLAUDE_CODE_SESSION_ID not available in this environment — cannot park.` ```bash echo "$CLAUDE_CODE_SESSION_ID" ``` ### Step 2 — Derive a slug from the conversation Analyze the conversation history and produce a 3-5 word kebab-case slug that captures the PROBLEM being worked on (not a generic verb). Examples of good slugs: - `pro-plus-duplicate-customer` - `n-plus-one-user-list` - `auth-middleware-token-leak` - `night-park-skill-creation` Bad slugs (do NOT use): - `session-work`, `debug-stuff`, `today`, `wip`, `task` — useless tomorrow. The slug MUST be ≤ 60 chars, lowercase, alphanumerics + hyphens only. ### Step 3 — Draft the summary from the conversation Read the conversation context and fill these sections substantively. These are NOT placeholders — they are the entire point of the document. | Section | What goes here | Length | |---------|----------------|--------| | `## Qué estábamos haciendo` | The OBJECTIVE of the session — what problem we were attacking, why it mattered, the user's original ask. | 2-4 lines | | `## Dónde quedamos` | Concrete current state — what was done, what decisions were made, what is half-finished, what is blocked. | 2-4 lines | | `## Próximo paso` | 1-3 bulleted, actionable items — the FIRST thing to do tomorrow when reopening. Each bullet must be doable, not abstract. | 1-3 bullets | | `## Archivos tocados / relevantes` | Files modified or central to the discussion, with a one-line reason each. | bullet list | | `## Contexto técnico clave` | Only if there is a non-obvious gotcha, a key decision, a command to remember, or an external link. **Omit the entire section if there is nothing substantive.** | optional | Write in the same language the user has been using in the session (Colombian-style Spanish or English). Default to the dominant language of the session. ### Step 4 — Pick a title The first line of the document is `# <Title>`. The title is one human-readable sentence that names the problem — NOT the slug. Examples