Agent skill

Frontend

by 8borane8 in 8borane8/s2pipe

Conventions front (Slick, Preact, CSS structurel, islands). An agent skill from 8borane8/s2pipe.

MITAuto-check passedFrontend & Design

Install Frontend

skills CLI
$ npx skills add 8borane8/s2pipe --skill frontend -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 8borane8/s2pipe frontend --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/8borane8/s2pipe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/frontend .claude/skills/frontend && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
frontend
GitHub stars
107
Token cost
~2.2k tokens
SKILL.md length
960 words
Files
2
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Conventions front (Slick, Preact, CSS structurel, islands). An agent skill from 8borane8/s2pipe.

  • Works in 5 steps: main, header, footer, nav : seulement… → Les pages injectent leur contenu dans… → Preferer une hierarchie claire et… → …
  • Tasks that involve React components
  • SKILL.md covers Langue et prose, Stack et dossiers, Polices et assets and HTML structurel, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Frontend is an agent skill from 8borane8/s2pipe. Conventions front (Slick, Preact, CSS structurel, islands). A utiliser des que l'on ecrit, modifie ou review du HTML, CSS, JSX/TSX, pages, templates, islands, components ou styles.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `css-order.md`).

It sits in Frontend & Design, covering React components. It works with Preact. The repository describes itself as: Self-hosted cloud gaming for a Nintendo Switch 2 at home. The licence is MIT.

When your agent uses it

  • Tasks that involve React components

Example prompts

  • “Use the frontend skill to convention front (Slick, Preact, CSS structurel, islands). An agent skill from 8borane8/s2pipe”
  • “/frontend”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. main, header, footer, nav : seulement dans le template (une fois). Pas de doublon dans la page injectee. Le
  2. Les pages injectent leur contenu dans div#app avec section, aside, article, puis elements semantiques ou
  3. Preferer une hierarchie claire et semantique plutot que des wrappers inutiles.
  4. Eviter les conteneurs sans but precis : pas de nav > ol si ol seul suffit (choisir l'un ou l'autre), pas de div
  5. Factoriser: pas de duplication de markup; extraire un component ou une island selon le cas.

What it can do on your machine

Read from SKILL.md and the folder at commit f07d0b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and css).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Frontend loads about 2.2k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 960 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 8borane8/s2pipe at commit f07d0b0, republished under its MIT licence (© 8borane8). 960 words, ~2,223 tokens.

Download SKILL.mdSave it as .claude/skills/frontend/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
frontend
description
Conventions front (Slick, Preact, CSS structurel, islands). A utiliser des que l'on ecrit, modifie ou review du HTML, CSS, JSX/TSX, pages, templates, islands, components ou styles.

Front

Appliquer ces regles a chaque tache front. Lire aussi css-order.md avant d'ecrire du CSS.

Langue et prose

  • Tout le contenu UI, commentaires utiles, labels, titres, messages et textes visibles en francais.
  • Ne jamais utiliser le tiret cadratin (—). Preferer la virgule, les deux-points, les parentheses ou un tiret simple -.

Stack et dossiers

Stack: Deno, @webtools/slick-server, Preact, CSS dans static/styles/.

DossierRole
pages/Routes SSR
templates/Layouts
islands/UI interactive hydratee
components/UI statique ou logique pure, sans hydratation propre
static/styles/CSS (tokens, reset, pages, templates)

Reutiliser tokens.css (variables) et reset.css. Ne pas reinventer couleurs, rayons, espaces ou typos deja tokens.

Polices et assets

  • Importer les polices via @import dans le CSS (tokens.css ou fichier de zone), pas via <link> ou preconnect dans head.
  • Laisser head: null sauf besoin exceptionnel (meta specifique, script tiers, etc.).

HTML structurel

Slick et #root

