Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From code-habits
Use when about to write a state, cursor, marker, scratch, or progress file for a cron loop, monitor task, polling job, recurring schedule, or any session-scoped/ephemeral data — directs the file to /tmp/<name>.json instead of ~/.claude/ or other config dirs.
npx claudepluginhub amitkot/claude-code-tools --plugin code-habitsHow this skill is triggered — by the user, by Claude, or both
Slash command
/code-habits:ephemeral-state-in-tmpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When you need to write a state file whose lifetime equals or is shorter than the current session, cron job, or monitor task — write it under `/tmp/`, not `~/.claude/` or any other config dir.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
When you need to write a state file whose lifetime equals or is shorter than the current session, cron job, or monitor task — write it under /tmp/, not ~/.claude/ or any other config dir.
The session/cron/task dies or expires; whatever you wrote stays. A file in /tmp self-cleans on reboot and matches the lifetime correctly. A file in ~/.claude/ becomes orphan state cluttering the user's settings dir with no automatic cleanup, and the user has to find and delete it manually.
/tmp/<feature>-state.json, not ~/.claude/.<feature>-state.json/tmp/<task>-progress.json/tmp/poll-cursor.json~/.claude/ IS rightOnly for state that should survive across sessions: durable preferences, memory entries indexed via MEMORY.md, settings that persist beyond the lifetime of any single task. If the file is read by a session-only cron, it's not durable — it goes in /tmp.