NishikantaRay

attic

Offloads context. Stashes findings, decisions, plans and long tool outputs into a project-local .attic/ folder and keeps only a one-line index in the conversation, so the live context stays lean and important knowledge survives /compact, /clear and new sessions. Supports intensity levels: lite, full (default), ultra, off. Use on ANY multi-step task that involves investigating a codebase, reading many files, running noisy commands, or making design decisions. Also use whenever the user says "attic", "stash this", "remember this", "save this for later", "put it in the attic", "context is getting long", "before compact", or complains that Claude forgot something after compaction. Do NOT use for one-line answers, typo fixes, or non-coding chat.

attic-stash

Stash the current finding, result, plan or decision into .attic/ and reply with its handle. Use when the user says "stash this", "put this in the attic", "remember this", "save this for later", or when a finding is worth keeping and attic mode is active.

attic-fail

Record an approach that was tried and did not work, so nobody repeats it. Use when the user says "that didn't work", "this approach failed", "record this failure", "don't try this again", "note what we ruled out", or when an attempt in this session was abandoned for a reason worth keeping. Also use for a temporary workaround that should not be mistaken for a real fix.

Code & Development Listed

attic-review

Check which stashed items may no longer match the code, and resolve them. Use when the user says "review the attic", "what's stale", "is the attic still accurate", "check the attic against the code", "verify this finding", or after a big refactor, rebase or merge that may have invalidated earlier findings. This is about whether stashed knowledge is still TRUE; use attic-doctor for structural damage and attic-prune for items that are merely old.

Data & Documents Listed

attic-recall

Pull ONE item back out of .attic/ by slug or search words and summarise it. Use when the question names a TOPIC: "what did we find about X", "recall X", "what's in the attic about X", or when the user references an attic:<slug> handle. A question with no topic that just asks what the attic contains goes to attic-index instead.

Code & Development Listed

attic-doctor

Check the CONTENTS of .attic/ for drift: orphaned items, stale index lines, malformed frontmatter, oversized hooks, and leaked credentials. Use when the user says "check the attic", "attic doctor", "is the attic healthy", or "did anything leak into the attic". Never use this for git, merge or conflict problems, even though they sound like breakage: every merge conflict goes to attic-git.

attic-help

One-screen reference for the attic commands and levels.

attic-pin

Pin an attic item so it is always injected into new sessions and never trimmed when the index outgrows its budget. Use when the user says "pin this", "always remember this", "keep this in context", or when an item is a long-lived architectural decision or constraint that must survive. Use --unpin to reverse it.

attic-prune

Find stale attic items and archive them. Use when the user says "prune the attic", "the attic is getting big", "clean up old items", or "archive old findings". This is about the ATTIC's own contents, never about cleaning up source code.

Data & Documents Listed

attic-stats

Report what the attic costs and what it holds, measured from local session transcripts. Use when the user asks "is the attic worth it", "attic stats", "how many tokens is this saving", "how big is the attic", or questions the plugin's value.

attic-sweep

Save the state of the current session into the attic before context is lost: the current plan, open questions, in-progress work, and any finding not yet stashed. Use right before /compact or /clear, at the end of a session, or when the user says "save state", "wrap up", "before compact", "checkpoint", "context is getting long", "summarise what we've done so far", "where are we", or "recap the session". A request to recap session progress IS a sweep: give the recap and persist it in the same pass.

attic-index

List everything in the attic. Use for questions about the attic's CONTENTS as a whole with no particular topic: "what's in the attic", "what have you stashed", "list stashed items", "show the index", "how many items are in the attic". A question about a specific topic goes to attic-recall instead; this skill answers "what is in there", not "what did we find about X".

Code & Development Listed

attic-git

Everything about .attic/ and git: fixes merge conflicts in INDEX.md and DECISIONS.md by installing a union merge driver, and sets up a shared attic for a team. Use whenever git and .attic/ appear in the same problem: "merge conflicts in INDEX.md", "the attic keeps conflicting", "conflict in DECISIONS.md", "share the attic with my team", "commit the attic", "onboard someone to our attic".