Le body rendu d'un template est deja injecte dans div#root par Slick. Inutile d'ajouter une div principale de coque (div#auth-shell, etc.) : utiliser un fragment <>...</> quand plusieurs racines suffisent.

Le slot de page est div#app (pas un main) : Slick y injecte le body de la page. Les templates portent deja header (et nav si besoin). Les pages injectees dans #app n'utilisent pas main, header, footer, nav : section / aside / article / div. header / footer restent valides dans un <dialog>.

Styler la coque via #root dans le CSS du template concerne.

Semantique et wrappers
  1. main, header, footer, nav : seulement dans le template (une fois). Pas de doublon dans la page injectee. Le slot du template est div#app.
  2. Les pages injectent leur contenu dans div#app avec section, aside, article, puis elements semantiques ou div / span si besoin.
  3. Preferer une hierarchie claire et semantique plutot que des wrappers inutiles.
  4. Eviter les conteneurs sans but precis : pas de nav > ol si ol seul suffit (choisir l'un ou l'autre), pas de div autour d'un h1 + p deja adjacents, etc.
  5. Factoriser: pas de duplication de markup; extraire un component ou une island selon le cas.

Exemple template (slot Slick) :

tsx
<div id="app">{/* contenu page */}</div>;

Exemple page avec aside :

tsx
<section id="register">
	<aside>...</aside>
	<article>...</article>
</section>;

Exemple page simple :

tsx
<section id="login">
	<article>...</article>
</section>;

CSS structurel

Selecteurs
  • Conteneur de page ou zone : un id sur la coque unique (#register, #billing).
  • Balise unique dans le template : pas besoin d'id si l'element n'existe qu'une fois (aside, nav, header dans ce template). Utiliser le selecteur de type directement (aside > h1, nav > a).
  • Motif reutilisable : class sur le conteneur racine du motif (.field, .btn, .brand).
  • Enfants d'un conteneur identifie : eviter les id enfants. Preferer le markup semantique (h1, p, form, fieldset) et des selecteurs structurels.
  • A l'interieur d'un conteneur, pas de classes partout. Styler via cascade et selecteurs structurels:
css
#register > article > form > fieldset > label > span {
	...
}
aside > h1 {
	...
}
aside > ol > li[aria-current="step"] > p {
	...
}
.field > input {
	...
}
  • Factoriser les styles partages en classes courtes; eviter les utilitaires type Tailwind.
  • Un fichier CSS par page ou zone, declare dans styles du template/page.
Fichiers et specificite

L'ordre dans styles compte: a specificite egale, le fichier charge plus tard gagne.

Pour masquer une zone, le selecteur doit battre le display du fichier de zone. Preferer un enfant de la coque:

css
#page > #panel {
	display: none;
}

pas #panel { display: none } si #panel { display: flex } est declare plus loin.

Layout
  • Preferer flexbox par defaut.
  • Utiliser grid seulement quand c'est clairement mieux (grilles 2D, alignements complexes).
  • Eviter float, et les proprietes layout exotiques ou fragiles (position absolu partout, hacks, etc.) sauf besoin reel.
Ordre des proprietes

Toujours le meme ordre de groupes. Mieux vaut declarer explicitement (ex. flex-direction: row) que d'omettre. Details et liste complete: css-order.md.

css
.box {
	width: 100%;
	height: auto;
	max-width: 28rem;

	color: var(--color-text);
	font-size: var(--text-md);
	font-weight: 400;
	font-family: var(--font-sans);
	line-height: 1.5;

	text-align: left;
	text-transform: none;

	display: flex;
	flex-direction: row;
	justify-content: flex-start;
	align-items: center;
	flex-wrap: nowrap;
	gap: var(--space-3);

	margin: 0;
	padding: var(--space-4);

	overflow: visible;
	background: var(--color-bg-elevated);
	border: 1px solid var(--color-border);
	border-radius: var(--radius-md);
}
Show full SKILL.md (400 more words)Show less

Islands vs components

BesoinEmplacement
Element interactif (etat, events, formulaires client, signals)islands/
Markup / UI non hydratee, ou logique UI sans hydratation proprecomponents/

