pstack Files

The skills that named Claude Code's user skills and plugins directories as ~/.claude/skills/ and ~/.claude/plugins/ now name ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/skills/ and ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/plugins/. Claude Code keeps both under its configuration directory. Without this change, on a machine with CLAUDE_CONFIG_DIR set, poteto-agent searched an empty ~/.claude/plugins/ for the poteto-mode skill, automate-me missed personal mode skills, and the reflect reviewers ignored the skill reads they were meant to count. The ~/.cursor/plugins/ rule in tools/substitutions.json writes the new form, and a new ~/.cursor/skills/ rule runs ahead of the project .cursor/skills/ rule, so a sync derives the same text and the change adds no fork.

recall, automate-me, and the Session pickup playbook described <encoded-cwd> as the workspace path with / changed to -, and recall said the leading slash was dropped. Claude Code changes every character other than a letter or digit to -, the leading slash included, so /private/tmp/coat_opus48_440 is stored as -private-tmp-coat-opus48-440. The three now say so.

tests/claude-config-dir.test.mjs now also fails on a skills or plugins path under ~/.claude without the variable, and on the old encoding wording. The ~/.claude/orchestrate/ store stays where it is: pstack creates it, not Claude Code. Both gaps were listed in the Scope section of #298.

Verified. Both tests fail on 14 lines at 0.9.98 and pass here. The sync dry-run at the pinned SHA prints the same ownership map as 0.9.98: 47 forked, 87 unchanged. The encoding comes from the projects/ directory names on a machine running Claude Code 2.1.296. Claude Code's environment variable reference says plugins live under CLAUDE_CONFIG_DIR. For user skills, the 2.1.296 binary joins skills onto the same configuration directory. A separate run with the variable set did not happen, because a new configuration directory starts logged out.