Agent skill

Bendc Frontend Guidelines

by Asymmetric-al in Asymmetric-al/core

HTML, CSS, and JavaScript craft guidelines from bendc/frontend-guidelines — semantics, a11y basics, selector discipline, motion-friendly CSS, and readable JS.

AGPL-3.0Auto-check passedFrontend & Design

Install Bendc Frontend Guidelines

skills CLI
$ npx skills add Asymmetric-al/core --skill bendc-frontend-guidelines -a claude-code

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

GitHub CLI
$ gh skill install Asymmetric-al/core bendc-frontend-guidelines --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/Asymmetric-al/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bendc-frontend-guidelines .claude/skills/bendc-frontend-guidelines && 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
bendc-frontend-guidelines
GitHub stars
381
Token cost
~1.4k tokens
SKILL.md length
487 words
Files
3 (incl. references)
Skills in repo
43
Repo updated
First seen
Licence
AGPL-3.0

At a glance

HTML, CSS, and JavaScript craft guidelines from bendc/frontend-guidelines — semantics, a11y basics, selector discipline, motion-friendly CSS, and readable JS.

  • Works in 5 steps: Confirm the surface is in scope (markup,… → Load references/readme-original.md (or… → Cross-check Precedence above before… → …
  • Static HTML/CSS
  • SKILL.md covers Triggers, Do not use when, Precedence (this repo wins) and Workflow, plus 2 more sections
  • Calls bun

What it does

Bendc Frontend Guidelines is an agent skill from Asymmetric-al/core. HTML, CSS, and JavaScript craft guidelines from bendc/frontend-guidelines — semantics, a11y basics, selector discipline, motion-friendly CSS, and readable JS. Use for markup review, static HTML/CSS, email HTML, or general front-end hygiene; pair with repo frontend rules and TypeScript lint policy.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/readme-original.md` and `references/upstream.md`).

It sits in Frontend & Design, covering Accessibility. It works with JavaScript and TypeScript. The repository describes itself as: A high-performance, enterprise-grade Next.js 16 application for mission-focused non-profit organizations. Built for high impact teams. The licence is AGPL-3.0.

When your agent uses it

  • Static HTML/CSS
  • General front-end hygiene
  • Pair with repo frontend rules and TypeScript lint policy

Example prompts

  • “/bendc-frontend-guidelines”

Workflow steps

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

  1. Confirm the surface is in scope (markup, styles, or JS where the upstream checklist applies).
  2. Load references/readme-original.md (or skim the sections you need: HTML, CSS, JavaScript).
  3. Cross-check Precedence above before recommending a change that touches tokens, Tailwind, motion, JS/TS code shape, or TS types.
  4. For shared UI or app routes, reconcile recommendations with docs/ai/rules/frontend.md and nearby components.
  5. Prefer small, evidence-based edits; do not rewrite large areas solely to match upstream brevity examples if repo style differs.

What it can do on your machine

Read from SKILL.md and the folder at commit c30c8ff. 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

    Shell commands in SKILL.md call:

    • bun

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

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Bendc Frontend Guidelines loads about 1.4k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 487 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.6k

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 Asymmetric-al/core at commit c30c8ff, republished under its AGPL-3.0 licence (© Asymmetric-al). 487 words, ~1,418 tokens.

Download SKILL.mdSave it as .claude/skills/bendc-frontend-guidelines/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
bendc-frontend-guidelines
description
HTML, CSS, and JavaScript craft guidelines from bendc/frontend-guidelines — semantics, a11y basics, selector discipline, motion-friendly CSS, and readable JS. Use for markup review, static HTML/CSS, email HTML, or general front-end hygiene; pair with repo frontend rules and TypeScript lint policy.
metadata.owner
core
metadata.last_updated
2026-05-15
metadata.status
active
metadata.version
1.0.0

bendc Frontend Guidelines

Triggers

Use this skill when the task benefits from foundational HTML, CSS, and vanilla JS craft guidance from the vendored bendc/frontend-guidelines checklist, including:

  • Semantic HTML, document structure, lang, charset, and meaningful elements (main, article, time, etc.)
  • Accessibility basics called out upstream: alt text, real links and buttons, not relying on color alone, labelling controls
  • CSS structure: selector weight, avoiding unnecessary !important, inheritance, shorthand, flow and layout (flex/grid over absolute positioning when appropriate)
  • CSS performance habits: prefer opacity / transform for animation; avoid animating layout-heavy properties (aligns with repo motion rules)
  • Vanilla or legacy JS style: readability, native APIs, avoiding foot-guns called out in the upstream doc

Also load docs/ai/rules/frontend.md for any apps/* or packages/ui work in this monorepo.

Do not use when

  • The task is strictly backend, migrations, or database-only work.
  • You only need React / Next.js / App Router patterns — prefer docs/ai/skills/nextjs-app-router/SKILL.md and framework docs.
  • You only need Tailwind, design tokens, or shared @asym/ui primitives — the upstream doc is not Tailwind-specific; follow docs/ai/rules/frontend.md first.

Precedence (this repo wins)

The full text of the upstream guide lives in references/readme-original.md. When that reference conflicts with the Precedence table below, follow the table.

TopicAuthoritative in this repo
Tailwind, Maia/Zinc tokens, cn(), no arbitrary hex in componentsdocs/ai/rules/frontend.md
Motion timing, tokens, reduced motion, transition-all ban, route view transitionsdocs/ai/rules/frontend.md, docs/ai/skills/emil-design-engineering/SKILL.md, docs/ai/skills/anim/SKILL.md
General JavaScript / TypeScript code shape, control flow, helper extractionESLint, TypeScript configuration, formatter output, and nearby source patterns — prefer explicit, straightforward code over upstream terseness, loop avoidance, recursion, or shorthand
TypeScript types, strict, equality (===), linted patternsESLint / TS config and existing code style — do not adopt upstream examples that rely on loose equality or patterns that fail lint here
React component structure, Server Components, hooksNext.js docs and docs/ai/skills/react-component-dev/SKILL.md

Use the bendc guide as a second opinion on semantics, DOM clarity, CSS discipline, and readable JS. Do not copy upstream JavaScript advice about terseness, avoiding loops, recursion, composition, or shorthand unless it improves clarity under this repo's AGENTS.md conventions.

Show full SKILL.md (159 more words)Show less

Workflow

  1. Confirm the surface is in scope (markup, styles, or JS where the upstream checklist applies).
  2. Load references/readme-original.md (or skim the sections you need: HTML, CSS, JavaScript).
  3. Cross-check Precedence above before recommending a change that touches tokens, Tailwind, motion, JS/TS code shape, or TS types.
  4. For shared UI or app routes, reconcile recommendations with docs/ai/rules/frontend.md and nearby components.
  5. Prefer small, evidence-based edits; do not rewrite large areas solely to match upstream brevity examples if repo style differs.

Checklist

  • Confirmed triggers match (HTML/CSS/JS craft vs pure React/Next/backend).
  • Read the relevant sections of references/readme-original.md or the live upstream README.
  • Applied Precedence: repo frontend rules, motion skills, AGENTS.md code style, and TypeScript lint are satisfied.
  • Did not strip accessibility or semantics for brevity.
  • If you edited files under docs/ai/skills/bendc-frontend-guidelines/, ran bun run skills:sync and bun run skills:verify before committing.

See also

  • Repo UI policy: docs/ai/rules/frontend.md
  • Motion craft: docs/ai/skills/emil-design-engineering/SKILL.md, docs/ai/skills/anim/SKILL.md
  • React component patterns: docs/ai/skills/react-component-dev/SKILL.md
  • Maintainer refresh notes: references/upstream.md

© Asymmetric-al, AGPL-3.0. 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 2 other files (references) in .agents/skills/bendc-frontend-guidelines of Asymmetric-al/core.

  • SKILL.md
  • references/readme-original.md
  • references/upstream.md

Open the folder on GitHubat commit c30c8ff

Compare with similar skills

Bendc Frontend Guidelines 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.

Bendc Frontend Guidelines compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bendc Frontend Guidelines this skillAsymmetric-al/core381—~1.4kAutomated safety check: PassAGPL-3.0
Connect Component To Figmadequelabs/cauldron129—~2kAutomated safety check: PassMPL-2.0
Jarvis Setupethanplusai/jarvis846—~2.5kAutomated safety check: NotesCustom licence
React Ariaintentui/laravel1621 repos~3.9kAutomated safety check: PassApache-2.0
Language Supportlive-codes/livecodes1.5k—~1.6kAutomated safety check: PassMIT
Instui Docsinstructure/instructure-ui482—~498Automated safety check: PassCustom licence

Similar skills

  • Connect Component To Figma

    dequelabs/cauldron

    Add a Figma Code Connect (.figma.tsx) file for a Cauldron React component.

    129 GitHub stars~2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Jarvis Setup

    ethanplusai/jarvis

    A skill your agent uses when helping someone install, configure, or debug a fresh clone of JARVIS (this repo) — especially "the mic doesn't work", "JARVIS says his language systems are down", any…

    846 GitHub stars~2.5k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check: notes
  • React Aria

    intentui/laravel

    Build accessible UI components with React Aria Components. An agent skill from intentui/laravel.

    162 GitHub starsUsed in 1 repo~3.9k tokens
    Frontend & DesignAuto-check passed
  • Language Support

    live-codes/livecodes

    Work with 90+ supported languages, compilers, CSS processors, and WASM-compiled languages for markup, style, and script editors.

    1.5k GitHub stars~1.6k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Instui Docs

    instructure/instructure-ui

    Look up authoritative Instructure UI (InstUI, @instructure/ui-) documentation — component APIs, props, theme variables, usage examples, and guides — by querying instructure.design's plaintext docs.

    482 GitHub stars~498 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Ranui

    chaxus/ran

    A skill your agent uses when building UI with the ranui web-component library (elements like <r-button, <r-modal, <r-select, <r-input, <r-message) or its fluent DOM builder (ranui/builder —…

    269 GitHub stars~2k tokensUpdated today
    Frontend & DesignAuto-check passed

More from Asymmetric-al/core

All 43 skills in this repo
  • Idempotency Handling

    Asymmetric-al/core

    Implement idempotency keys and handling to ensure operations can be safely retried without duplicate effects.

    381 GitHub stars~867 tokensUpdated today
    Auto-check passed
  • Accessibility Review

    Asymmetric-al/core

    Audit and fix accessibility in Core UI. An agent skill from Asymmetric-al/core.

    381 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Email Inbox

    Asymmetric-al/core

    A skill your agent uses when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted…

    381 GitHub stars~4.1k tokensUpdated today
    Auto-check: notes
  • Components Build

    Asymmetric-al/core

    Build modern, composable, and accessible React UI components following the components.build specification.

    381 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Create Agent

    Asymmetric-al/core

    Guides a one-question-at-a-time design interview, captures alignment in agent/EVE-BRIEF.md, then scaffolds and implements a runnable eve agent with verbose teaching comments.

    381 GitHub stars~2.6k tokensUpdated today
    Auto-check: notes
  • Emil Design Engineering

    Asymmetric-al/core

    Design engineering principles and patterns for building polished, accessible web interfaces.

    381 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Questions about Bendc Frontend Guidelines

What does Bendc Frontend Guidelines do?

HTML, CSS, and JavaScript craft guidelines from bendc/frontend-guidelines — semantics, a11y basics, selector discipline, motion-friendly CSS, and readable JS. Bendc Frontend Guidelines is an agent skill from Asymmetric-al/core. HTML, CSS, and JavaScript craft guidelines from bendc/frontend-guidelines — semantics, a11y basics, selector discipline, motion-friendly CSS, and readable JS.

When should I use Bendc Frontend Guidelines?

Bendc Frontend Guidelines fits situations like: static HTML/CSS; general front-end hygiene; pair with repo frontend rules and TypeScript lint policy.

How do I install Bendc Frontend Guidelines in Claude Code?

Run `npx skills add Asymmetric-al/core --skill bendc-frontend-guidelines -a claude-code`. Or copy the skill folder (.agents/skills/bendc-frontend-guidelines in Asymmetric-al/core) into .claude/skills/bendc-frontend-guidelines in your project. Claude Code loads it when a task matches its description.

How do I install Bendc Frontend Guidelines in Codex?

Run `npx skills add Asymmetric-al/core --skill bendc-frontend-guidelines -a codex`. Or copy the skill folder (.agents/skills/bendc-frontend-guidelines in Asymmetric-al/core) into .agents/skills/bendc-frontend-guidelines in your project. Codex loads it when a task matches its description.

Can I use Bendc Frontend Guidelines 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 Asymmetric-al/core --skill bendc-frontend-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bendc-frontend-guidelines, .gemini/skills/bendc-frontend-guidelines, .github/skills/bendc-frontend-guidelines and .opencode/skills/bendc-frontend-guidelines in your project.

What does Bendc Frontend Guidelines need to run?

Going by SKILL.md and its folder, Bendc Frontend Guidelines needs the command-line tools its instructions call (bun).

Does Bendc Frontend Guidelines access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Bendc Frontend Guidelines 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 Bendc Frontend Guidelines use?

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

How many tokens does Bendc Frontend Guidelines use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.

What are the alternatives to Bendc Frontend Guidelines?

Skills that share tags, products or a category with Bendc Frontend Guidelines: Connect Component To Figma (dequelabs/cauldron, 129 stars), Jarvis Setup (ethanplusai/jarvis, 846 stars), React Aria (intentui/laravel, 162 stars) and Language Support (live-codes/livecodes, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bendc Frontend Guidelines?

Asymmetric-al (a GitHub organization) maintains it in Asymmetric-al/core, which has 381 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 9, 2026.

Source: Asymmetric-al/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.