Menu
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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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 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 | frontend-hero-section |
| description | 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. |
| slipstream | {"category":"frontend","requires":["frontend-design-system"],"verification":{"kind":"build","description":"The app builds with the hero section in place.","command":"pnpm --dir {{appName}} build"},"tags":["design","landing","polish"]} |
The hero decides whether a visitor stays. A polished one is not busy: it is one strong line, one supporting sentence, one primary action, and generous space around them. This skill builds that, leaning on the design system tokens so it matches the rest of the site.
clamp(2.5rem, 6vw, 5rem)) with tight tracking and a balanced two or three line wrap.Build the app and confirm it compiles, then load the page and check the hero shows one headline, one supporting line and a single primary action, with the type scaling smoothly between a narrow and a wide viewport.