Bendc Frontend Guidelines

Organization

Asymmetric-al

bendc-frontend-guidelines

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.

Overview

Publisher	Asymmetric-al
Repository	`core`
Skill name	`bendc-frontend-guidelines`
Stars	383
Forks	7
Bundled files	2
License	AGPL-3.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Asymmetric-al on GitHub. Read the source before you install it.

Installation

Install the Bendc Frontend Guidelines AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Asymmetric-al/core/tree/develop/docs/ai/skills/bendc-frontend-guidelines

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Asymmetric-al/core.git /tmp/core
mkdir -p .claude/skills
cp -r /tmp/core/docs/ai/skills/bendc-frontend-guidelines .claude/skills/bendc-frontend-guidelines

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bendc Frontend Guidelines in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bendc Frontend Guidelines on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bendc Frontend Guidelines is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Topic	Authoritative in this repo
Tailwind, Maia/Zinc tokens, `cn()`, no arbitrary hex in components	`docs/ai/rules/frontend.md`
Motion timing, tokens, reduced motion, `transition-all` ban, route view transitions	`docs/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 extraction	ESLint, 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 patterns	ESLint / 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, hooks	Next.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.

Workflow

Confirm the surface is in scope (markup, styles, or JS where the upstream checklist applies).
Load references/readme-original.md (or skim the sections you need: HTML, CSS, JavaScript).
Cross-check Precedence above before recommending a change that touches tokens, Tailwind, motion, JS/TS code shape, or TS types.
For shared UI or app routes, reconcile recommendations with docs/ai/rules/frontend.md and nearby components.
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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/readme-original.md16 KB
references/upstream.md1 KB

Frequently asked questions

What does the Bendc Frontend Guidelines AI skill do?

Why use Bendc Frontend Guidelines on TypingMind?

Because you install it once and use it with any model. Bendc Frontend Guidelines is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bendc Frontend Guidelines in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Asymmetric-al/core/tree/develop/docs/ai/skills/bendc-frontend-guidelines. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bendc Frontend Guidelines?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bendc Frontend Guidelines?

As many as you like. As long as a model supports skills, you can use Bendc Frontend Guidelines with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bendc Frontend Guidelines AI skill free?

Yes. It is published on GitHub by Asymmetric-al under the AGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Receiving Code Review

obra

CommunityPopular

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative…

Requesting Code Review

obra

CommunityPopular

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Systematic Debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Test Driven Development

obra

CommunityPopular

Use when implementing any feature or bugfix, before writing implementation code

Bendc Frontend Guidelines

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

bendc Frontend Guidelines

Triggers

Do not use when

Precedence (this repo wins)

Workflow

Checklist

See also

Bundled files

Frequently asked questions

Set up your own AI workspace now

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

bendc Frontend Guidelines

Triggers

Do not use when

Precedence (this repo wins)

Workflow

Checklist

See also

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now