メニュー
Use whenever the user says "use slipstream", "use superpowers", or starts any task in a project that has slipstream. A hard, always-on discipline that forces scoped reads over whole-file reads to save tokens, recalls memory before acting, and records what is durable every turn so memory grows constantly.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when several pieces of work are genuinely independent and can run at once, to fan them out across parallel agents instead of doing them in sequence. Cuts wall-clock time and keeps each strand in its own clean context.
Use when a written plan exists and you are about to build it in the current session, to work it task by task with a checkpoint after each. Keeps execution honest against the plan instead of drifting into a freehand build.
Use when work needs its own isolated checkout — parallel strands that would fight over files, or a risky change you want quarantined from the main tree. Gives each strand a real working directory on its own branch without re-cloning.
Use when a site needs to look designed rather than defaulted, before building sections: establish a cohesive design system of type scale, spacing, colour, radius and shadow tokens so every component shares one premium visual language.
Use when building the top of a landing page, to produce a high-impact hero with confident display type, a clear single call to action and balanced composition, the kind of opening a polished marketing site leads with.
Use when filling out a landing page below the hero, to build the polished marketing sections a premium site is made of: a feature grid, a logo or social-proof strip, a testimonial and a closing call to action.
| name | using-slipstream |
| description | Use whenever the user says "use slipstream", "use superpowers", or starts any task in a project that has slipstream. A hard, always-on discipline that forces scoped reads over whole-file reads to save tokens, recalls memory before acting, and records what is durable every turn so memory grows constantly. |
| slipstream | {"category":"context","requires":[],"tags":["discipline","memory","token-efficiency"]} |
slipstream only saves tokens and builds memory if the agent actually uses it. The dashboard showing "0% optimised" means whole files were read instead of scoped slices: a failure, not a neutral state. This skill is a rigid discipline, not a suggestion. When the user invokes slipstream, follow every step. Do not read a whole file when a symbol or a line range will do. Do not finish a turn without recording what is durable.
/slipstream:recall). Never start from zero on something a past session already decided..claude/slipstream/map.md (/slipstream:map), then pull exactly what you need with sp_symbol (one symbol) or sp_lines (one range). Reading an entire file when a slice would do is a defect; the optimisation tally must not stay at 0%.sp_search over the map and sp_search_memory over past work before grepping the tree./slipstream:remember. Memory should grow constantly, not only when asked.Confirm three things before claiming the turn is done: you recalled memory before the first read, you used scoped reads (sp_symbol/sp_lines) rather than whole-file reads so the optimisation tally moved above 0%, and any durable outcome is saved (npx slipstream memory list --root . shows it). If you read a whole file when a slice would have worked, say so and correct the habit.