メニュー
Use when creating or editing a slipstream skill, to produce one that loads cleanly and earns its place. Covers the frontmatter contract, the trigger-shaped description, the required body sections and the verification gate, so the skill validator passes and the skill is actually useful.
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 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.
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.
| name | writing-skills |
| description | Use when creating or editing a slipstream skill, to produce one that loads cleanly and earns its place. Covers the frontmatter contract, the trigger-shaped description, the required body sections and the verification gate, so the skill validator passes and the skill is actually useful. |
| slipstream | {"category":"context","requires":[],"tags":["meta","authoring","quality"]} |
A skill is a reusable piece of judgement the agent loads when it is relevant. A weak skill is worse than none: it adds noise and trains the agent to ignore skills. This meta-skill is how to write one that loads cleanly, fires at the right moment and changes behaviour. It encodes slipstream's own contract so a new skill passes the validator on the first try.
SKILL.md in a directory of the same name under the right category folder. The directory name must match the name in the frontmatter.slipstream.verification gate with a real command. The memory and context categories are gateless because they are about discipline, not a deployable artifact.## Steps and ## Verify sections, plus an optional ## Overview. Steps are small and concrete; Verify states how to prove the skill worked.requires pointing only at skills that really exist, since the loader checks every dependency.Run npx slipstream validate and confirm the skill loads with no issues, the directory matches the name, the required sections are present and any non-gateless category carries a verification gate.