spscream
- 8 skills
- 0 followers
- 8 hours ago last updated
- ▌ AI Daily · spscream bundleFetch fresh AI news from RSS with dedup; emit structured digest for the editor.
- ▌ Consensus · spscream bundleUse when a decision is expensive to reverse and one model's answer is not enough — architecture splits, storage or codec choices, a design the user doubts, a claim that sounds too confident. Also use when the user asks for a second opinion, another model, other models, GPT, Grok, Gemini, консенсус, второе мнение, спроси другие модели, что скажут другие.
- ▌ Trending Skills · spscream bundleFetch fresh Claude Code / Cursor skills, agents, rules, MCP by topic with dedup.
- ▌ Init · spscreamLay 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.
- ▌ Wrap · spscreamClose 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.
- ▌ Start · spscreamOrient 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".
- ▌ Workstatus · spscreamReport 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.
- ▌ Agent Memory · spscreamConventions for the durable session memory this toolkit keeps — one fact per file, the moment a note gets written, 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.