Menú
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.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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 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.
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-git-worktrees |
| description | 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. |
| slipstream | {"category":"context","requires":[],"tags":["git","isolation","parallel"]} |
A single working tree can only hold one state at a time, so two strands of work editing the same files collide, and a risky experiment contaminates the tree you trust. A git worktree gives a branch its own directory backed by the same repository: separate files, shared history, no second clone. It is the isolation layer that makes [[dispatching-parallel-agents]] safe when strands would otherwise overlap.
git worktree add ../<name> -b <branch>. It is a full directory you can build and test in independently.git worktree remove ../<name>. Do not leave stale worktrees; they drift and confuse later sessions.Each isolated strand built and verified inside its own worktree, the main tree was never a shared edit surface, and every worktree was removed after its branch integrated.