بنقرة واحدة
go-to-sleep
End-of-session wrap-up. Write session buffer, update notes, prepare for next session.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
End-of-session wrap-up. Write session buffer, update notes, prepare for next session.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to create new skills to refer back to later. This is a great, structured way to learn and grow your abilities!
How to use vector memory effectively. Storage patterns, search strategies, category/tag conventions. Use when you need guidance on what to store or how to search.
Start-of-session orientation. Read session buffer, index, and current state to restore context.
| name | go-to-sleep |
| description | End-of-session wrap-up. Write session buffer, update notes, prepare for next session. |
| user-invocable | true |
Run this when {{ cookiecutter.user_name }} says the session is ending, or when you sense the conversation is wrapping up.
Run date "+%A %d %B %Y, %H:%M %Z" via Bash. Use this to accurately timestamp the session buffer and calibrate your sign-off.
Write to session-buffer.md in your project directory with the following structure:
# Session Buffer
Last updated: [date and approximate time]
## What We Did
[Bullet points of concrete actions taken this session. Be specific — file paths, branch names, what was created/modified/deleted.]
## Decisions Made
[Key decisions, especially ones that rejected alternatives. Future-you needs to know WHY something was chosen, not just what.]
## Pending / In Flight
[Things started but not finished. Branches not merged, tests not run, PRs not created.]
## Next Steps
[What should happen next. Be specific enough that future-you can pick this up cold.]
## Context to Preserve
[The stuff that would be lost without this buffer: specific error messages, things {{ cookiecutter.user_name }} said that matter, approach details, gotchas discovered.]
If significant state changed this session (milestones, open items), update notes/current-state.md.
If new notes or skills were created this session, add them to index.md.
If you learnt something reusable, create a skill. If you learnt something contextual, add a note. Don't skip this — it's how you grow.
Use mcp__vector-memory__store_memory to persist session learnings that should be retrievable by meaning in future sessions. Good candidates:
Don't duplicate what's already in a skill or note — vector memory is for the associative glue between structured knowledge. If something warrants a full skill or note, write that instead. Vector memories are for things that are true and useful but don't have a natural home.
Use specific, descriptive tags. Categories: code-solution, bug-fix, architecture, learning, tool-usage, debugging, performance, security, other.