← ClaudeAtlas

initlisted

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.
spscream/ai-floppy · ★ 0 · Code & Development · score 72
Install: claude install-skill spscream/ai-floppy
# Init A thin wrapper. All the work is in `scripts/init.sh`; this skill exists to ask the two questions the script cannot answer for itself, then run it. ## 1. Ask Ask the human, in one short message, for: - **the memory directory** — where this repository's durable memory lives. Suggest `.agent-memory` if they have no reason to want something else. - **the memory language** — the language notes get written in. This is independent of the language the agent replies in (see `agent-memory`); suggest `en` if they have no preference. Do not guess either value silently — a wrong memory directory is annoying to move later, and this only needs one short question. ## 2. Run the script Before running it — this is the writing half, it lays files into `--repo .` — confirm that directory is the repository the human meant to set up. Several projects can be open in the same harness at once (Cursor especially), and the shell a skill runs in is not necessarily the one the human was talking about. One line naming it is enough. Neither harness is trusted to hand a skill the plugin root, so do not rely on a variable alone. Claude Code sets `CLAUDE_PLUGIN_ROOT` and Cursor sets `CURSOR_PLUGIN_ROOT` (measured 2026-08-26), but each only in some contexts, and a variable a harness did not set is indistinguishable here from one it did. Locate the plugin the same ways `.floppy/run` locates it once installed — the two harness variables, then `AI_FLOPPY_HOME` for development, then the newest