setup-pstack
Setup pstack
On Codex, read the platform mapping, including its per-skill notes, before following this skill.
On GitHub Copilot, read the platform mapping, including its per-skill notes, before following this skill.
On Muse, read the platform mapping, including its per-skill notes, before following this skill.
On Antigravity, read the platform mapping, including its per-skill notes, before following this skill.
Write the current runtime's per-role model override sheet. Each pstack skill names a default model inline; the override sheet adapts those defaults to the models you actually have access to.
On any runtime other than Claude Code, read Other runtimes first. Its table gives the sheet path, how the sheet loads, and how to list models, and your runtime's section says which steps change. The rest of this file describes Claude Code.
On Claude Code the config directory is $CLAUDE_CONFIG_DIR when that variable is set and ~/.claude otherwise. This skill calls it <config>, and the user sheet is <config>/pstack-models.md. A project sheet, .claude/pstack-models.md at the repository root (git rev-parse --show-toplevel; outside a repository, the directory Claude Code starts in), is committed with the repository and replaces the user sheet in that project. The session hook reads it whenever it exists. The model rows defer to it through the line step 6 writes under its heading, so a hand-written project sheet needs that line too. Claude Code has no auto-applied "rules" mechanism like Cursor's .mdc, so inclusion is explicit: the user adds a line to <config>/CLAUDE.md such as:
@<config>/pstack-models.md