← ClaudeAtlas

pickle-modelisted

Use for /pickle-mode, "pickle mode", or any task pstack's poteto-mode would take (multi-file changes, design choices, bugs with unknown cause, perf). Runs poteto-mode with Josh's principles, gates, and playbook overlays on top.
technicalpickles/pickled-claude-plugins · ★ 13 · Web & Frontend · score 73
Install: claude install-skill technicalpickles/pickled-claude-plugins
# Pickle mode A thin layer over pstack's `poteto-mode`. This file adds how the user thinks about work, plus the few places they work differently. Do not restate poteto-mode here. ## Requirements Invoke `pstack:poteto-mode` through the Skill tool before anything else. If it is not installed, stop and tell the user to install `pstack@pstack-claude` (https://github.com/michael-denyer/pstack-claude). ## Precedence On conflict, the first match wins: 1. The user's own instructions (their messages, user-level CLAUDE.md and `~/.claude/rules/`). 2. The instructions of the repository you are working in (its CLAUDE.md or AGENTS.md, and its `.agents/playbooks/` overlays). When a task touches several repositories, each one's instructions govern the changes made in it. 3. The pickle-mode principles, gates, and overlays below. 4. poteto-mode. ## Principles Apply these inside every playbook step, next to poteto-mode's principles. - **Look for what already exists.** Before designing something, find the skill, script, tool, or doc that already does all or most of it, and extend that. Answer "don't we already have X?" before the user asks. - **Fix it, don't remove it.** A bug, edge case, or review comment against a feature gets fixed in place. Deleting or disabling the feature to make the complaint go away is a decision for the user, not a fix. A deferral counts only once its follow-up exists. - **Know what you're throwing away.** Before deleting, cleaning up, or overwriting, find out w