← All creators

spscream

User

Session ritual for coding agents: durable git-committed memory, a start rite, a wrap rite, and the guards that keep them honest. Claude Code + Cursor plugin.

5 indexed · 0 Featured · 0 stars · avg score 72
Prolific

Categories

Indexed Skills (5)

Code & Development Listed

init

Lay the floppy memory out in this repository — copy the shim to .floppy/run, write .floppy/config, create the memory skeleton, gitignore the local scope, and point AGENTS.md at agent-memory. Idempotent, safe to run again. Use once per repository, when setting the plugin up for the first time, or when the user asks to init, set up, or bootstrap floppy here.

0 Updated yesterday
spscream
AI & Automation Listed

workstatus

Report what is true right now, checked live rather than recalled — retells `bash .floppy/run status` and names what is waiting on the human. Use mid-session for "where are we", a live status check, before answering a question about current state, or when the user asks for workstatus.

0 Updated yesterday
spscream
AI & Automation Listed

wrap

Close a session — select the facts worth keeping into memory, update the current-state file, name what's left unfinished, then check and commit through the shim. Use when a session is ending, context is about to be cleared, or the user asks to wrap up.

0 Updated yesterday
spscream
AI & Automation Listed

agent-memory

Conventions for the durable session memory this toolkit keeps — one fact per file, note frontmatter and metadata.evidence, the three-level index tree, the quota.lock ratchet, and which of project/cross-project/workplace/machine scope a fact belongs to. Load this before writing, moving, or reorganizing a memory note, or whenever start/workstatus/wrap need the ground rules — they assume these conventions rather than restate them.

0 Updated yesterday
spscream
Data & Documents Listed

start

Orient a fresh session before touching any file — read the current-state file, the relevant half's own guidance, and that half's memory index, then verify live facts with `bash .floppy/run status` instead of trusting the documents. Use at the start of a session, when picking up a new task or branch of work, or when the user asks to start, orient, or "what's next".

0 Updated yesterday
spscream

Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.