Regles strictes:

  1. Une island = racine d'interactivite. Export default Preact depuis islands/.
  2. Les components peuvent etre dynamiques (props, rendu conditionnel) mais doivent etre importes depuis une island (ou depuis une page/template s'ils restent 100% statiques SSR).
  3. Interdit: importer une island depuis une autre island.
  4. Pages et templates importent les islands; les islands importent des components, jamais l'inverse pour l'hydratation.
  5. Minimiser le JS client: ne pas hydrater ce qui peut rester HTML statique.
txt
page / template
  -> island (interactive)
       -> component (sous-UI, factorisee)
  -> component (statique SSR ok)

Navigation

Interdit: location.reload(), location.assign(), location.href =.

  • Changer de page: Slick.redirect(url) (@webtools/slick-client).
  • Rester sur la page apres une mutation: mettre a jour le DOM et les signals (conserver media, scroll, etat local).
  • Lien interne: <a href> suffit (Slick intercepte).

UX

  • Liste / catalogue: la liste est le contenu principal. Creation et edition dans un <dialog>, pas un formulaire toujours visible a cote.
  • Champs de saisie vides: placeholder (exemples courts).
  • "Reinitialiser" applique tout de suite. Pas besoin d'une seconde confirmation du type Valider.
  • Un filtre ou etat actif doit se voir (compteur, pastille, aria-pressed).
  • Ne pas garder de controle UI sans usage reel.

Factorisation

  • Extraire des qu'un motif se repete (markup, CSS, logique).
  • Preferer un component/island clair plutot que copier-coller. Deux ecrans identiques = une island parametree, pas deux.
  • CSS: classes partagees pour les motifs; ids pour les coques de page.
  • Props et API internes courtes; pas d'abstractions prematurees inutiles.
  • Reutiliser tokens et styles existants avant d'en ajouter.

Checklist avant de livrer

  • Textes FR, aucun tiret cadratin
  • Polices via @import CSS, pas de <link> font dans head
  • Pas de div coque inutile dans le template (#root suffit)
  • div#app dans le template (slot Slick), pas de main sur le slot
  • Pas de main / header / footer / nav dans la page injectee (deja dans le template)
  • Balises uniques sans id superflu; pas d'id sur les enfants d'une coque
  • Markup semantique (h1, p, ol) plutot que id descriptifs
  • Pas de wrappers inutiles (nav > ol, div autour de h1 + p, etc.)
  • Ids sur conteneurs de page, classes sur motifs reutilisables
  • CSS structurel dans les sous-arbres (pas de classes sur chaque enfant)
  • Proprietes CSS dans l'ordre defini, flex explicite
  • Interactif = island; pas d'import island -> island
  • Factorise, tokens reutilises, peu de JS client
  • Pas de reload hard; mutation sur place ou Slick.redirect
  • Placeholders; reinitialiser applique sans etape de plus
  • Responsive: palier intermediaire

© 8borane8, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .cursor/skills/frontend of 8borane8/s2pipe.

  • SKILL.md
  • css-order.md

Open the folder on GitHubat commit f07d0b0

Compare with similar skills

Frontend next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Frontend compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontend this skill8borane8/s2pipe107—~2.2kAutomated safety check: PassMIT
Tailwind To Stylexshadcn-labs/shadcn-cssinjs123—~2.7kAutomated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k41 repos~769Automated safety check: PassApache-2.0
Tailwindcss Developmentanonaddy/anonaddy4.9k10 repos~865Automated safety check: PassMIT
Core Component Library PatternsChrisWiles/claude-code-showcase6.1k8 repos~1.2kAutomated safety check: PassNone
React Router Developmentremix-run/react-router57k1 repos~1.5kAutomated safety check: PassMIT

Similar skills

  • Tailwind To Stylex

    shadcn-labs/shadcn-cssinjs

    Migrate TailwindCSS to StyleX. An agent skill from shadcn-labs/shadcn-cssinjs.

    123 GitHub stars~2.7k tokensUpdated 26 days ago
    Frontend & DesignAuto-check passed
  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 41 repos~769 tokens
    Frontend & DesignAuto-check passed
  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed
  • Core Component Library Patterns

    ChrisWiles/claude-code-showcase

    Reference for building UI with a token-based core component library: spacing, color and typography tokens, Box, stacks, Text, Button, Input and Card, plus layout patterns.

    6.1k GitHub starsUsed in 8 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • React Router Development

    remix-run/react-router

    Guides work on React Router apps by first identifying whether the app uses Framework, Data or Declarative mode, then loading the matching reference and the installed package docs.

    57k GitHub starsUsed in 1 repo~1.5k tokens
    Frontend & DesignAuto-check passed
  • React UI State Patterns

    ChrisWiles/claude-code-showcase

    Sets patterns for React interfaces: when to show loading spinners or skeletons, how to surface errors, how to disable buttons during async work and how to handle empty lists.

    6.1k GitHub starsUsed in 8 repos~1.6k tokens
    Frontend & DesignAuto-check passed

Works with

Questions about Frontend

What does Frontend do?

Conventions front (Slick, Preact, CSS structurel, islands). An agent skill from 8borane8/s2pipe. Frontend is an agent skill from 8borane8/s2pipe. Conventions front (Slick, Preact, CSS structurel, islands).

When should I use Frontend?

Frontend fits situations like: tasks that involve React components.

How do I install Frontend in Claude Code?

Run `npx skills add 8borane8/s2pipe --skill frontend -a claude-code`. Or copy the skill folder (.cursor/skills/frontend in 8borane8/s2pipe) into .claude/skills/frontend in your project. Claude Code loads it when a task matches its description.

How do I install Frontend in Codex?

Run `npx skills add 8borane8/s2pipe --skill frontend -a codex`. Or copy the skill folder (.cursor/skills/frontend in 8borane8/s2pipe) into .agents/skills/frontend in your project. Codex loads it when a task matches its description.

Can I use Frontend in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 8borane8/s2pipe --skill frontend -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend, .gemini/skills/frontend, .github/skills/frontend and .opencode/skills/frontend in your project.

What does Frontend need to run?

SKILL.md names no scripts, command-line tools or credentials: Frontend is instructions for the agent only.

Does Frontend access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Frontend safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Frontend use?

Frontend is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frontend use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Frontend?

Skills that share tags, products or a category with Frontend: Tailwind To Stylex (shadcn-labs/shadcn-cssinjs, 123 stars), Web Artifacts Builder (anthropics/skills, 180k stars), Tailwindcss Development (anonaddy/anonaddy, 4.9k stars) and Core Component Library Patterns (ChrisWiles/claude-code-showcase, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontend?

8borane8 (a GitHub user) maintains it in 8borane8/s2pipe, which has 107 GitHub stars. The repository was last updated on October 6, 2026.

Source: 8borane8/s2pipe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.